Provide Storage Overview

DataHaven depends on independent operators to keep replicas available and verifiable. This section is for teams that want to run storage nodes, starting with the Backup Storage Provider (BSP) role that backs up user data, answers proof challenges, and helps the network recover if a Main Storage Provider (MSP) goes offline.

Storage Provider Roles at a Glance

Type	Role	Core responsibilities	Selection	Incentives & risks
MSP	Primary provider for a bucket; the user's main point of contact for storing and retrieving files	Handles storing and retrieving files, anchors bucket roots on-chain, coordinates replication to BSPs	User-selected when creating a bucket	Earns storage fees; currently not polled or slashed, so reputation and market competition drive quality
BSP	Backup provider that stores replicas and proves data availability to the network	Stores replicas, maintains a global commitment of stored file keys, responds to periodic proof challenges, provides recovery if an MSP fails	Assigned by the network for redundancy	Earns rewards for durable replicas; can be slashed for missing proofs or losing data

What to Expect as a Storage Provider

• Register on DataHaven and bond BSP stake: Use the BSP signup flow on the DataHaven chain to post collateral; EigenLayer registration applies to validators, not BSPs.
• Stay reachable for replication and proofs: MSPs rely on BSPs to accept replication quickly; protocol challenges have deadlines.
• Plan for durability and bandwidth: Keep enough capacity to accommodate new replicas, and maintain consistent throughput to answer chunk-level challenges.
• Monitor network status: Review known issues and release notes so you understand current replication behavior and any temporary protocol limits.

Note

BSP replication availability can change during testnet iterations. Check Known Issues for the latest status before onboarding capacity.

Hardware Guidelines

Component	Baseline requirement
CPU	8 physical cores @ 3.4 GHz (Intel Ice Lake+ or AMD Zen3+)
RAM	32 GB DDR4 ECC
System storage	500 GB NVMe SSD (chain data)
User data storage	1 TB+ NVMe SSD or HDD (expandable)
Network	500 Mbit/s symmetric

• Keep chain data and user data on separate volumes for steadier I/O.
• Size --max-storage-capacity to roughly 80% of available disk so filesystems and temporary files have headroom.
• Plan for growth; expandable storage or dedicated cloud volumes work well when performance is consistent.

Next Steps

• Backup Storage Provider: Get Started

  Responsibilities, operational flow, and readiness checklist for running a BSP.

• End-to-End BSP Onboarding

  This tutorial takes you step-by-step through spinning up a BSP and verifying it on-chain.

Last update: January 21, 2026
| Created: September 18, 2025