Testnet · chain 6913
Single node vs multi-node
Pick one: a private local chain on your machine, or a node that joins the public testnet and syncs with everyone else.
1. Single node (local only)
Use when: you are developing on a laptop and do not need the live network.
Do not pass --p2p-listen or --bootnodes. Your machine is the whole chain.
./boing-node --rpc-port 8545 --data-dir ./data
# Optional: produce blocks locally
./boing-node --validator --rpc-port 8545 --data-dir ./data
RPC: http://127.0.0.1:8545/. This does not sync with https://testnet-rpc.boing.network/.
2. Multi-node (public testnet)
Use when: you want to peer with chain 6913, help soak the network, or become a validator later.
Pass --p2p-listen and the official --bootnodes address. Open inbound TCP 4001 if others should dial you.
export BOING_CHAIN_ID=6913
./boing-node \
--data-dir ./boing-data \
--p2p-listen /ip4/0.0.0.0/tcp/4001 \
--bootnodes /ip4/169.155.48.188/tcp/4001 \
--rpc-port 8545
Next: Bootnodes · Join Testnet — run a node · Become a validator
Quick comparison
| Single node | Public testnet peer | |
|---|---|---|
| Talks to other nodes | No | Yes (--p2p-listen) |
| Bootnode | Not needed | Required (--bootnodes) |
| Shares live chain history | No — your own chain | Yes — syncs with peers |
| Best for | Local dApp work | Operators and soak testing |