-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add chainId to bot's config #283
Comments
/start |
@rndquu The time limit for this bounty is on Tue, 16 May 2023 15:16:11 GMT Your currently set address is: |
[ CLAIM 50 DAI ]
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We are in the process of moving to support L2/sidechains for bounty hunter payouts because of high gas fees on ethereum mainnet.
We should be done:
chainId
parameter here from the bot's yml configchainId
is not set then by default use1
for ethereum mainnetNotice that while it seems natural also to read a payment token address from the bot's config we shouldn't do it because gelato network (used for relaying safe transactions for large rewards) supports only few tokens so chances are that partner would set an unsupported token. So right now it is safer to hardcode payment token addresses for each supported network.
The text was updated successfully, but these errors were encountered: