4844

What Is 4844?

4844 refers to Ethereum’s EIP-4844 proposal, also known as Proto-Danksharding. It was activated as part of the Dencun mainnet upgrade, introducing a more cost-effective “data publishing” mechanism for Layer 2 networks.

In the Ethereum ecosystem, Layer 2 solutions (L2s) function like elevated highways, helping divert large volumes of traffic. Rollups are the most common L2 implementation, bundling multiple user transactions and posting them to Ethereum mainnet to ensure security. EIP-4844 introduces a new “Blob” data channel, making this data publishing step both cheaper and more scalable.

Why Does 4844 Reduce L2 Costs?

Previously, rollups stored their transaction data on Ethereum’s “calldata,” competing with regular smart contract execution for the same resources—resulting in high prices. EIP-4844 moves this “short-lived” data to a separate “Blob fee market,” making costs more predictable and manageable.

Think of calldata as a “permanent notice board,” while Blobs are like “temporary display boards that are regularly cleared.” Since rollups only need to guarantee data availability for a limited period, Blobs suffice and offer lower costs, increasing overall network throughput.

What Is a Blob in 4844?

A Blob is a large chunk of data attached to a special transaction type, used exclusively for publishing and attestation. Blobs cannot be read directly by Ethereum smart contracts (EVM); instead, their integrity and availability are assured through commitment and verification mechanisms.

Blob data is stored on the network only temporarily before being pruned by nodes, easing permanent storage requirements. This aligns with rollup needs, as they only require anyone to access historical data during dispute or replay periods.

How Does 4844 Work on Ethereum?

4844 introduces a new transaction type that can carry Blob data. Each block has a cap on the number of Blobs it can include, and Blob pricing is determined by a dedicated market that adjusts dynamically based on supply and demand.

When users or rollups submit Blob-carrying transactions, validators check the associated commitments for validity and collect Blob fees. This design separates “data availability costs” from “contract execution costs,” preventing resource contention and stabilizing L2 data publishing expenses.

It’s important to note that the EVM cannot access Blob contents directly; applications must rely on commitment proofs to verify that the Blob was published as required. This approach reduces long-term storage burdens while retaining an audit window for data recovery and verification.

How Does 4844 Impact Rollups?

4844 makes it significantly cheaper for rollups to publish data, enabling larger batches and more flexible packaging—directly improving user experience with lower fees and faster confirmations. Since the Dencun upgrade in March 2024, core L2 fees have dropped dramatically and remained low over time (see: Ethereum.org upgrade notes and community fee dashboards, March 2024 onward).

For operators, smoother fees and expanded data bandwidth mean supporting more users and sophisticated applications—such as high-frequency trading, NFT minting, or in-game interactions—with better resilience during peak periods.

How Can You Save on L2 with 4844?

To benefit from lower costs enabled by EIP-4844, the main principle is to perform on-chain interactions on Ethereum L2s that support Blobs, while paying attention to deposit/withdrawal methods and risk management.

Step 1: Prepare Your Wallet. Use a popular wallet updated to the latest version for compatibility with L2 networks and signature formats. Beginners can add the target L2’s RPC endpoint and chain ID in wallet settings.

Step 2: Deposit and Withdraw via Gate. Transfer funds from Gate to your target L2 address by selecting the appropriate L2 network channel on the withdrawal page—usually with lower network fees. The reverse applies for deposits; always double-check network and address details, test with a small amount first to avoid loss from errors.

Step 3: Interact on L2. Carry out transfers, DEX trades, or NFT minting on your chosen L2—typically enjoying lower network fees and faster confirmation. During busy periods, consider tipping higher fees or transacting off-peak.

Step 4: Monitor Fee Dashboards. Keep an eye on official or community-provided L2 fee panels, noting any temporary spikes in Blob pricing due to congestion and timing your transactions for cost efficiency.

Step 5: Understand Bridge Wait Times. Official bridges for different L2s may have withdrawal delays; in urgent cases, reputable third-party bridges can be used, but always assess counterparty risk and extra fees.

