dackie
Farcaster channel for Dackie community. Following the vision bringing the world on-chain. Invite link: https://warpcast.com/~/channel/dackie/join?inviteCode=GsZLJFfLieD9EdH_-9sNZw
DackieSwap pfp
1 reply
1 recast
2 reactions
Dackie pfp
0 reply
0 recast
3 reactions
Dackie pfp
1 reply
1 recast
3 reactions
DackieSwap pfp
0 reply
1 recast
1 reaction
Dackie pfp
3 replies
0 recast
7 reactions
Dackie pfp
0 reply
0 recast
3 reactions
DackieSwap pfp
2 replies
1 recast
5 reactions
Dackie pfp
1 reply
0 recast
4 reactions
Dackie pfp
2 replies
0 recast
4 reactions
Dackie pfp
1 reply
0 recast
2 reactions
andreapn pfp
In my understanding, the SuperchainERC20 operates with the following highlights: 1. The SuperchainERC20 token must be deployed on a superchain (such as Base, OP, Zora, Mode...) using the same contract address. Therefore, it must be deployed via a create2 factory. 2. There is no lock and unlock mechanism when bridging with SuperchainERC20; instead, it uses a burn/mint mechanism. 3. SuperchainERC20 is a standard ERC20 token with an integrated extension that allows SuperBridge to burn tokens on the source chain and mint them on the destination chain. 4. No approval is needed when bridging via SuperBridge. 5. The SuperchainERC20 token on the destination chain should revoke owner permissions to prevent minting on other destination chains instead of the source chain. 6. One unclear point, which @optimism has not addressed extensively, is the type of message sent between superchains during bridging. Is it sent via a validator node or by some other means? https://x.com/Optimism/status/1866508652016013666
0 reply
1 recast
3 reactions
DackieSwap pfp
0 reply
5 recasts
9 reactions
DackieSwap pfp
0 reply
1 recast
5 reactions
DackieSwap pfp
0 reply
1 recast
4 reactions
andreapn pfp
0 reply
2 recasts
3 reactions