Merge pull request #3 from KolbyML/update-e2store

Update links from era2 to e2ss

README.md

@@ -1,13 +1,13 @@
 # Ethereum Historical Data Endpoints
 
-This page contains a **community-maintained list of Ethereum historical data endpoints**, including **Era1, Era, E2ss files, and torrents**.
+This page contains a **community-maintained list of Ethereum historical data endpoints**, including **Era1, Era, E2SS files, and torrents**.
 
 > ⚠️ This list should not be treated as a single source of truth for these endpoints, or the data they provide. It is a **community-maintained list**, and as such, some endpoints listed here may not be up to date, or may not provide the data they claim to be providing.
 
 Historical data providers offer **three primary storage formats**:
 - **Era1**(Pre-Merge) - Archive nodes providing **execution layer history** before The Merge (ETH1).
 - **Era**(Post-Merge) - Execution layer history **from The Merge onward**, including historical block data.
-- **E2ss**(State) - **State snapshots** for execution clients.
+- **E2SS**(State) - **State snapshots** for execution clients.
 - **Erb**(Blob) - Era file equivalent for blob sidecars [ ⚠️ Under Development ].
 
 This registry is designed to **reduce reliance on centralized providers** by creating a **publicly accessible, decentralized list of historical data sources**. It aligns with **EIP-4444** and **Portal Network** efforts to ensure that Ethereum clients can obtain block history **beyond what traditional p2p sync provides**.

endpoints/mainnet.yaml

@@ -21,7 +21,7 @@
       link: mailto:[email protected]
     - name: "@KolbyML"
       link: https://x.com/Kolby_ML      
-- endpoint: https://era2.ethportal.net
+- endpoint: https://e2ss.ethportal.net
   name: EF DevOps
   format: e2ss
   torrent: false

index.md

@@ -2,14 +2,14 @@
 layout: default
 ---
 
-This page contains a **community-maintained list of Ethereum historical data endpoints**, including **Era1, Era, E2ss files, and torrents**.
+This page contains a **community-maintained list of Ethereum historical data endpoints**, including **Era1, Era, E2SS files, and torrents**.
 
 > ⚠️ This list should not be treated as a single source of truth for these endpoints, or the data they provide. It is a **community-maintained list**, and as such, some endpoints listed here may not be up to date, or may not provide the data they claim to be providing.
 
 Historical data providers offer **three primary storage formats**:
 - **Era1** [Spec](https://github.com/ethereum/go-ethereum/pull/26621#issue-1573139029) - Execution layer historical block data **before The Merge**.
 - **Era** [Spec](https://github.com/status-im/nimbus-eth2/blob/613f4a9a50c9c4bd8568844eaffb3ac15d067e56/docs/e2store.md#era-files) - Consensys layer historical block data **from The Merge onward**.
-- **E2ss** [Spec](https://github.com/ethereum/trin/blob/62dd518a88eda8496f89db9f9c149231a2c326dc/e2store/src/era2.rs#L24-L37) - **State snapshots** for execution clients.
+- **E2SS** [Spec](https://github.com/ethereum/trin/blob/f0187cbddd2a8a6d3ebaefa250dd6136fb5816cb/crates/e2store/src/e2ss.rs#L1-L26) - **State snapshots** for execution clients.
 - **Erb** [Spec](https://github.com/status-im/nimbus-eth2/pull/5882) - Era file equivalent for blob sidecars [ ⚠️ Under Development ].
 
 This registry is designed to **reduce reliance on centralized providers** by creating a **publicly accessible, decentralized list of historical data sources**. It aligns with **EIP-4444** and **Portal Network** efforts to ensure that Ethereum clients can obtain block history **beyond what traditional p2p sync provides**.