This repository has been archived by the owner on Sep 19, 2024. It is now read-only.
Replies: 1 comment 2 replies
-
I think this looks bounty ready. I agree with the Did you post it under discussions because you wanted to work through something more before turning it into an official bounty? |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Ethereum gas prices are high again and withdrawing payouts becomes more and more expensive.
Some folks are already complaining:
There are many options for L2 solutions (here the term "L2" also includes sidechains). I think we can select any L2 solution which meets the following criteria:
Eth mainnet <=> L2
Gnosis Chain is not widely adopted but meets other criteria.
How fast is the bridge
Bridge website: https://bridge.gnosischain.com
It takes 20 block confirmations on ethereum mainnet (~4 minutes) to transfer DAI from ethereum mainnet to gnosis chain. Technically ethereum mainnet's DAI are converted to XDAI on gnosis chain (XDAI is used for gas payments on gnosis chain, 1 XDAI = 1 DAI).
It takes 20 block confirmations on gnosis chain (~2 minutes) to transfer XDAI from gnosis chain to DAI on ethereum mainnet. It requires 2 transactions: 1st transfer transaction is on gnosis chain and 2nd claim transaction is on ethereum chain (which is pretty expensive right now)
Codebase
Right now we support payouts in ERC20 DAI on ethereum mainnet. XDAI in gnosis chain is not a plain ERC20 token, it is used for gas payments (the same way as ETH is used in ethereum chain). While it seems to be natural to support XDAI (which is pegged to DAI) for payouts in gnosis chain it also requires us to maintain 2 codebases for permit2 and gnosis safe payouts. By "2 codebases" I mean supporting payouts in ERC20 and native gas tokens which adds complexity. That is why it is better to use WXDAI in gnosis chain which is a plain ERC20 token.
In short
ERC20 DAI in ethereum = ERC20 WXDAI in gnosis chain
. So bounty hunter payouts are going to be inWXDAI
in gnosis chain and inDAI
on ethereum mainnet.Bounty hunter flow
From a bounty hunter's view everything is the same. He posts
/wallet 0x01
and solves an issue. Payouts (permit2 URLs or automatic safe transactions) are performed in a chain that would be set in partner's config.Partner flow
Partner would need to add a
CHAIN_ID
parameter to the bot's config. So partner will be able to use either ethereum mainnet either gnosis chain.Also notice that while it is technically possible to create 2 gnosis safes with the same address (on mainnet and in gnosis chain) current gnosis safe web UI does not support this feature. From https://help.safe.global/en/articles/5267779-i-sent-assets-to-a-safe-address-on-the-wrong-network-any-chance-to-recover:
How to migrate on the bot's side
Basically we need to:
CHAIN_ID
from a partner's configBeta Was this translation helpful? Give feedback.
All reactions