Bootstrap Checklist (Local Dev)
This is the single “canonical” checklist for getting a working local setup:
trac-peer connected to that MSB network
subnet deployed and usable
demo tx executed and state query verified
It’s written to be copy/paste friendly and to remove ambiguity about “which value goes where”.
Values you need (fill these in)
Name
What it is
Where you get it
32-byte hex (64 chars) identifying the MSB network
From your MSB node logs//stats (often shown as msb.writerKey)
From your MSB node logs/config
discovery string for the subnet/app
you choose (e.g. my-app-v1)
32-byte hex join-code for the subnet
generated by peer1 and persisted to stores/<peer-store>/subnet-bootstrap.hex
Recommended defaults:
0) Install trac-peer
1) MSB: confirm the network parameters
On your already-running MSB node:
Confirm MSB is running and note:
Confirm you can fund a new address (you’ll do this for each peer) using MSB CLI (example):
If you don’t know how to run MSB locally, start with:
2) Start peer1 (creates the subnet)
Pick store names (so you can run multiple peers on one machine):
--msb-store-name=peer1-msb
Run:
Peer1 prints:
Peer MSB address: trac1... ← fund this on MSB
Peer pubkey (hex): ... ← used for subnet admin
Peer1 also creates (and persists) the subnet bootstrap join-code:
stores/peer1/subnet-bootstrap.hex
Read it with:
3) Fund peer1 on MSB (required for txs)
On your MSB funded/admin node, transfer TNK to peer1’s MSB address.
If peer1 is not funded, tx submission will fail with errors like:
Requester address not found in state
4) Deploy the subnet (one-time per subnet)
In the peer1 terminal:
This registers the subnet in MSB (so settlement and MSB preflight checks work).
5) Become subnet admin (recommended)
In peer1:
Verify:
6) Execute a demo contract tx (Tuxemon)
The demo app supports:
In peer1:
Read your tuxedex (unconfirmed is fine for dev):
7) Start peer2 (join the subnet)
Get SUBNET_BOOTSTRAP from stores/peer1/subnet-bootstrap.hex and run:
Fund peer2’s printed Peer MSB address on MSB as well.
8) Writers/indexers (optional for multi-writer subnets)
If your subnet is gated (default), peer2 may replicate reads but won’t be allowed to append writes unless admin approves it.
On peer2, get its writer key:
On peer1 (admin), add peer2:
Optionally also add it as an indexer:
If you want an open subnet instead:
9) Enable RPC (wallet/dApp connectivity)
Start a peer with HTTP RPC:
If you want wallets/dApps to be able to submit txs over HTTP, add:
Quick check:
Last updated
