{
  "id": 7898,
  "title": "EIP-7898: Uncouple execution payload from beacon block",
  "status": "Stagnant",
  "type": "Standards Track",
  "category": "Core",
  "summary": "This addresses a fundamental scalability bottleneck by separating transaction data from consensus data in Ethereum blocks. Currently, beacon blocks contain all transaction data embedded within them, but as Ethereum aims to increase block sizes (potentially by 10x), this creates serious networking and processing problems. Larger transaction payloads cause higher latencies for block transmission, increased bandwidth requirements, and longer block processing times that hurt validator performance. This EIP solves these issues by replacing the full transaction data in beacon blocks with just a header, while transmitting the actual transaction data separately. This allows the consensus layer to process blocks quickly while handling much larger transaction payloads independently. Additional benefits include reduced storage requirements for beacon nodes, more efficient proposer-builder separation, and laying groundwork for future innovations like ZK-proof-based execution validation where transaction data could be handled similarly to blobs with data availability sampling.",
  "impacts": [],
  "discussion_url": "https://ethereum-magicians.org/t/uncouple-execution-payload-from-beacon-block/23029",
  "source_markdown_url": "https://github.com/ethereum/EIPs/blob/master/EIPS/eip-7898.md",
  "canonical_url": "/latest/eips/7898.json",
  "markdown_url": "/latest/eips/7898.md",
  "citations": [
    {
      "recordId": "eip-7898",
      "artifactPath": "normalized/7898.json",
      "url": "/records/proposal/eip-7898/normalized/7898.json",
      "label": "EIP-7898: Uncouple execution payload from beacon block",
      "snippet": "This addresses a fundamental scalability bottleneck by separating transaction data from consensus data in Ethereum blocks. Currently, beacon blocks contain all transaction data embedded within them, but as Ethereum aims "
    }
  ]
}