Skip to content

Data Flow and Lifecycle

DataHaven separates storage from verification: storage providers hold the bytes, and the chain records a compact, verifiable receipt.

This page follows a file’s journey from choosing a Main Storage Provider (MSP) and bucket to uploading, policy-driven redundancy with Backup Storage Providers (BSPs), retrieval with an integrity check, and ongoing health checks. It also shows, at a high level, how updates create new versions and how you can move or remove data.

Roles at a Glance

  • User / Application: Initiates actions such as choosing an MSP, creating buckets, uploading files, and retrieving stored data.
  • DataHaven chain: Maintains compact on-chain commitments (bucket roots from MSPs, global roots from BSPs) and coordinates BSP challenges.
  • Storage Providers: DataHaven divides data storage, verification, and retrieval responsibilites across Main Storage Providers (MSP) and Backup Storage Providers (BSP). The two roles compare as follows:
MSP BSP
Chosen by the user. Randomly assigned by the network.
Maintains the bucket trie (primary copy). Replicates data across the network (backup copies).
Periodically anchors the bucket root on-chain. Periodically posts the global Merkle commitment of all stored files.
Serves files for read requests. Not part of the normal read path.
Performance is incentivized by competition to attract and retain users. Performance ensured via a slashing mechanism for failed proof challenges.

Now that you understand roles, you are ready to follow the step-by-step journey of data through the DataHaven lifecycle.

Connect and Choose Storage Providers

The first steps of the dataflow are as follows:

graph LR
    A[Connect wallet<br>or app identity]
    B[Select<br>an MSP]
    C[Create or reuse bucket<br>to hold files]
    D[Set policy for desired<br>BSP replicas]
    A-->B
    B-->C
    C-->D

Upload the File

Once you connect to the network, select your MSP, and create a bucket, the upload steps are as follows:

sequenceDiagram
    participant User/App
    participant MSP
    participant Offchain Storage
    participant BSP
    participant Blockchain

    User/App->>MSP: Open a storage request<br>for your bucket
    MSP->>Offchain Storage: Accept storage request,<br>Store the bytes off-chain
    MSP->>BSP: Coordinate replications<br>for backup copies
    BSP->>MSP: Confirm creation<br>of replica copies
    MSP->>Blockchain: Anchor Merkle-root<br>of bucket update

If replication or anchoring fails, the upload aborts.

Retrieve the File

The process to retrieve a file you successfully uploaded to DataHaven is as follows:

sequenceDiagram
    participant User/App
    participant MSP
    participant Blockchain

    User/App->>MSP: Requests the file
    MSP->>User/App: Returns the bytes plus<br>bucket root Merkle proof
    User/App->>Blockchain: Checks proof against<br>file's on-chain commitment
    Blockchain->>User/App: Confirms proof check passed,<br>returned data matches original upload

Verify Storage Over Time

Scheduled health checks, in the form of proof challenges, ensure BSPs retain your backup copies over time as follows:

sequenceDiagram
    participant Blockchain
    participant BSP

    Blockchain->>BSP: Sends proof of storage challenge as scheduled
    BSP->>Blockchain: Provides small cryptographic proofs in response

If the BSP returns the expected information, the health check passes. BSPs face slashing penalties in the event of data loss resulting in a failed proof challenge.

Change or Replace a File

The flow for changing or replacing a file is as follows:

graph LR
    A[Upload new content<br>to your bucket]
    B[Change to content creates<br>updated file fingerprint]
    C[Bucket updates on-chain<br>summary to reference<br>new version.]
    A-->B
    B-->C

It is important to note that whether older versions of files are retained is determined by your app's or storage provider's policy.

Next Steps

Now that you understand DataHaven's data storage lifecycle, consider these resources to get hands-on and start building.

Last update: November 6, 2025
| Created: October 17, 2025