Spin Up Local Devnet¶

DataHaven can be run locally as a self-contained development network that mirrors the behavior of the full chain. Running a local devnet lets you experiment with core components without relying on external infrastructure. In this guide, you’ll learn how to spin up a local DataHaven node, which will allow you to go through the guides in the DataHaven docs as if you were using the testnet.

Prerequisites¶

Before you begin, ensure you have the following:

macOS or Linux operating system
Docker installed and running
Node.js ≥ 24 installed. LTS version recommended
pnpm installed for package management
Rust ≥ 1.86 installed
PostgreSQL installed
Diesel CLI installed for database management

Clone the StorageHub Repository¶

Start by cloning the official StorageHub repository, which contains all the scripts and Docker configurations required to spin up your local DataHaven devnet.

git clone https://github.com/Moonsong-Labs/storage-hub.git
cd storage-hub/test

Install Dependencies¶

Install all required dependencies using pnpm.

pnpm i

Pull Docker Images¶

Download the latest StorageHub and Main Storage Provider (MSP) backend Docker images. These images include prebuilt binaries and configurations for running the DataHaven node and MSP locally.

docker pull --platform linux/amd64 moonsonglabs/storage-hub:latest
docker tag moonsonglabs/storage-hub:latest storage-hub:local
docker pull --platform linux/amd64 moonsonglabs/storage-hub-msp-backend:latest
docker tag moonsonglabs/storage-hub-msp-backend:latest sh-msp-backend:local

Start the Local Devnet¶

With everything set up, start your local DataHaven devnet using the preconfigured solochain-evm script. This will launch a Substrate node with EVM compatibility and initialize the StorageHub runtime pallets.

pnpm docker:start:solochain-evm:initialised

Now you're ready to start building and testing with the StorageHub SDK against your local DataHaven devnet. You can use this setup to issue storage requests, create buckets, upload files, and more. The relevant local devnet configuration parameters (including Chain ID, RPC URL, WS URL, and MSP URL) can be found in the Starter Kit guide.

Note

Deleting files in the local devnet is currently not supported.

Stop the Local Devnet¶

To stop the local devnet, press Ctrl + C in the terminal where it's running.

After you stop running the solochain (local devnet) script, you should also manually remove all Docker containers.

To remove containers related to the devnet, you can run the following command in the terminal and then manually remove them by name or ID:

docker ps -a

If you want to remove all containers, you can run:

docker rm -f $(docker ps -a -q)

This command forces the removal of all running containers by listing their IDs with docker ps -a -q, then passing them to docker rm -f.

Last update: November 11, 2025
| Created: November 7, 2025