jesse.base.eth 🔵
@jessepollak
I love this idea
9 replies
0 recast
33 reactions
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 🔵
@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
androidsixteen
@androidsixteen.eth
> could even just do a trusted commitment at the end from the operator I get what you're saying. It's easier to use the same tool-suite if the shape of the backend is a "chain"
1 reply
0 recast
3 reactions
jesse.base.eth 🔵
@jessepollak
yes, exactly! and you get access to the built in payments and identify infrastructure which is incredibly powerful!
1 reply
0 recast
2 reactions
androidsixteen
@androidsixteen.eth
it is still confusing to me that we would want to use a kludgy time-series DB intended for a consensus environment in a centralized manner but liquidity and identity onramps from existing chains are compelling reasons! Someone needs to be a very efficient "L3" (ie. a server) that could be used for all these use cases
1 reply
0 recast
2 reactions
jesse.base.eth 🔵
@jessepollak
yeah I expect we will see massive experimentation across L3 infrastructure and we are excited about all of it on base talking with folks about running OP Stack L3s, Orbit L3s, MoveVM L3s, SVM L3s, etc etc
1 reply
0 recast
2 reactions