Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add EIP: P2P History Network #8630

Open
wants to merge 7 commits into
base: master
Choose a base branch
from
+44 −0
Open

Add EIP: P2P History Network #8630

Changes from all commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
7f5e323
Add EIP: P2P History Network
KolbyML Jun 7, 2024
701a96e
7719: fix
KolbyML Jun 7, 2024
b79aa67
7719: fix
KolbyML Jun 7, 2024
d9d372f
7719: fix
KolbyML Jun 7, 2024
f5d8af8
7719: fix
KolbyML Jun 7, 2024
befbfd2
7719: fix
KolbyML Jul 26, 2024
64aa993
7719: update spec link
KolbyML Jul 31, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
44 changes: 44 additions & 0 deletions EIPS/eip-7719.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,44 @@
---
eip: 7719
title: P2P History Network
description: Instead of each node storing a full copy of historical history divide the responsibility amongst the nodes on the network.
author: Kolby ML (@KolbyML)
discussions-to: https://ethereum-magicians.org/t/eip-7719-p2p-history-network/20231
status: Draft
type: Standards Track
category: Networking
created: 2024-06-05
requires: 7643, 7718

Check failure on line 11 in EIPS/eip-7719.md

View workflow job for this annotation

GitHub Actions / EIP Walidator

unable to read file `eip-7718.md`: Io: JsValue(Error: ENOENT: no such file or directory, open 'EIPS/eip-7718.md' Error: ENOENT: no such file or directory, open 'EIPS/eip-7718.md' at async open (node:internal/fs/promises:636:25) at async readFile (node:internal/fs/promises:1246:14)) 

error[preamble-requires-status]: unable to read file `eip-7718.md`: Io: JsValue(Error: ENOENT: no such file or directory, open 'EIPS/eip-7718.md'
Error: ENOENT: no such file or directory, open 'EIPS/eip-7718.md'
    at async open (node:internal/fs/promises:636:25)
    at async readFile (node:internal/fs/promises:1246:14))
  --> EIPS/eip-7719.md:11:16
   |
11 | requires: 7643, 7718
   |                ^^^^^ required from here
   |
   = help: see https://ethereum.github.io/eipw/preamble-requires-status/
---

## Abstract

An overlay network over Discv5 based off the _Portal Wire Protocol_ [EIP-7718](./eip-7718.md). This overlay network is called the Portal History Network and serves headers, block bodies, and receipts. Look ups on the network are done via block hash. All data has strong validity conditions, but proving path will differ based certain fork transitions.

Check failure on line 16 in EIPS/eip-7719.md

View workflow job for this annotation

GitHub Actions / EIP Walidator

unable to read file `eip-7718.md`: Io: JsValue(Error: ENOENT: no such file or directory, open 'EIPS/eip-7718.md' Error: ENOENT: no such file or directory, open 'EIPS/eip-7718.md' at async open (node:internal/fs/promises:636:25) at async readFile (node:internal/fs/promises:1246:14)) 

error[markdown-link-status]: unable to read file `eip-7718.md`: Io: JsValue(Error: ENOENT: no such file or directory, open 'EIPS/eip-7718.md'
Error: ENOENT: no such file or directory, open 'EIPS/eip-7718.md'
    at async open (node:internal/fs/promises:636:25)
    at async readFile (node:internal/fs/promises:1246:14))
  --> EIPS/eip-7719.md
   |
16 | An overlay network over Discv5 based off the _Portal Wire Protocol_ [EIP-7718](./eip-7718.md). This overlay network is called the Portal History Network and serves headers, block bodies, and receipts. Look ups on the network are done via block hash. All data has strong validity conditions, but proving path will differ based certain fork transitions.
   |
   = help: see https://ethereum.github.io/eipw/markdown-link-status/

Check failure on line 16 in EIPS/eip-7719.md

View workflow job for this annotation

GitHub Actions / EIP Walidator

unable to read file `eip-7718.md`: Io: JsValue(Error: ENOENT: no such file or directory, open 'EIPS/eip-7718.md' Error: ENOENT: no such file or directory, open 'EIPS/eip-7718.md' at async open (node:internal/fs/promises:636:25) at async readFile (node:internal/fs/promises:1246:14)) 

error[markdown-refs]: unable to read file `eip-7718.md`: Io: JsValue(Error: ENOENT: no such file or directory, open 'EIPS/eip-7718.md'
Error: ENOENT: no such file or directory, open 'EIPS/eip-7718.md'
    at async open (node:internal/fs/promises:636:25)
    at async readFile (node:internal/fs/promises:1246:14))
  --> EIPS/eip-7719.md
   |
16 | An overlay network over Discv5 based off the _Portal Wire Protocol_ [EIP-7718](./eip-7718.md). This overlay network is called the Portal History Network and serves headers, block bodies, and receipts. Look ups on the network are done via block hash. All data has strong validity conditions, but proving path will differ based certain fork transitions.
   |
   = help: see https://ethereum.github.io/eipw/markdown-refs/

## Motivation

Historical blocks and receipts currently occupy more than 700GB of disk space (and growing!). Therefore, to validate the chain, users must typically have a 2TB disk.

With lightweight sync strategies based on the PoS weak subjectivity assumption, which was possible after the merge, storing all the block history was no longer required to sync and played a centralizing force increasing the storage requirements and sync times to participate in the Ethereum Network.

Instead of each Ethereum node storing a full copy of the block history, imagine that this burden was divided amongst all nodes enabling each node to store a fraction of the blocks, but having access to all historical blocks as a collective lowering the cost for everybody, while maintaining the current JSON-RPC interfaces.

## Specification

Specification of the _Portal History Network_ are on [ethereum/portal-network-specs](https://github.com/ethereum/portal-network-specs/blob/bc7f4d0d930f79a610f54ab3160bd3ee93e92cae/history/history-network.md).

## Rationale

Block history look up's are optimized for contacting the least amount of nodes and to obtain single pieces of history. Models for doing bulk downloads of block history are being researched, for the majority of post [EIP-4444](./eip-4444.md) optimizing for faster single block look up times is considered more important.

Validation for block headers will use different proving paths depending which block range they are from. For pre-merge headers the embedded accumulator of [EIP-7643](./eip-7643.md) is used for header validation, for merge till capella _HistoricalRootsBlockProof_ the frozen accumulator in the beacon state is used, but can be embedded in the client as well. For Capella onwards minus 8192 blocks _HistoricalSummariesBlockProof_ the accumulator in the beacon state is used. The latest 8192 blocks are already contained by the EL and CL node which can be used to validate that the headers are valid.

TBD <!-- TODO -->

## Security Considerations

Needs discussion. <!-- TODO -->

## Copyright

Copyright and related rights waived via [CC0](../LICENSE.md).
Loading