Quick Start

Launch a testnet full node after completing Installation.

Native binary

Bootstrap an empty data directory from the official testnet genesis state:

miden-node bootstrap \
  --data-directory full-node-data \
  --network testnet

Start the full node and sync from the official testnet RPC endpoint:

miden-node full \
  --data-directory full-node-data \
  --rpc.listen 127.0.0.1:57291 \
  --network testnet

Docker image

Bootstrap an empty data volume from the official testnet genesis state:

docker run --rm \
  -v miden-full-node-data:/data \
  ghcr.io/0xmiden/miden-node:<release-tag> \
  miden-node bootstrap \
  --data-directory /data \
  --network testnet

Start the full node and sync from the testnet RPC endpoint:

docker run --rm --name miden-full-node \
  -v miden-full-node-data:/data \
  -p 127.0.0.1:57291:57291 \
  ghcr.io/0xmiden/miden-node:<release-tag> \
  miden-node full \
  --data-directory /data \
  --rpc.listen 0.0.0.0:57291 \
  --network testnet

The Docker port publish binds the RPC endpoint to 127.0.0.1 on the host. The node listens on 0.0.0.0 inside the container so Docker can route the mapped port.

Check the local RPC endpoint from another terminal:

grpcurl -plaintext localhost:57291 miden.node.v1.NodeService/Status

The -plaintext flag is required for the local full node RPC listener because it does not use TLS.

Replace testnet with mainnet or devnet in both commands to follow another official network, and select the appropriate <release-tag>. See Official Network URLs for public official network endpoints.