Content
@
0 reply
26 recasts
26 reactions
jesse.base.eth 🔵
@jessepollak
we aligned internally today that our medium term scaling goal is to target 1 Ggas/s on @base our current target is 2.5 mgas/s, so ~400x, with a long term goal of pushing even further past >1000x it's pronounced "gigagas" and this is our broadband moment
29 replies
40 recasts
379 reactions
androidsixteen
@androidsixteen.eth
What's your OKR for managing state growth and ensuring full nodes can stay synced with the network on consumer hardware? Throughput is great, but you're just big blocking unless you have a plan for staying decentralized
2 replies
0 recast
1 reaction
shazow
@shazow.eth
Isn't this conflating decentralization requirements of L1's? It's important for an L1 to be runnable on consumer hardware because there isn't another chain to fall back to when things go wrong. L2's have that luxury, so we can make more generous assumptions (like ignoring full state transition history).
1 reply
0 recast
1 reaction
androidsixteen
@androidsixteen.eth
Are you suggesting that nobody besides the sequencer should need to run a full node for the L2?
1 reply
0 recast
1 reaction
shazow
@shazow.eth
I'm suggesting no one needs to be able to replay the entire history from genesis for L2's, as an example. Yes, many infrastructure participants need to be able to run verifying nodes but those can be partial/light, etc.
1 reply
0 recast
1 reaction
androidsixteen
@androidsixteen.eth
Splitting optimistic vs. zk rollups: - zk: main assumption here would be that the prover can keep up with the throughput, which still takes into consideration another property besides gas/s - optimistic: don't you need a robust set of nodes that can check the sequencer's work?
1 reply
0 recast
0 reaction