Risk Warning: All on-chain transfers and signatures carry irreversible risk. Always verify networks, contracts, and addresses—start small to minimize potential losses.

How Does 4844 Differ from Sharding and Calldata?

Compared to calldata, Blobs in 4844 have their own fee market, are stored temporarily, and cannot be read directly by the EVM—making them ideal for rollup data that only needs short-term availability and usually at a lower price point.

Unlike full sharding, 4844 is an interim solution (Proto-Danksharding). It does not split Ethereum into parallel execution shards but instead increases data bandwidth within the existing structure while introducing independent pricing—laying groundwork for future Danksharding and data availability sampling.

What Are the Risks and Limitations of 4844?

EIP-4844 does not directly lower smart contract execution costs on Ethereum Layer 1; complex contracts remain expensive on L1. If Blob demand surges in a short period, Blob prices may rise temporarily—causing brief L2 fee volatility.

Blob data is only stored on the network for a limited time before deletion, requiring rollups and node operators to archive necessary data elsewhere. Wallets, browsers, or tools may vary in how quickly they upgrade for compatibility; early users may experience display or signature prompt discrepancies.

Additionally, 4844 does not alter the fundamental security model of rollups or bridge withdrawal times. Users must remain vigilant regarding cross-chain bridges, contract upgrades, and permission management risks.

What’s Next for 4844?

EIP-4844 is seen as a critical step toward full Danksharding. Next steps include raising the Blob per-block cap, optimizing fee adjustment mechanisms, and advancing technologies like Data Availability Sampling (DAS) to further expand bandwidth and node participation.

On the application side, more L2s will optimize batching strategies around lower-cost data availability (DA), making high-frequency and real-time on-chain applications increasingly viable. Alternative data availability layers will continue developing in parallel with Ethereum’s roadmap—creating a multi-layered ecosystem.

Key Takeaways of 4844

EIP-4844 delivers a cheaper, short-term storage channel for rollup data publishing by decoupling “data availability costs” from “contract execution costs.” This greatly improves Layer 2 fees and throughput while paving the way for full Danksharding. For users: moving interactions onto Blob-enabled L2s, choosing proper deposit/withdrawal channels via Gate, and following risk management best practices help ensure you benefit from lower costs and a better experience.

FAQ

Will Blob Data Be Stored Permanently On-Chain?

No. Blob data remains on-chain for about 18 days before being automatically deleted. This temporary storage design meets L2 data availability requirements while saving full node storage space. L2 projects can archive necessary historical data elsewhere before Blobs expire to ensure traceability.

Why Are Blobs So Much Cheaper Than Calldata?

Blobs have a dedicated gas pricing mechanism with initially low prices and do not compete with contract execution for gas space. Calldata must be stored and executed by all nodes permanently—making it expensive—while Blobs only need to be stored for 18 days with a separate gas market. This design allows L2 transaction costs to decrease by over 90%.

If I Transact on an L2, Will I Notice Cheaper Fees Due to 4844?

Yes. As long as your chosen L2 implements Blob-based data publishing, you will benefit directly from significantly lower transaction fees. Leading L2s like Arbitrum and Optimism already support Blobs; new users can bridge assets from platforms like Gate to these L2s for low-cost transactions.

Why Is Each Blob Fixed at 128KB in Size?

This size reflects Ethereum’s trade-off between throughput and node resource requirements. A 128KB Blob meaningfully reduces L2 costs without overwhelming node verification or storage loads. The size may be adjusted based on future network conditions but is currently proven effective.

Does 4844 Affect Mainnet Transactions on Ethereum?

Very little. EIP-4844 primarily optimizes Layer 2 transactions—mainnet transactions do not use Blobs. However, by dramatically reducing L2 costs over time, it encourages more users to migrate from mainnet to L2s—helping relieve mainnet congestion as part of Ethereum’s scalability roadmap.