datahaven-xyz/datahaven

An EVM compatible Substrate chain, powered by StorageHub and secured by EigenLayer

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 3 minutes ago
Added to GitGenius on September 8th, 2026
Created on March 6th, 2025
Open Issues & Pull Requests: 1 (+0)
GitHub issues: Enabled
Number of forks: 146
Total Stargazers: 7,895 (+0)
Total Subscribers: 28 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Issue API getrepoissuespagesummary failed: 429 Rate limit exceeded. Please try again later.

Detailed Description

DataHaven is a decentralized storage network built on an EVM-compatible Substrate chain that combines StorageHub infrastructure with EigenLayer's restaking security model.

The project addresses the need for verifiable, tamper-evident storage at production scale. It separates storage from verification by having Main Storage Providers store data off-chain while cryptographic commitments anchor on-chain. Files are chunked into 8KB segments, hashed into Merkle trees, and committed to the blockchain. Backup Storage Providers replicate data across the network for redundancy, with on-chain slashing penalties for failed proof challenges. Users can verify data integrity by checking Merkle proofs against on-chain commitments, and the validator set is secured through Ethereum restaking via EigenLayer operators.

The tool suits applications requiring cryptographically verifiable storage of training data, machine learning models, and Web3 assets. Its EVM compatibility through Frontier pallets enables familiar Ethereum tooling and smart contract development. The native trustless bridge to Ethereum via Snowbridge allows token and message transfers between chains. Teams should adopt this if they need production-grade decentralized storage with cryptographic proof of data integrity rather than trust-based alternatives, and if they can operate within the Substrate and EVM ecosystem.

The project maintains active development across multiple specialized components: the operator directory handles node building and runtime development, contracts manage smart contract logic, test covers end-to-end testing and network deployment, deploy provides Kubernetes orchestration, and tools supplies development utilities. The codebase is written in Rust and requires a substantial development environment including Kurtosis for network orchestration, Foundry for Solidity development, and Docker for containerization.