Ethereum

Been working on a prototype and spec for @vitalik.eth's minimal keystore rollup

hackmd.io/@mdehoog/mksr

Please read and comment if you have thoughts

one of the hardest problems with smart contract wallets is how you manage keys across 10s or 100s or 1000s of chains.

@mdehoog from the @base team has been building on @vitalik.eth's initial specification for a keystore rollup - would love folks to review and share feedback!

Devconnect

@base builder #001; onchain cities w/ OAK & city3

I managed to invite @vitalik.eth to share this idea back in /devconnect Istanbul and recall 2 of the many challenges on the idea 

- Can we avoid recursive SNARKs and get L1 gas costs low by batching?
- How can we get enough L2s have L1-reading functionality?

I think there are more but I only jotted down the qs 👆

Contributing @bentobatch FID:12963
My opinions are trash, but Account Abstraction is the future. #ERC4337  
Hosting /bento-batch

Re L2s having L1-reading functionality: this is a big missing piece. The options today are to either do MPT proofs on L2s that have access to an L1 state root, or for L2s that support it, send deposit messages on the L1 to L2s to update their MKSR root.