Content pfp
Content
@
0 reply
0 recast
0 reaction

jesse.base.eth πŸ”΅ pfp
jesse.base.eth πŸ”΅
@jessepollak
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!
3 replies
5 recasts
57 reactions

Joethebeast.eth 🎩🍱 pfp
Joethebeast.eth 🎩🍱
@joethebeast1221
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 πŸ‘†
5 replies
0 recast
2 reactions

Michael de Hoog pfp
Michael de Hoog
@mdehoog
The ideal end state would be some ability to read L1 state directly on L2s, like Optimism's Remote Static Call proposal or Brecht's L1CALL proposal. It seems it will take some time before we standardize on this.
0 reply
0 recast
2 reactions