Free 30-min Web3 Consultation
Book Consultation
Smart Contract Security Audits
View Audit Services
Custom DeFi Protocol Development
Explore DeFi
Full-Stack Web3 dApp Development
View App Services
Free 30-min Web3 Consultation
Book Consultation
Smart Contract Security Audits
View Audit Services
Custom DeFi Protocol Development
Explore DeFi
Full-Stack Web3 dApp Development
View App Services
Free 30-min Web3 Consultation
Book Consultation
Smart Contract Security Audits
View Audit Services
Custom DeFi Protocol Development
Explore DeFi
Full-Stack Web3 dApp Development
View App Services
Free 30-min Web3 Consultation
Book Consultation
Smart Contract Security Audits
View Audit Services
Custom DeFi Protocol Development
Explore DeFi
Full-Stack Web3 dApp Development
View App Services
decentralized-identity-did-and-reputation
Blog

The Unfunded Mandate of Eternal Data Availability

Networks like Arweave and Filecoin promise permanent storage, but their economic models cannot guarantee data retrieval decades from now. This is a fatal flaw for building critical, long-lived identity and reputation layers on-chain.

introduction
THE UNFUNDED MANDATE

Introduction

Blockchain's promise of permanent data availability is a core axiom that current economic models cannot sustain.

Data permanence is a subsidy. Blockchains like Ethereum and Solana guarantee data availability for state execution, but the one-time transaction fee does not fund perpetual storage. This creates an unfunded mandate where future network participants bear the cost of historical data.

The cost compounds silently. Unlike compute, which is ephemeral, storage costs accumulate linearly with chain age. Protocols like Arbitrum and Optimism push this cost to layer-1 Ethereum via calldata, merely deferring the economic problem.

Rollups externalize the true cost. The dominant scaling narrative assumes cheap, permanent L1 data. This reliance makes the entire modular stack dependent on Ethereum's social consensus to maintain data availability, not a sustainable economic one.

Evidence: Ethereum's historical data now exceeds 15TB. Storing this via decentralized providers like Filecoin or Arweave would cost millions annually, a cost not captured by gas fees paid years ago.

thesis-statement
THE UNFUNDED MANDATE

The Core Flaw

Blockchains promise permanent data availability but lack a sustainable economic model to pay for it.

The DA subsidy is unsustainable. Layer 2s like Arbitrum and Optimism pay for data availability (DA) on Ethereum, treating it as a variable operational cost. This creates a perpetual economic drain where sequencer profits are decoupled from the long-term cost of storing their state.

Rollups externalize their largest cost. The security model assumes Ethereum validators will forever store and serve this data, but the fee market only pays for short-term inclusion. This is a classic tragedy of the commons where the burden of historical data falls on a system not compensated for it.

Proof systems are not a panacea. Validity proofs from zkEVMs like zkSync verify state transitions, but they don't store the data needed to rebuild the chain. A prover with the only data copy becomes a centralized point of failure, negating decentralization guarantees.

Evidence: Ethereum's blob fee market is volatile. A single day of peak activity can cost an L2 like Base over $100k in DA fees, demonstrating the model's exposure to unpredictable, non-recoverable costs.

THE UNFUNDED MANDATE OF ETERNAL DATA AVAILABILITY

Economic Model Comparison: Storage vs. Retrieval

Comparing the economic incentives and guarantees for storing data versus the mechanisms for retrieving it, highlighting the misalignment that creates systemic risk.

Economic FeaturePure Storage (e.g., Arweave, Filecoin)Pure Retrieval (e.g., Arweave Gateways, Filecoin Retrieval Markets)Hybrid/Intent-Based (e.g., Lava Network, The Graph)

Primary Revenue Source

One-time storage fee + endowment

Pay-per-request fee

Staking rewards + usage fees

Incentive Horizon

200+ years (endowment model)

< 1 second (per request)

Variable (staking slashing periods)

Guarantee of Future Service

Mathematical endowment (theoretically perpetual)

None (market-driven availability)

Service-Level Agreement (SLA) staking

Data Retrieval Latency SLA

None

None (best-effort)

< 2 seconds (enforced by slashing)

Upfront Capital Requirement

High (endowment locked forever)

Low (pay-as-you-go)

Medium (stake to provide service)

Provider Churn Risk

Low (sunk cost)

High (no commitment)

Medium (slashing disincentivizes exit)

Censorship Resistance

High (data is permanently on-chain)

Low (gateways can filter/block)

Medium (decentralized provider set)

