
Danksharding represents Ethereum's next-generation scaling technology, fundamentally designed to make the network faster, cheaper, and more accessible to users worldwide. At its core, ethereum danksharding breaks up the blockchain's data processing workload, allowing the network to handle thousands of transactions per second without sacrificing the decentralization principles that make Ethereum secure and trustworthy.
Traditional sharding approaches split a blockchain into multiple segments, or "shards," with each shard processing its own independent set of transactions. Ethereum's danksharding takes this concept several steps further: instead of maintaining separate shards with fixed collation leaders, danksharding organizes data with a single proposer per slot, thanks to the innovative "dank" design. This architectural choice significantly simplifies protocol logic and improves overall efficiency.
The evolution of ethereum danksharding emerged from the network's ongoing efforts to solve scalability challenges. The Ethereum upgrade roadmap originally proposed traditional sharding to address network congestion. However, with the rapid rise of rollups and the increasing need for faster data availability, danksharding emerged as the preferred solution. This technology is particularly crucial as the network faces growing user demand and as DeFi, NFTs, and gaming applications continue to expand rapidly.
Here's how danksharding compares to classic sharding:
| Feature | Traditional Sharding | Danksharding |
|---|---|---|
| Data Segmentation | Multiple Shards | Single Data Space |
| Proposer System | Multiple Collators | Single Proposer |
| Complexity | Higher | Lower |
| Scalability Potential | High | Very High |
The single proposer model in danksharding reduces coordination overhead and makes the system more efficient. By consolidating the data availability layer, ethereum danksharding creates a more streamlined architecture that can scale more effectively than traditional multi-shard designs.
💡 Pro Tip: Danksharding isn't just for developers—every user on Ethereum will experience lower fees and faster transactions once the technology is fully implemented.
Proto-danksharding, officially known as EIP-4844, serves as an important stepping stone towards full ethereum danksharding implementation. It represents a protocol upgrade designed to immediately reduce transaction fees by introducing a new data structure called "blobs" to the Ethereum network.
EIP-4844 is particularly significant because it adds these data blobs to the Ethereum Mainnet, enabling rollups to post transaction data more efficiently and at a fraction of the current cost. Unlike full danksharding, proto-danksharding doesn't segment the entire blockchain into multiple shards, but it establishes all the essential groundwork: blob data structures, new fee markets, and the validator mechanics necessary for future upgrades.
The implementation of proto-danksharding marks a critical milestone in Ethereum's scaling journey. By introducing blobs as a new transaction type, EIP-4844 creates a separate fee market for data availability, which doesn't compete with regular transaction execution. This separation is crucial for maintaining low fees on Layer 2 rollups while preserving Ethereum's security guarantees.
Key features introduced by EIP-4844:
The difference between proto-danksharding and full danksharding lies primarily in scope and scale. Proto-danksharding introduces data blobs and the mechanisms developers need to significantly cut rollup fees, whereas full danksharding will further scale up the number of blobs per block and introduce even greater data capacity. Proto-danksharding can be thought of as "danksharding lite"—it delivers immediate benefits while paving the way for more comprehensive scaling solutions.
Danksharding's power lies in how it enables efficient, low-cost data storage for rollups through several innovative mechanisms. The main innovations are data blobs, KZG commitments, and a new validator process that work together to create a scalable and secure system.
What are Data Blobs?
Data blobs are large chunks of binary data included alongside Ethereum blocks. These blobs represent a new transaction type specifically designed for data availability. Unlike regular transaction data, blobs are not directly accessible by smart contracts, but rollups use them to store large amounts of transaction data at a significantly reduced cost. Because blobs don't compete with regular Ethereum transactions for block space, rollup fees drop dramatically.
Each blob can contain approximately 125 KB of data, and blocks can include multiple blobs. This creates a substantial amount of additional data capacity for the network without impacting regular transaction processing. The blobs are stored by consensus layer nodes for a limited period (typically a few weeks), which is sufficient for rollups to process and finalize their transactions.
KZG Commitments and Their Role
KZG (Kate-Zaverucha-Goldberg) commitments are cryptographic proofs that ensure blobs can be verified without requiring validators to download and process all the data. These commitments allow the network to guarantee data availability while maintaining efficiency. The KZG ceremony, which was completed in 2023 with participation from tens of thousands of contributors worldwide, generated secure cryptographic parameters that make it mathematically impossible for anyone to manipulate or censor blob data.
KZG commitments work by creating a cryptographic "fingerprint" of the blob data. Validators can verify that the data exists and is correct by checking this fingerprint, without needing to process the entire blob. This is crucial for maintaining Ethereum's decentralization, as it keeps hardware requirements for validators reasonable even as data throughput increases dramatically.
Validator Processing Explained
Validators in the danksharding system propose and validate blocks that now contain blob data alongside regular transactions. They confirm that blobs are available and verifiable—not by reading all the content, but by checking the KZG commitments. This process maintains Ethereum's decentralization while boosting data throughput significantly.
When a validator proposes a block with blobs, other validators perform data availability sampling to ensure the blobs are actually available. This sampling process is efficient and doesn't require downloading entire blobs, making it feasible for validators to participate even with modest hardware.
| Component | Purpose |
|---|---|
| Data Blobs | Store large rollup data at low cost |
| KZG Commitments | Ensure data availability and validity |
| Validators | Propose and verify blocks with blobs |
| Data Availability Sampling | Efficient verification without full downloads |
💡 Pro Tip: Blobs make rollups dramatically cheaper—always check if your dApp or favorite Layer 2 has integrated EIP-4844 for maximum fee savings!
Rollups are scaling solutions that bundle (or "roll up") many transactions off-chain and post summary data to Ethereum for security. These solutions have become the primary scaling strategy for Ethereum, and proto-danksharding makes them significantly more efficient and affordable.
There are two major types of rollups, each with distinct approaches:
Optimistic Rollups (e.g., Arbitrum, Optimism, Base): These rollups assume transactions are valid by default, with fraud proofs available for disputes. If someone submits an invalid transaction, other participants can challenge it during a dispute period. This approach is simpler but requires a waiting period for withdrawals.
ZK (Zero-Knowledge) Rollups (e.g., zkSync, StarkNet, Polygon zkEVM): These rollups use advanced cryptographic proofs to instantly validate transactions. While more complex to implement, they offer faster finality and don't require dispute periods.
Proto-danksharding's blobs allow both types of rollups to store transaction data much more cheaply than before. Previously, rollups had to post data as expensive calldata, competing with regular transactions for block space. With blobs, rollups have a dedicated, much cheaper data availability layer. This massively reduces rollup operating costs and, by extension, user fees.
The impact on users is substantial and immediate. Lower data posting costs mean rollups can pass savings directly to users, making Ethereum-based applications more accessible to everyone. This is particularly crucial for enabling mass adoption of DeFi, NFTs, and on-chain gaming.
Examples of User Cost Impact:
Major rollup projects have quickly adopted proto-danksharding to take advantage of these cost savings. Most leading Layer 2 solutions have integrated EIP-4844 support, and users are already experiencing the benefits through reduced transaction fees. Major trading platforms and exchanges have also begun supporting these rollups, making it easier for users to access low-cost Ethereum transactions.
Danksharding is engineered with end users in mind, delivering tangible benefits that make Ethereum more accessible and practical for everyday use. The technology addresses the network's most pressing challenges: high fees, limited throughput, and scalability constraints.
Key Benefits:
| Feature | Pre-Danksharding | Post-Danksharding |
|---|---|---|
| Layer 2 Transaction Fees | $0.30–$2.00 | $0.02–$0.10 |
| Data Throughput | ~1MB/block | 16MB+/block (future) |
| User/Dev Access | Limited by cost | Open for mass use |
| Transactions Per Second | Limited | Significantly increased |
For traders and users on major platforms, these improvements mean lower bridging fees, more trading opportunities on Ethereum Layer 2 solutions, and quicker deposits and withdrawals as rollups settle faster across the ecosystem. The cost reduction is particularly impactful for users who make frequent transactions or participate in DeFi protocols with multiple operations.
The scalability improvements also enable entirely new use cases that were previously impractical due to high fees. Micro-payments, on-chain gaming with frequent state updates, and social applications with high transaction volumes all become viable on Ethereum with danksharding.
Let's examine the concrete impact of proto-danksharding on transaction fees across popular Ethereum rollups. The data demonstrates the dramatic cost reduction that users experience:
| Rollup | Avg. Tx Fee (Before EIP-4844) | Avg. Tx Fee (After EIP-4844) |
|---|---|---|
| Arbitrum | $0.30 | $0.05 |
| Optimism | $0.25 | $0.04 |
| Base | $0.19 | $0.03 |
| zkSync Era | $0.20 | $0.03 |
How the Fee Reduction Works:
Data Posting: Rollups must post transaction data to Ethereum for security and data availability. This ensures that anyone can reconstruct the rollup state if needed.
Before EIP-4844: Rollups posted data using expensive calldata, which competed with regular smart contract transactions for block space. This made data posting one of the largest costs for rollup operators.
With Proto-Danksharding: Rollups post data as blobs, which exist in a separate fee market and are significantly cheaper than calldata. Blobs don't compete with execution layer transactions.
User Benefits: As rollup operators save on data posting costs, they pass these savings directly to users through lower transaction fees. The reduction happens almost immediately as rollups adopt blob usage.
Fee Market Dynamics: The blob fee market operates independently from regular gas fees, creating a more stable and predictable cost structure for Layer 2 operations.
Additional Considerations:
Variable Fees: While blob fees are generally much lower, they can fluctuate based on demand for blob space. However, even during high demand, blob fees remain substantially lower than calldata costs.
Security Maintained: The security and trust guarantees remain identical to the pre-blob system. Blobs are committed to the beacon chain and verified by validators.
Gradual Adoption: As more rollups adopt EIP-4844, users should verify that their preferred Layer 2 has implemented blob support to ensure they're receiving maximum fee savings.
Long-term Trajectory: As full danksharding is implemented, fees are expected to decrease even further as the number of available blob spaces per block increases.
Danksharding was architected to preserve Ethereum's core values of security, censorship resistance, and decentralization even as the network scales to handle dramatically higher transaction volumes. These properties are fundamental to Ethereum's value proposition and cannot be compromised for the sake of performance.
Censorship Resistance
Danksharding makes it extremely difficult for any single participant or group to prevent data from being included in blocks. The single proposer structure, combined with KZG commitments, creates multiple layers of protection against censorship at the protocol level. Even if some validators attempt to censor certain transactions or data, the probabilistic nature of validator selection and the transparency of blob commitments make sustained censorship impractical.
The data availability sampling mechanism also contributes to censorship resistance. Because validators can efficiently verify that data is available without downloading entire blobs, it becomes harder for malicious actors to hide censored data. The network can quickly detect and respond to censorship attempts.
Decentralization Preservation
Maintaining a large, decentralized validator set is crucial for Ethereum's security model. Danksharding achieves increased throughput without significantly raising hardware requirements for validators. Validators handle blob data using accessible cryptographic checks (KZG commitments) rather than processing all the data directly. This keeps participation barriers low and allows a diverse, geographically distributed validator set to independently verify data availability.
The design carefully balances increased data capacity with validator requirements. Even as the number of blobs per block increases with full danksharding, the verification process remains efficient enough for home validators to participate meaningfully in network consensus.
KZG Ceremony and Cryptographic Security
The KZG ceremony represents a critical security component of the danksharding system. This trusted setup, conducted with participation from tens of thousands of contributors worldwide, generated the cryptographic parameters necessary for KZG commitments. The ceremony's design ensures that as long as at least one participant acted honestly and destroyed their secret contribution, the system remains secure.
This cryptographic foundation guarantees data availability even if some validators are malicious. The mathematical properties of KZG commitments make it computationally infeasible to create false proofs or hide unavailable data.
Security Best Practices for Users:
Ethereum's scaling roadmap follows a carefully staged approach, with each phase building upon previous achievements. The progression from proto-danksharding to full danksharding represents a multi-year journey of continuous improvement.
Phase 1: Proto-Danksharding (EIP-4844) This phase has been implemented, delivering blob data structures and achieving major fee savings for rollup users. The initial implementation includes support for a limited number of blobs per block, which already provides substantial scaling benefits.
Phase 2: Data Availability Upgrades Ongoing improvements focus on enhancing Layer 2 data interactions and optimizing the blob fee market. This includes refinements to data availability sampling, improvements to validator efficiency, and potential increases in the number of blobs per block.
Phase 3: Full Danksharding The ultimate goal targets 64 or more blob data spaces per block, exponentially increasing Ethereum's data availability capacity. This will enable even cheaper rollup transactions and support significantly higher transaction throughput across the entire ecosystem. Full danksharding will also introduce more sophisticated data availability sampling techniques.
Phase 4: Future Proposals Beyond full danksharding, researchers are exploring multidimensional fee markets, further sharding research and development, and potential integration with other scaling technologies. The roadmap remains flexible to incorporate new innovations as they emerge.
The transition from proto-danksharding to full functionality is expected to occur over the next several years, subject to thorough testing, security audits, and mainnet stability verification. The Ethereum development community prioritizes security and decentralization over speed of implementation, ensuring each upgrade meets the network's high standards.
Key Milestones to Watch:
The roadmap demonstrates Ethereum's commitment to long-term scalability while maintaining the security and decentralization properties that make the network valuable. Each phase brings tangible benefits to users while laying groundwork for future improvements.
Ethereum Danksharding is an upgrade designed to increase transaction throughput, reduce costs, and enhance network security. It improves blockchain rollup efficiency, enabling higher transaction volume per block while maintaining decentralization and safety.
Proto-Danksharding makes extensive changes to Ethereum's architecture today, enabling future upgrades to full Danksharding. Danksharding represents the complete implementation with enhanced data availability and scalability through blob-carrying transactions.
Danksharding enhances Ethereum's transaction throughput through sharding technology, significantly reducing gas fees. It provides additional storage space for rollup transactions, enabling the network to process more transactions efficiently and simultaneously.
Danksharding combines sharding with Rollup technology to enhance scalability while maintaining decentralization and security. It separates settlement and data availability layers, offering more efficient transaction processing and lower fees than traditional Layer 2 solutions, positioning itself as Ethereum's ultimate scaling solution.
Danksharding的分阶段实现预计从2023年起开始,Proto-Danksharding作为第一步已在规划中。完整Danksharding的主网实现时间表仍在调整,具体上线日期尚未最终确定。
Danksharding enhances Ethereum's security by improving data availability, reducing centralization risks, and strengthening the network's resistance to censorship through distributed data sampling.











