What Bitcoin Doesn’t Have but Ethereum Does: The Real Meaning of Receipts and Blobs

-

※ This article is published in its current form first and will be updated to the final Daily Crypto Times (DCT) format in two days.

What Bitcoin Doesn’t Have but Ethereum Does: The Real Meaning of Receipts and Blobs

Vitalik Buterin sought to extend Satoshi Nakamoto’s Bitcoin network by adding a general-purpose computing layer capable of executing smart contracts. To achieve this, he moved beyond Bitcoin’s UTXO model and adopted an account-based architecture, creating what is now known as a “second-generation blockchain.” As a result, Ethereum became significantly more complex than Bitcoin, with a fundamentally different internal data-processing structure.

It is highly recommended to read the following two articles first, as they provide essential background for understanding this topic:
1) Bitcoin‑Style Competition Among Ethereum Builders: A Complete Guide to the ePBS Architecture
2) The Truth Behind the L2 Scaling Debate: Why Rollup‑First Is the Best Path Today

These two articles provide important context for understanding Ethereum’s block production pipeline and its L2 scaling strategy. Building on that foundation, this article focuses on two structural elements that highlight how Ethereum differs from Bitcoin: the Receipt mechanism, which enables verification of smart contract execution, and the Blob data architecture, which supports L2 scalability. Together, these components reveal why Ethereum chose a fundamentally different design path and offer insight into whether the second-generation blockchain model is truly successful. While the topic may be challenging for general readers, this article aims to explain it as clearly as possible.

Most people understand a blockchain as “a chain of blocks composed of a block header and a block body.” In Bitcoin, when a new block is created, only that block needs to be propagated across the network.

Ethereum, however, is far more complex. In Ethereum’s block validation process, not only the block header and block body but also a separate data structure called Receipts must be propagated and verified.

Receipts are generated alongside the transaction list when a block is created, and the block header stores a summary of them called the receiptsRoot. To validate a block, validators must verify not only the header and body but also the entire execution results contained in the Receipts.

Additionally, Blob data (EIP‑4844) submitted by L2 rollups must be stored long‑term by L2 sequencers, DA layers, or other nodes, separately from the L1 blockchain. Understanding this structure is essential to grasp how Ethereum validates execution and how its Rollup‑based L2 scaling model works.

1) Where Receipts Appear in the Full Block Pipeline

Ethereum’s block production pipeline proceeds as follows:

  • User: Sends a transaction to the network.
  • Builder: Executes the transaction in the EVM and produces both the block body (transaction list) and the Receipts.
  • Proposer: Selects the builder’s block and broadcasts it to the network.
  • Validators: Re‑execute the transactions and compare their computed receiptsRoot with the one stored in the block header.

The key point is that the block body and Receipts are separate data structures.

  • Block Body: Contains only the list of transactions.
  • Receipts: Contains the execution results of each transaction (success/failure, gas used, event logs, internal calls, etc.).

The block header stores only the receiptsRoot, not the full Receipts. Validators use this root to confirm that the execution results have not been tampered with.

2) Why Ethereum Must Have Receipts

Bitcoin’s UTXO model allows validation by simply checking whether the final result is correct. Ethereum, however, is a smart‑contract platform, and its execution process is far more complex.

A single transaction may involve:

  • Multiple contract calls
  • Internal transactions
  • Event logs
  • Gas consumption
  • Success or failure

Much of this execution data is not stored in the state. Receipts are the only structure that records:

  • Event logs
  • Gas usage
  • Success/failure status
  • Internal call information

Because of Receipts, block explorers (like Etherscan), indexing services (like The Graph), and wallet applications can display accurate information. Most importantly, the receiptsRoot in the block header summarizes the entire execution result, making it essential for block validation.

3) Why Blobs and Receipts Are Completely Different

Blob data (EIP‑4844) and Receipts may appear similar because both store only a summary on L1, but their purpose and retention model are entirely different.

Blob Data — For L2 Data Availability

  • Large data batches submitted by L2 rollups.
  • L1 stores only the commitment.
  • Blob contents are deleted after a period.
  • Long‑term storage is handled by L2 sequencers, DA layers, or archive nodes.

Receipts — For L1 Execution Verification

  • Store transaction execution results and event logs.
  • L1 stores the receiptsRoot permanently.
  • Receipts are preserved long‑term by nodes and indexers.

Summary Comparison

Category Blob Data Receipts
Purpose L2 data availability L1 execution verification
Retention Temporary, deletable Long‑term external storage
L1 Storage Blob commitment receiptsRoot
Data Type Large L2 data batches Structured execution results

Conclusion

Understanding Ethereum as merely “a chain of block headers and block bodies” is not enough to explain the existence of Receipts and Blob data.

Ethereum’s architecture is more complex: Receipts provide permanent proof of L1 execution, while Blobs support scalable L2 data availability.

Recognizing the roles of these two components clarifies how Ethereum aims to maintain a secure L1 while enabling scalable L2 expansion.