Example Protocol

Arweave

Arweave Gateway Ecosystem

Lava Network

deep-dive
THE UNFUNDED MANDATE

Why This Breaks Decentralized Identity

Decentralized identity systems fail because they assume permanent, low-cost data availability which contradicts blockchain economic realities.

Decentralized identity requires permanence. Systems like Verifiable Credentials and Soulbound Tokens store attestations on-chain, creating an infinite data liability. This liability is a perpetual cost that no single entity or protocol can guarantee to pay.

Blockchains are not archival databases. Layer 1s like Ethereum and rollups like Arbitrum prune state to manage costs. Identity data, which is rarely accessed, becomes a prime candidate for deletion under state expiry or high gas fee pressure.

The economic model is inverted. Users pay once to mint an identity, but the network bears the recurring cost of storing it forever. This creates a tragedy of the commons where the system's utility directly increases its eventual insolvency.

Evidence: The Ethereum Foundation's Purge roadmap explicitly aims to reduce historical data burden. Arweave exists precisely because general-purpose blockchains are economically unfit for permanent storage, yet identity protocols rarely integrate it by default.

counter-argument
THE UNFUNDED MANDATE

The Rebuttal (And Why It Fails)

The argument for permanent on-chain data availability is a moral hazard that externalizes costs onto future generations.

The 'Historical Data' Rebuttal is the primary defense: only new state needs DA, old data can be pruned. This is a cost-shifting fallacy. It assumes a permanent, altruistic archive like Arweave or Filecoin will always exist to serve historical proofs, creating a critical systemic dependency on an unpaid third party.

Pruning creates a time bomb. Protocols like Celestia and EigenDA explicitly design for pruning. A rollup that prunes its data outsources its liveness to external historians. This fragments security guarantees and reintroduces the very trust assumptions that modularity aimed to eliminate. The system's security decays over time.

Evidence from Ethereum's roadmap proves the point. Proto-Danksharding (EIP-4844) introduces blob storage with a ~18-day expiry. This is a deliberate economic policy, not a technical limitation. It forces rollups to implement their own long-term DA solution, passing the cost and complexity buck to individual application layers.

risk-analysis
THE UNFUNDED MANDATE

The Bear Case for DID Builders

Decentralized Identity systems promise user sovereignty, but their economic models fail to account for the permanent cost of data availability.

01

The Problem: Data is a Liability, Not an Asset

DID protocols store user credentials, attestations, and social graphs. This data must be perpetually available for the system to function, creating an infinite financial obligation. Unlike DeFi protocols where TVL generates fees, DID data is a pure cost center with no native revenue stream.

  • No Cash Flow: Storing a user's data doesn't generate protocol fees.
  • Infinite Time Horizon: Data must be available for decades, far beyond any VC runway.
  • Misaligned Incentives: Users expect free storage; builders bear the escalating cost.
∞
Time Obligation
$0
Native Revenue
02

The Solution: Subsidies & Rent Extraction

Builders are forced into unsustainable models, either relying on external capital or creating rent-seeking mechanisms that undermine decentralization.

  • VC Lifeline: Projects like Spruce ID and Disco rely on grants and venture funding to subsidize storage, a non-scalable model.
  • Centralized Pinata: Many "decentralized" profiles default to pinning data on IPFS via centralized gateways like Pinata or Infura, recreating points of failure.
  • Token Tax: The eventual "solution" is often a protocol token that taxes usage or mandates staking for node operators, adding friction.
100%
Subsidy-Dependent
Centralized
Default Fallback
03

The Verdict: Ethereum is the Only Viable Ledger

Permanent data availability is a public good that only a maximally decentralized and credibly neutral settlement layer can provide. Rollups and alt-L1s lack the social consensus for eternal guarantees.

  • Ethereum's Social Contract: The network's ~$1T+ economic security and long-term roadmap (including EIP-4844 blobs) make it the only plausible base for immutable data.
  • Alt-L1 Obsolescence: Storing core identity data on a chain that might not exist in 20 years is negligent.
  • Conclusion: True DID protocols must be Ethereum-native state. Everything else is a temporary experiment funded by depreciating venture capital.
$1T+
Base Security
Ethereum
Required Base
future-outlook
THE UNFUNDED MANDATE

The Path Forward: From Storage to Service

Eternal data availability is a public good problem that storage-first solutions cannot solve without a sustainable economic model.

