Content
@
0 reply
0 recast
0 reaction
itai (building dynamic.xyz)
@itai
1/ 🌟 With the rise of smart contract wallets like the @coinbasewallet smart wallet, understanding ERC-6492 is becoming crucial, and so I wanted to write a quick thread to explain it in a bit more detail. Let's dive in!
7 replies
19 recasts
50 reactions
itai (building dynamic.xyz)
@itai
2/ 🤔 The Challenge: One of the cool features of account abstraction (ERC-4337) is deferring contract deployment until you need it. This saves on gas costs while still providing a deterministic address. But here's the catch: how do you Sign In with Ethereum (SIWE) using a contract that isn't deployed yet?
1 reply
0 recast
2 reactions
itai (building dynamic.xyz)
@itai
3/ 💡 The Solution: Enter ERC-6492, which introduces a standard way to validate signatures for these pre-deployed contracts. This allows interactions with "counterfactual addresses"—addresses that represent contracts not yet on-chain but will be when needed.
1 reply
1 recast
1 reaction
itai (building dynamic.xyz)
@itai
4/ 🛠️ Counterfactual Addresses: Think of these as Schrödinger's Contracts. They're both deployed and not deployed until you open the box (or, in this case, actually deploy them).
1 reply
0 recast
2 reactions
itai (building dynamic.xyz)
@itai
5/ 🔄 How ERC-6492 Works: It wraps signatures with specific data, including the factory address and creation calldata. This enables verification processes to simulate contract deployment and check the signature as if the contract were already live.
1 reply
0 recast
2 reactions
