Bundlers need some assurance that the network state will not change on a layer 2 blockchain between the time a bundler does its checks and the transaction is included.
This would lose bundlers money.
To fix this, Yoav proposes a new RPC request.
The request is eth_sendRawTransactionConditional, which acts just like eth_sendRawTransaction but includes some lightweight checks for the sequencer so the bundler doesn't submit an invalid bundle.
It checks:
- block number is within a range
- block time is within a range
- validate that a list of addresses haven't changed state OR
- that storage slots of addresses have the expected values
This won't stop us from deploying on new networks of course.
But if it becomes unprofitable to run bundlers on these networks, everyone loses.
[shameless plug at end of thread]
Learn more about account abstraction and start using ERC-4337 today at stackup.sh
• • •
Missing some Tweet in this thread? You can try to
force a refresh
Wow, lots of excitement and questions about ERC-4337!
I'm going to address a few of the common questions and concerns people have about it:
"Account abstraction has existed before! What's new about this?"
This is true! Smart accounts have existed before, notably Safe and Argent.
Three things make it stand out.
Standout 1:
Unlike other implementations of account abstraction including Argent, Safe, Biconomy, Gelato network, and so on, it provides a decentralized relay system so it's censorship resistant.