jesse.base.eth πŸ”΅ pfp
jesse.base.eth πŸ”΅
@jessepollak
I love this idea
9 replies
0 recast
33 reactions

androidsixteen pfp
androidsixteen
@androidsixteen.eth
Honest question - what's the benefit of an "L3" here? If the event span is shorter than the time it takes to play exit games, then why not just have a server and post selective data to L2 at the end of the event?
1 reply
0 recast
8 reactions

jesse.base.eth πŸ”΅ pfp
jesse.base.eth πŸ”΅
@jessepollak
L3s don't have to be optimistic w/exit games. could do validity proofs. or could even just do a trusted commitment at the end from the operator. benefit is: 0. use L2 assets 1. write everything in EVM 2. integrate seamlessly with other EVM tools 3. everything is open and onchain it's gradually going to "just work"
3 replies
1 recast
11 reactions

silv pfp
silv
@silv.eth
I thought another huge benefit of L3 was that gas fees can be drastically cheaper than L2? So many more txns can be on-chain than were feasible otherwise? Or is that not the case
2 replies
0 recast
0 reaction

jesse.base.eth πŸ”΅ pfp
jesse.base.eth πŸ”΅
@jessepollak
yes that's the case!
0 reply
0 recast
1 reaction

androidsixteen pfp
androidsixteen
@androidsixteen.eth
You don't get another factor of savings when you post to L3 vs. L2 because the "compression" from a validity proof or from posting calldata can only be gained once Savings could come from more efficient VMs or using alt-DA layers, but those savings could also be gained at L2. What L3 really allows for is *flexibility*
1 reply
0 recast
0 reaction