Content
@
0 reply
0 recast
0 reaction
jacopo.eth
@jacopo.eth
Great summary about the challenges and strategy for scaling ethereum. One thing I’m personally excited about are L1 state reads from L2, not just for interop but to boost composability for protocols on L2. Many use cases I’ve thought about will finally become possible. I also plan to contribute more to discussions and development. If you’re an Ethereum dev, consider doing the same. There’s no better time to get involved.
3 replies
0 recast
24 reactions
.
@chaskin.eth
Please let me know how I can help you
1 reply
0 recast
6 reactions
I. Christwin〔▸‿◂〕💡
@ichristwin.eth
I totally feel the same way. Learnt about L1CALL and L1SLOAD during the most recent DevCon and I've been counting the hours waiting for Pectra to go live. I'm using tokenbound accounts (EIP-6551) as the native accounts for tokenized-revenue-generating-assets (see Infrastructure Finance aka iFi) https://medium.com/althea-mesh/introducing-ifi-infrastructure-finance-4e23056ca114 It abstracts away a lot of things to just make them NFTs with TBAs. But then every revenue they generate for their owners on the L2 can only be claimed via a tx message bridged from the assets TBAs on L1, simply because there is no easy way to know `ownerOf(assetId)` to approve the claim for. L1SLOAD or REMOTESTATICCALL makes my life a whole lot easier with. 🥹 we unlock a lot better UX for crosschain DePIN & IFI apps with this. https://x.com/tyneslol/status/1852346121081020775
0 reply
0 recast
2 reactions
rocketman
@rocketman
have this working in /flows can vote with your nouns on base
1 reply
0 recast
2 reactions
