BlockchainAdvanced#Scaling#Deep Tech
Sharding
S
Definition
A family of scaling designs that divide data or execution work across subsets of a network; the exact meaning depends on the protocol.
Source reviewed
- Ethereum.org: Danksharding roadmap opens in a new tab
Supports: Documents Proto-Danksharding blobs, the later full-Danksharding roadmap, data-availability sampling, and that shard chains are no longer part of Ethereum's roadmap.
- Ethereum.org: Data availability opens in a new tab
Supports: Explains why data availability matters for verification, and distinguishes full-node verification from rollup and light-client constraints.
Concept Diagram
Key Takeaways
1
Sharding can refer to different ways of partitioning execution, state, data, or validator work
2
Ethereum's current sharding roadmap uses temporary data blobs for rollups, not execution shard chains
3
Full Danksharding remains a later roadmap stage; it is not a current TPS guarantee
4
Check data availability, validation, settlement, retention, and live-versus-proposed scope for each protocol
Practical Example
A rollup posts transaction data in an EIP-4844 blob rather than treating Ethereum as 64 execution chains. A user checking the system should distinguish the rollup's execution and security model from Ethereum's temporary blob-data availability, and should not infer a fixed fee or throughput outcome from the word sharding.
Finished learning?
Related Terms
Blockchain
Data Availability (DA)Assurance that data needed for a specified verification process was published and can be accessed under that system's rules. It is distinct from permanent historical retrievability.
Blockchain
Base Layer (Layer 1)A blockchain's own consensus and settlement layer. The label describes where that protocol processes and orders transactions; security, finality, data availability, and scaling guarantees differ by chain and design.
Blockchain
Layer 2 (L2)A protocol layer that executes transactions outside an L1 while using that L1 for some combination of data availability, proofs, dispute resolution, or settlement. Fees, finality, bridges, and withdrawal paths depend on the specific L2 design.
Blockchain
NodeSoftware connected to a blockchain network that can relay data and, depending on its operating mode, validate blocks and transactions under that network's rules. Node capabilities, data retained, privacy, and trust assumptions vary by implementation.
Related Deep Dives
Master the hub of Blockchain
Explore all our strategic guides about Blockchain to take your operations to the next level.
View all articles