PeerDAS in Fusaka is significant because it literally is sharding.
Ethereum is coming to consensus on blocks without requiring any single node to see more than a tiny fraction of the data. And this is robust to 51% attacks - it's client-side probabilistic verification, not validator voting.
Sharding has been a dream for Ethereum since 2015 , and data availability sampling since 2017 ( github.com/ethereum/resea… ), and now we have it.
That said, there are three ways that the sharding in Fusaka is incomplete:
* We can process O(c^2) transactions (where c is the per-node compute) on L2s, but not on the ethereum L1. If we want to scaling to benefit the ethereum L1 as well, beyond what we can get by constant-factor upgrades like BAL and ePBS, we need mature ZK-EVMs.
* The proposer/builder bottleneck. Today, the builder needs to have the whole data and build the whole block. It would be amazing to have distributed block building.
* We don't have a sharded mempool. We still need that.
But even still, this is a fundamental step forward in blockchain design. The next two years will give us time to refine the PeerDAS mechanism, carefully increase its scale while we continue to ensure its stability, use it to scale L2s, and then when ZK-EVMs are mature, turn it inwards to scale ethereum L1 gas as well.
Big congrats to the Ethereum researchers and core devs who worked hard for years to make this happen.
Ethereum is coming to consensus on blocks without requiring any single node to see more than a tiny fraction of the data. And this is robust to 51% attacks - it's client-side probabilistic verification, not validator voting.
Sharding has been a dream for Ethereum since 2015 , and data availability sampling since 2017 ( github.com/ethereum/resea… ), and now we have it.
That said, there are three ways that the sharding in Fusaka is incomplete:
* We can process O(c^2) transactions (where c is the per-node compute) on L2s, but not on the ethereum L1. If we want to scaling to benefit the ethereum L1 as well, beyond what we can get by constant-factor upgrades like BAL and ePBS, we need mature ZK-EVMs.
* The proposer/builder bottleneck. Today, the builder needs to have the whole data and build the whole block. It would be amazing to have distributed block building.
* We don't have a sharded mempool. We still need that.
But even still, this is a fundamental step forward in blockchain design. The next two years will give us time to refine the PeerDAS mechanism, carefully increase its scale while we continue to ensure its stability, use it to scale L2s, and then when ZK-EVMs are mature, turn it inwards to scale ethereum L1 gas as well.
Big congrats to the Ethereum researchers and core devs who worked hard for years to make this happen.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
