Danksharding Definition: Danksharding is Ethereum’s scaling design that adds large, temporary data packets called blobs to each block, giving rollups a cheap place to publish their transaction data. Instead of every node downloading every blob, nodes will eventually check that the data is available by sampling small random pieces of it, which lets the number of blobs per block grow without raising hardware requirements.
What Is Danksharding?
Ethereum’s scaling plan relies on rollups, networks that execute transactions off the main chain and post compressed records back to it. Posting that data used to be their biggest cost, because it competed with every other transaction for ordinary block space. Danksharding gives rollups a separate, cheaper lane.
The idea replaced an older plan. Ethereum once intended sharding in the classic sense, splitting the network into many parallel chains. Researchers concluded that rollups would do the execution work more efficiently, so the main chain only needed to guarantee one thing at scale: that rollup data was published and available to anyone who wanted to check it.
Danksharding is arriving in stages rather than in one upgrade. The first stage is already live, and each later step builds on how blobs are priced and verified.
How Does Danksharding Work?
The first stage, proto-danksharding, arrived with EIP-4844 in the Dencun upgrade on 13 March 2024. It introduced blobs: chunks of about 128 KB attached to a block but kept separate from the main transaction data. Ethereum nodes store blobs for only about 18 days, long enough for anyone to verify a rollup’s records, then delete them. The chain permanently keeps just a small cryptographic commitment to each blob.
Blobs have their own fee market, modelled on EIP-1559. A blob base fee rises when blocks carry more blobs than the target and falls when they carry fewer, independent of ordinary gas prices. At launch, the target was three blobs per block with a maximum of six.
Consider what this did to a rollup’s costs. Before Dencun, a rollup posting a batch of user transactions paid for that data at the same rate as any other Ethereum transaction. After Dencun, it posted the batch as a blob in a market with little competition, and on several major rollups user fees dropped by more than 90% within days. The rollups changed nothing else; only the price of their data fell.
Full danksharding raises the blob count much further. The obstacle is that more blobs mean more data for every node to download.
Data availability sampling solves this: blob data is extended with error-correcting codes, and each node downloads only small random pieces. If enough random samples are available, the whole blob almost certainly is. The Fusaka upgrade of December 2025 introduced PeerDAS, the first version of this sampling on Ethereum.
Proto-Danksharding vs. Full Danksharding
| Proto-danksharding (EIP-4844) | Full danksharding | |
|---|---|---|
| Status | Live since March 2024 | Being rolled out in stages |
| Blob capacity | A handful of blobs per block | Many times more |
| How nodes verify data | Every node downloads every blob | Nodes sample random pieces |
| Main benefit | Separate, cheaper data market for rollups | Far greater data capacity without heavier nodes |
Why Is Danksharding Important for Traders?
Danksharding sets the cost of trading on Ethereum’s Layer 2 networks. Cheaper blobs are why a swap on a major rollup can cost cents instead of dollars, and each capacity increase tends to push those fees down further. For active traders, that makes Layer 2 venues practical for strategies that would be unprofitable on the main chain.
It also reshapes ETH’s economics. Rollups that used to pay large fees to Ethereum now pay much less, so less ETH is burned through fees. When blob demand stays below target, the blob fee sits near its minimum and contributes almost nothing, which is one reason ETH supply can grow during quiet periods even after the Merge.
The design has limits. Blobs are deleted after about 18 days, so rollups and third parties must keep their own long-term copies of the data. Cheap blob space only helps while supply exceeds demand; if rollup usage outgrows capacity, blob fees rise just like ordinary gas. Data availability sampling is also new and complex, and bugs in it would affect every rollup that depends on Ethereum for data.
Key Takeaways
- Danksharding scales Ethereum by giving rollups cheap, temporary blob space for their data instead of splitting the network into shards that execute transactions.
- Proto-danksharding, live since the Dencun upgrade in March 2024, added blobs of about 128 KB with their own fee market.
- Blobs are deleted after roughly 18 days, while the chain keeps a permanent cryptographic commitment to their contents.
- Full danksharding relies on data availability sampling, letting nodes verify large amounts of data by checking small random pieces.
- Cheaper blob space lowers Layer 2 trading fees but also reduces the ETH burned by rollups.
Is danksharding the same as sharding?
No. Earlier sharding plans would have split Ethereum into many parallel chains that each executed transactions. Danksharding keeps a single chain and only shards data availability, leaving execution to rollups.
Does danksharding make Ethereum mainnet transactions cheaper?
Not directly. Blobs carry rollup data, so the savings go mainly to Layer 2 users, while fees for ordinary transactions on the main chain still depend on demand for regular block space.
What happens to blob data after it is deleted?
Ethereum nodes drop blobs after about 18 days, but rollups, indexers and archive services keep copies. The blockchain permanently stores only a small cryptographic commitment that proves what each blob contained.
Who is danksharding named after?
It is named after Ethereum researcher Dankrad Feist, who proposed the design. Proto-danksharding also nods to researcher Protolambda, one of the authors of EIP-4844.
