Summary: EthStorage is best cataloged not as a generic storage network, but as an Ethereum-native storage layer that tries to extend short-lived blob DA into long-lived application storage. Its reusable mechanism is a two-layer design: an Ethereum L1 storage contract handles fee distribution and Proof-of-Storage verification, while an es-node network stores offchain replicas and proves them over time. On top of that, EthStorage positions itself as programmable key-value storage with CRUD semantics and atomic application-plus-storage execution, which makes it a useful comparison class for Filecoin/Arweave-style static-file networks, EIP-4844-era long-term DA debates, and any system claiming fully onchain applications without paying raw SSTORE costs.
What it does:
Provides a storage contract on Ethereum L1 plus an L2 storage-provider network that stores replicas offchain and submits storage proofs back to L1
Lets application contracts store data through EthStorage so blob data can remain retrievable after Ethereum blob expiry, including for rollup and OP Stack use cases
Exposes programmable key-value storage semantics for dapps rather than only immutable static-file hosting
Claims smart contracts can manage storage logic directly, including access control and composability features, instead of treating storage as a detached content-addressed bucket
Aims to let application logic and storage logic execute in a single transaction, tightening the relationship between storage updates and contract state changes
Supports storage providers running es-node software and receiving storage fees after submitting valid storage proofs onchain
Key claims:
The official overview defines EthStorage as a modular and decentralized storage Layer 2 offering programmable key-value storage powered by DA, which is the clearest short description of its mechanism
The architecture docs split the system into two explicit layers: an L1 storage contract for fee distribution and Proof-of-Storage verification, and an L2 es-node network for replica storage and continuous DA sampling
EthStorage’s stated motivation is that EIP-4844 blob data is temporary, so rollups may lose unconditional ability to derive state from L1 alone after blob expiry; EthStorage positions itself as the long-term DA layer added on top
The docs say this can support rollups, fully onchain apps, dynamic websites, games, social apps, and AI use cases, which matters because the project is explicitly pitching itself as more than archival blob storage
The dapp guide says EthStorage offers KV CRUD semantics, smart-contract programmability, and atomic application-plus-storage execution in one transaction, contrasting itself with Filecoin/Arweave-style static-file systems where updates and deletes are awkward or effectively require re-paying for replacement data
EthStorage says storage fees are paid in ETH and can be around 1/100 to 1/1000 of SSTORE, which means the economic thesis is tightly coupled to Ethereum-native UX rather than to a separate storage token for end users
A current practical limitation is that mainnet storage-provider participation is still whitelisted during the initial launch phase, so the network’s present-day trust surface includes explicit operator gating even though the docs say it intends to become permissionless later
Whitepaper: No official whitepaper or standalone technical paper was found in the primary sources reviewed for this pass. See ../whitepapers/ethstorage-primary-sources-2026-05-09.md for the source trail used here.