Ethereum's consensus is the bottleneck. The core mandate for data availability layers is permanence, not just temporary storage. L1s like Ethereum treat data as a consensus resource, creating a permanent cost that rollups must subsidize indefinitely.

Storage is not a service. Projects like Filecoin or Arweave provide raw storage, but they lack the cryptoeconomic guarantees of a live consensus layer. Their models work for archiving, not for the real-time state proofs required by validity or fraud proofs.

The solution is a service abstraction. Protocols must treat data availability as a verifiable compute service, not a storage product. This shifts the economic model from paying for bytes to paying for a cryptographic proof of data persistence and retrievability.

Evidence: Celestia's modular design separates execution from consensus and data availability, creating a dedicated market for DA. EigenLayer's restaking introduces cryptoeconomic security as a service, allowing new DA layers to bootstrap trust from Ethereum validators.

takeaways
THE UNFUNDED MANDATE

TL;DR for Protocol Architects

Data availability is the silent, capital-intensive foundation for L2s and modular chains. The current model of paying per byte for eternity is a ticking time bomb.

01

The Celestia Fallacy

Celestia pioneered modular DA but created a pay-per-byte model that externalizes long-term costs. L2s today are building on a foundation of variable, unpredictable operational expense.

  • Costs scale linearly with usage, turning user growth into a financial liability.
  • Creates perverse incentives for sequencers to censor or reorder transactions to reduce DA fees.
  • No sunk-cost benefit: Every historical byte must be paid for, forever, with no amortization.
~$0.0005
Cost per KB (est.)
∞
Payment Term
02

EigenDA's Capital Lockup Gambit

EigenDA's restaking model attempts to solve the cost problem by using staked ETH as collateral for data availability. This trades recurring fees for systemic risk.

  • Shifts cost from OpEx to systemic risk via restaking slashing conditions.
  • Creates liquidity fragmentation as billions in LSTs are locked into a single provider's ecosystem.
  • Security ≠ Durability: A cryptoeconomic slashing event could invalidate historical data, breaking the chain of trust.
$10B+
TVL at Risk
~90%
Cost Reduction Claim
03

Avail's Proof-of-Sufficiency

Avail uses validity proofs (ZK) and data availability sampling (DAS) to create a verifiable, scalable DA layer. It's a technical improvement but still inherits the perpetual payment model.

  • ZK proofs reduce node resource requirements, enabling light clients and better scaling.
  • DAS allows secure sampling with a small subset of nodes, improving decentralization.
  • Core problem remains: Validators are still paid per block, creating an infinite operational tail for rollups.
~100K
TPS (Theoretical)
1 of 512
Sample Size (DAS)
04

The NearDA Arbitrage Play

NearDA exploits the fact that NEAR's sharded storage is a sunk cost. It offers DA as a marginal service on existing infrastructure, undercutting dedicated providers.

  • Leverages amortized storage costs from the NEAR protocol's core state.
  • Presents as a pure cost leader, with fees ~100x lower than Ethereum calldata.
  • Introduces new dependencies: DA security is now tied to the economic security and governance of the NEAR L1.
$0.001
Per MB (vs. ~$500 on Eth)
L1-Bound
Security Model
05

The Permanent Storage Endgame

The only escape from recurring fees is permanent, provable storage. This shifts the paradigm from 'renting' to 'owning' data shelf space.

  • Solutions like Filecoin's FVM, Arweave, and Bitcoin inscriptions offer one-time, perpetual storage.
  • Enables true cost predictability for protocol architects—a known upfront capital expenditure.
  • Trade-off is latency and finality: Retrieval is slower than hot DA layers, requiring hybrid caching architectures.
One-Time
Fee Model
~Minutes
Retrieval Latency
06

Architect's Mandate: Hybrid DA Stacks

The optimal solution is a layered approach. Use a hot, cheap DA layer (EigenDA, NearDA) for immediate consensus and a permanent ledger (Arweave, Filecoin) for final, immutable anchoring.

  • Hot Layer for Performance: Handles live sequencing and state derivation with low latency.
  • Cold Layer for Permanence: Provides a cryptographically assured, one-time-paid archive.
  • This bifurcation lets you optimize for both user experience and long-term fiscal sanity.
2-Layer
Strategy
>99%
Cost Savings (Long-Term)
ENQUIRY

Get In Touch
today.

Our experts will offer a free quote and a 30min call to discuss your project.

NDA Protected
24h Response
Directly to Engineering Team
10+
Protocols Shipped
$20M+
TVL Overall
NDA Protected Directly to Engineering Team