{"id":"EIP-4844","name":"Shard Blob Transactions","status":"Final","chain":"ethereum","category":{"id":"infrastructure","name":"Infrastructure","description":"Foundational patterns enabling other standards"},"journeyStages":[{"id":"gas","name":"Gas & Fees","description":"Paying for transactions"}],"uxImpact":"L2 rollups can post data cheaply via blobs — dramatically lower L2 fees but blob data is temporary. Design implications: on L2 UIs, show 'Secured by Ethereum blobs' badge, indicate blob fee separately from execution gas on L2 fee breakdowns, for data-heavy L2 txs show potential savings vs. calldata. Design decisions: whether to expose blob mechanics to users (educational) or abstract as 'L2 data fee' (simple); how to communicate temporary blob availability for archival use cases. Live on all major L2s. Slashed L2 fees 10-100x. Unpredictable Gas Fees (Medium) remains a prediction and transparency UX gap despite dramatically lower costs.","hasDetailedContent":true,"content":{"id":"EIP-4844","summary":"EIP-4844 introduces \"blob transactions\" - a new way to post data to Ethereum that's 10-100x cheaper. This slashed Layer 2 fees dramatically, making Arbitrum, Base, and Optimism transactions cost pennies instead of dollars.","applicability":{"whenToUse":["Your product addresses: l2 transactions are expensive because of L1 data costs.","Your product addresses: l1 calldata competes with regular transactions.","The flow should deliver: blob space costs ~90% less, L2 txs drop to $0.01-0.10.","Fee screens need estimates, speed options, and plain-language breakdowns."],"whenToAvoid":["Clear network indicator: \"You're on Base (L2)\".","Monitor blob utilization, warn users during high usage.","Always show comparison or savings percentage.","Protocol plumbing is invisible and never surfaces in user-facing UI."]},"designerTakeaways":["You can design UI that delivers blob space costs ~90% less, L2 txs drop to $0.01-0.10.","You can design UI that delivers blobs have separate fee market.","You can design UI that delivers sub-penny fees make micro-transactions viable."],"problemsSolved":[{"problem":"L2 transactions are expensive because of L1 data costs","oldWay":"L2s post transaction data to L1 calldata at ~$0.50-5 per tx","newWay":"Blob space costs ~90% less, L2 txs drop to $0.01-0.10","impact":"critical"},{"problem":"L1 calldata competes with regular transactions","oldWay":"L2 batch posts compete for same gas, driving up all fees","newWay":"Blobs have separate fee market, don't affect regular txs","impact":"high"},{"problem":"Small transactions not economically viable on L2","oldWay":"$2 in fees for a $5 NFT mint makes no sense","newWay":"Sub-penny fees make micro-transactions viable","impact":"high"},{"problem":"L2 fee spikes during L1 congestion","oldWay":"When L1 is busy, L2 fees spike proportionally","newWay":"Blob fees have independent market, more stable L2 costs","impact":"medium"},{"problem":"Users confused about L2 vs L1 fee relationship","oldWay":"Hard to explain why L2 fees track L1 gas prices","newWay":"L2 fees mostly independent, easier to predict","impact":"medium"}],"uxPatterns":[{"name":"L2 Fee Display","description":"Show users how cheap L2 transactions are","mockup":"concept/one-click-swap","userFlow":["User initiates swap on L2","Fee shown prominently (it's impressively low)","Comparison to L1 shown for context","User confirms, pays fraction of a cent","Transaction confirms quickly"]},{"name":"Network Comparison","description":"Help users choose network based on cost","mockup":"concept/nft-gallery","userFlow":["User wants to mint/trade/interact","App shows available networks","Clear fee comparison displayed","Recommendation based on cost vs security tradeoffs","User selects cheapest suitable option"]},{"name":"Blob Fee Tracker","description":"Show current blob fee market status","mockup":"concept/gas-abstraction","userFlow":["User views fee dashboard","Sees L1 gas and blob gas separately","Understands blob utilization affects L2 costs","Can time transactions for lower fees"]},{"name":"Micro-Transaction UI","description":"Design for viable small transactions","mockup":"generic/list-selector","userFlow":["User wants to send small amount","Preset small amounts shown (now viable!)","Fee is fraction of tip amount","User sends micro-payment","Creator receives almost full amount"]}],"uiComponents":[{"name":"L2FeeDisplay","description":"Show L2 transaction fee with L1 comparison","states":["loading","cheap","moderate","expensive"],"props":["fee","feeUsd","l1Comparison","savings"]},{"name":"NetworkSelector","description":"Choose network with fee comparison","states":["loading","ready","selected"],"props":["networks[]","fees[]","recommended","onSelect"]},{"name":"BlobStatusIndicator","description":"Show blob space utilization","states":["low","moderate","high","full"],"props":["utilization","blobGas","trend"]},{"name":"MicroTxAmount","description":"Amount selector for small transactions","states":["selecting","selected","custom"],"props":["presets[]","minViable","fee","onSelect"]},{"name":"SavingsBadge","description":"Highlight fee savings vs L1","states":["minimal","good","great","amazing"],"props":["percentSaved","amountSaved","comparison"]}],"antiPatterns":[{"pattern":"Showing L2 fees without context","why":"\"$0.02\" means nothing without knowing L1 would be \"$2.00\"","instead":"Always show comparison or savings percentage","severity":"medium"},{"pattern":"Hiding which network user is on","why":"Users may think they're on L1 and be confused by low fees","instead":"Clear network indicator: \"You're on Base (L2)\"","severity":"high"},{"pattern":"Not recommending L2 when appropriate","why":"Users pay 100x more on L1 unnecessarily","instead":"Suggest L2 for transactions that don't need L1 security","severity":"medium"},{"pattern":"Designing for $5+ transaction fees","why":"L2 fees are often sub-cent, old patterns wasteful","instead":"Enable micro-transactions, small tips, frequent interactions","severity":"medium"},{"pattern":"Ignoring blob fee spikes","why":"When blob space is full, L2 fees can spike temporarily","instead":"Monitor blob utilization, warn users during high usage","severity":"high"},{"pattern":"Not explaining L1 vs L2 security tradeoffs","why":"Users should know L2 inherits security from L1 with delay","instead":"Explain when L1 is worth the cost (large amounts, long-term storage)","severity":"low"}],"onMonad":[{"aspect":"L2 Relationship","ethereum":"EIP-4844 reduces costs for L2s posting to L1","monad":"Monad is L1, doesn't post to Ethereum","designImplication":"Monad fees are its own thing, not affected by EIP-4844"},{"aspect":"Fee Predictability","ethereum":"Blob fees can be volatile based on L2 demand","monad":"Monad has its own fee market, typically stable and low","designImplication":"Different fee display patterns needed for Monad"},{"aspect":"Transaction Cost","ethereum":"L2 post-4844: $0.01-0.10 per tx","monad":"Native L1 with similar or lower costs due to parallelism","designImplication":"Can offer L2-like prices with L1 security on Monad"},{"aspect":"Micro-transactions","ethereum":"L2s via 4844 enable micro-tx use cases","monad":"Native micro-tx viability without L2 complexity","designImplication":"Build micro-tx UX patterns for Monad directly"}],"keyTakeaways":["EIP-4844 = cheap data posting = cheap L2 transactions","L2 fees dropped 90%+ after 4844","Always show fee context (comparison to L1)","Design for micro-transactions (they're viable now)","Monitor blob utilization for fee spikes"],"technicalNotes":"EIP-4844 introduces Type 3 (blob) transactions with up to 6 blobs of 128KB each. Blobs are only guaranteed available for ~18 days, not permanent. Blob gas has separate fee market from regular gas using EIP-1559 mechanism. Target is 3 blobs per block, max 6. L2s use blobs to post compressed transaction data instead of calldata."},"sources":[{"label":"Official specification","url":"https://eips.ethereum.org/EIPS/eip-4844","type":"official-spec"},{"label":"Discussion","url":"https://ethereum-magicians.org/search?q=EIP-4844","type":"discussion"}],"urls":{"canonical":"https://www.eipsfordesigners.com/standards/EIP-4844","markdown":"https://www.eipsfordesigners.com/standards/EIP-4844/content.md","agent":"https://www.eipsfordesigners.com/standards/EIP-4844/agent.md","api":"https://www.eipsfordesigners.com/api/standards/EIP-4844","official":"https://eips.ethereum.org/EIPS/eip-4844","discussion":"https://ethereum-magicians.org/search?q=EIP-4844"},"freshness":{"lastReviewed":"2026-04-05","lastUpdated":"2026-04-05"}}