// the find
datahaven-xyz/datahaven
An EVM compatible Substrate chain, powered by StorageHub and secured by EigenLayer
DataHaven is a Substrate chain that bolt together three big upstream projects — StorageHub for decentralized storage, EigenLayer for validator security, and Snowbridge for trustless Ethereum bridging — to offer verifiable blob storage with on-chain Merkle commitments. Files are chunked, hashed into Merkle trees, roots anchored on-chain, and backup providers face slashing if they fail proof-of-custody challenges. It's aimed at Web3 applications that need tamper-evident data storage without trusting a centralized provider.
The proof-of-custody model is the right design: storage providers don't just promise to hold your data, they get slashed on-chain when they can't prove it, which is a real enforcement mechanism rather than wishful economics. Borrowing EigenLayer's restaked ETH for validator security sidesteps the cold-start problem of bootstrapping your own token's economic security from nothing. The two-tier provider split (MSPs for serving reads, BSPs for redundancy with slashing) maps cleanly to different failure modes. Dev tooling is genuinely well done — Kurtosis-based local network launcher, sccache + cargo-chef for build caching, type regeneration scripts — someone thought about the inner loop.
The dependency surface is brutal: Substrate, StorageHub (third-party), EigenLayer AVS contracts, Snowbridge, and Frontier EVM pallets are all large, fast-moving upstreams. A breaking change in any one of them cascades here, and the custom code in this repo is relatively thin on top of that integration pile. The 'AI-First' branding is trend-chasing — nothing in the architecture is AI-specific; it stores bytes with integrity proofs, which is useful for plenty of things but has nothing particular to do with training data beyond marketing copy. Getting a local environment running requires Docker, Kurtosis, Bun, Foundry, Rust, and optionally Zig — that's a high barrier before you've even confirmed the thing works. The slashing economics between EigenLayer validator slashing and StorageHub BSP slashing are two separate systems operating on different assets; the README doesn't explain what happens when they conflict or how the economic incentives actually balance at steady state.