EthStorage primary sources — 2026-05-09

Classification takeaway

EthStorage is best cataloged as Ethereum-native programmable storage and long-term DA infrastructure, not merely as another decentralized file store. The key reusable mechanism is its two-layer design: an Ethereum L1 contract verifies storage proofs and handles fees, while an es-node network stores replicas and keeps blob data retrievable after normal blob expiry. The main analytical value is that it pushes storage closer to Ethereum contract semantics through KV CRUD, programmability, and atomic application-plus-storage transactions.

Primary sources reviewed

1. Main site — https://ethstorage.io/

   • The homepage itself is not very extractor-friendly, but it confirms the official domain and product framing.
   • Most useful as a canonical root URL and for linking the broader project surface.

2. Docs overview — https://docs.ethstorage.io/

   • Clearest short definition of the project.
   • Says EthStorage is a modular decentralized storage L2 with programmable key-value storage powered by DA, motivated by long-term DA needs after EIP-4844 blob expiry.

3. How EthStorage Works — https://docs.ethstorage.io/readme/how-ethstorage-works.md

   • Core architecture page.
   • Defines the 2-part system: L1 storage contract for fee distribution and Proof-of-Storage verification, plus L2 es-node storage providers doing offchain replication and proof submission.

4. Storage Provider Guide — https://docs.ethstorage.io/storage-provider-guide.md

   • Best source for operator responsibilities and current trust assumptions.
   • Shows that providers store blob data, receive storage fees, and must provide proof of replication over time.
   • Also important because it states current mainnet mining is whitelisted during early launch.

5. Dapp Developer Guide — https://docs.ethstorage.io/dapp-developer-guide.md

   • Most important classification source after the architecture page.
   • Explains EthStorage’s pitch around Ethereum-native security, lower cost than SSTORE, KV CRUD semantics, programmability, ETH-denominated fees, and atomic application-plus-storage execution.

6. Official docs Q&A on mechanism — docs ask= interface over the above pages

   • Used to retrieve concise official summaries from the documentation itself for:
     • proof / pricing / long-term DA architecture
     • best pages for architecture and storage-provider roles
     • the core distinction versus static-file systems like Filecoin and Arweave
     • current whitelisting and mainnet participation constraints
   • Valuable here because the docs intentionally expose a doc-native query interface and the returned answers cite source pages.

7. GitHub org and repos — https://github.com/ethstorage ; https://github.com/ethstorage/es-node ; https://github.com/ethstorage/storage-contracts

   • Confirms the live implementation surfaces for node software and contracts.
   • Helpful for showing EthStorage is more than a conceptual docs project.

Whitepaper / technical-doc status

• No official standalone whitepaper or formal technical paper was found in the official site/docs sources reviewed during this pass.
• The docs are the main primary source today, especially the overview, architecture, dapp, and storage-provider pages.

Why it stays in the active corpus

• Provides a strong comparison class for long-term DA and fully onchain app claims after EIP-4844.
• Useful for separating static-file storage networks from Ethereum-native storage systems that promise CRUD semantics and transaction-level atomicity.
• Highlights an important current trust/control wrinkle: the project’s mechanism aspires to permissionlessness, but present-day mainnet storage-provider admission is still whitelisted.