Add EIP: P2P History Network

[KolbyML]

This eip is a draft for the Portal History Network. A P2P network for historical data which is referenced in Ethereum's roadmap

[eth-bot]

File EIPS/eip-7719.md

Requires 1 more reviewers from @axic, @lightclient, @SamWilsn

[abcoathup]

Suggested change

	eip:
	eip: 7719

Assigning next sequential EIP/ERC/RIP number.

Please also update the filename.

[abcoathup]

Suggested change

	discussions-to: https://ethereum-magicians.org/t/add-eip-p2p-history-network/20231
	discussions-to: https://ethereum-magicians.org/t/eip-7719-p2p-history-network/20231

[kdeme]

Suggested change

	Instead of each Ethereum node storing a full copy of the block history, what if 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, well maintaining the current JSON-RPC interfaces.
	Instead of each Ethereum node storing a full copy of the block history, what if 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.

[SamWilsn]

Try to write your proposal as if it were already final. It's always weird when stuff like "will be" and "should be" sneaks into final proposals.

[SamWilsn]

Please include a license under which we can redistribute this PDF, or link to it externally. You can use the CSL-JSON format described in EIP-1:

Some text somewhere that needs a citation. [^1]

[^1]:
    ```csl-json
    {
      "publisher-place": "Berlin, Heidelberg",
      "abstract": "We describe a peer-to-peer distributed hash table with provable consistency and performance in a fault-prone environment. Our system routes queries and locates nodes using a novel XOR-based metric topology that simplifies the algorithm and facilitates our proof. The topology has the property that every message exchanged conveys or reinforces useful contact information. The system exploits this information to send parallel, asynchronous query messages that tolerate node failures without imposing timeout delays on users.",
      "author": [
        {
          "given": "Petar",
          "family": "Maymounkov"
        },
        {
          "given": "David",
          "family": "Mazi\u00e8res"
        }
      ],
      "container-title": "Peer-to-Peer Systems",
      "editor": [
        {
          "given": "Peter",
          "family": "Druschel"
        },
        {
          "given": "Frans",
          "family": "Kaashoek"
        },
        {
          "given": "Antony",
          "family": "Rowstron"
        }
      ],
      "type": "paper-conference",
      "DOI": "10.1007/3-540-45748-8_5",
      "id": "10.1007/3-540-45748-8_5",
      "citation-key": "10.1007/3-540-45748-8_5",
      "ISBN": "978-3-540-45748-0",
      "URL": "https://www.scs.stanford.edu/~dm/home/papers/kpos.pdf",
      "issued": {
        "date-parts": [
          [
            2002
          ]
        ]
      },
      "page": "53-65",
      "publisher": "Springer Berlin Heidelberg",
      "title": "Kademlia: A Peer-to-Peer Information System Based on the XOR Metric",
      "custom": {
        "additional-urls": [
          "https://link.springer.com/chapter/10.1007/3-540-45748-8_5",
          "https://users.cs.utah.edu/~stutsman/cs6963/public/papers/kademlia.pdf"
        ]
      }
    }
    ```

[KolbyML]

This PDF is no longer included directly in the EIP, because now we can link directly to the ethereum/portal-network-specs let me know what the best steps forward is on this

[KolbyML]

This PDF is no longer included directly in the EIP, because now we can link directly to the ethereum/portal-network-specs let me know what the best steps forward is on this

[KolbyML]

@SamWilsn ready for another look

[github-actions]

The commit 64aa993 (as a parent of 05a5276) contains errors.
Please inspect the Run Summary for details.