Younchan Jung
Researcher exploring structural shifts in AI, blockchain, and the on‑chain economy.

If you would like to read this article in Korean, please click the button below.

댓글

댓글 쓰기

이 블로그의 인기 게시물

Ethereum’s Quiet Takeover: How Stablecoins and Tokenized Assets Are Rewriting Global Finance

-
이미지
Ethereum’s Quiet Takeover: How Stablecoins and Tokenized Assets Are Rewriting Global Finance In 2026, the global financial system is undergoing a profound transformation—quiet on the surface, but seismic underneath. At the center of this shift is Ethereum . Once viewed simply as a smart‑contract platform, Ethereum has now become the settlement and liquidity backbone of global finance, reshaping the very structure of how money and assets move. How Ethereum Became the Foundation of Global Finance Stablecoin payments and real‑world asset tokenization (RWA) are expanding faster than ever. What’s striking is that this movement is no longer led by crypto startups. Instead, Visa, Stripe, PayPal, JPMorgan, BlackRock, and Fidelity —the world’s largest financial institutions—are building new financial infrastructure directly on Ethereum. Recent on‑chain data highlights the scale of this shift: Tokenized funds: 31,300 holders Tokenized equities: 21,000 holders Tokenized commodities: 11...
자세한 내용 보기

The Real Reason the CLARITY Act Stalled: A USDC Yield War Between Coinbase and the Banks

-
이미지
3-Point Summary The CLARITY Act stalled not because of regulators, but due to internal industry conflict. The core battle centers on whether stablecoins like USDC should be allowed to generate yield. Coinbase’s opposition to a yield ban significantly weakened political momentum for the bill. The CLARITY Act stalled because the industry itself couldn’t agree on who controls the economics of digital dollars. 50-Second Shorts Video '" style="cursor: pointer; position: relative; width: 100%; aspect-ratio: 1/1; border-radius: 8px; overflow: hidden;"> Watch the 50-second video to understand why the CLARITY Act stalled before diving into the full analysis below. Why the CLARITY Act Stalled: Not Regulation, but an Internal War 1) What the CLARITY Act Was Trying to Do The CLARITY Act is...
자세한 내용 보기

비트코인은 자산, 이더리움은 인프라: 기관이 다시 짜는 글로벌 금융의 판도

-
이미지
비트코인과 이더리움—같은 기관 채택, 완전히 다른 두 개의 트랙 기관들의 암호자산 채택 속도가 눈에 띄게 빨라지고 있다. 하지만 이 흐름 속에서 비트코인과 이더리움이 맡고 있는 역할은 근본적으로 다르다. 비트코인은 기관의 포트폴리오에 편입되는 ‘보유 자산’ 으로 자리 잡고 있고, 이더리움은 글로벌 금융 시스템이 다시 구축되는 ‘운영 인프라’ 로 기능하고 있다. 이 둘은 경쟁 관계가 아니라, 새로운 금융 아키텍처를 구성하는 두 개의 기둥이다. 1. 비트코인: 기관이 ‘보유하는 자산’ 최근 블랙록이 단 10거래일 만에 17,645 BTC(약 11억 6천만 달러) 를 매수한 사실은 시장의 시선을 사로잡았다. 이는 채굴자들이 생산하는 속도보다 더 빠르게 비트코인을 흡수하는 수준이다. 기관들이 비트코인을 반드시 보유해야 하는 자산 으로 인식하고 있다는 강력한 신호다. 비트코인이 기관 포트폴리오에서 차지하는 의미는 명확하다. ETF 운영을 위한 재고 확보 블랙록의 IBIT 현물 ETF는 투자자 수요를 충족하기 위해 대량의 BTC를 보유해야 한다. 기관 고객에게 제공하는 규제된 비트코인 접근성 연기금, 보험사, 국부펀드 등은 직접 보관 리스크 없이 비트코인에 노출되기를 원한다. 디지털 금으로서의 포지셔닝 래리 핑크는 비트코인을 글로벌 거시 자산, 가치 저장 수단, 인플레이션 헤지로 규정해 왔다. 장기적 희소성에 대한 선제적 대응 블랙록의 공격적 매수는 희소 자산을 조기에 확보하려는 전형적인 기관 전략이다. 결국 비트코인은 금고에 보관되는 자산 , 즉 디지털 금이다. 기관은 비트코인을 ‘운영’하지 않는다. 보유한다. 2. 이더리움: 금융 자산이 실제로 ‘움직이는 인프라’ 이더리움은 완전히 다른 질문에 답한다. “금융 자산은 어디에서 발행되고, 이동하고, 결제되고, 운영될 것인가?” 기관들은 ETH를 단순히 사들이는 것이 아니라, 이더리움 위에 금융 시스템을 구축하고 있다. 대표적인 사례는 다음과 같다. JP Morgan — Onyx, JPM C...
자세한 내용 보기