Public testnet · chain 6913

Join the Testnet

Connect to live chain 6913: use the apps, run a peer node, or register as a validator. Day-to-day hosted traffic still uses a single validator path (not multi-region HA). Incentivized rewards are not running.

At a glance

RPC
https://testnet-rpc.boing.network/
Bootnode
/ip4/169.155.48.188/tcp/4001
Node release
testnet-v0.1.24 (or newer)
Wallet / SDK
Express 0.1.26 · @boing-network/boing-sdk@^0.5.41

Official listing JSON: /api/networks. Only one hosted bootnode — the old companion IP was retired.

Choose a path

Run a peer node (step by step)

Goal: your machine syncs chain 6913 from the hosted bootnode. You are not a validator yet — that is a separate registration step.

  1. Get the binary — download testnet-v0.1.24 (Linux example; Windows and macOS zips are on the same release page). Rename the platform binaries:
    curl -sSLO https://github.com/Boing-Network/boing.network/releases/download/testnet-v0.1.24/release-linux-x86_64.zip
    unzip release-linux-x86_64.zip
    mv boing-node-linux-x86_64 boing-node
    mv boing-linux-x86_64 boing
    chmod +x boing-node boing
    Prefer building from source? cargo build --release -p boing-node -p boing-cli — details in the validator guide.
  2. Start the node — listen for peers and dial the official bootnode:
    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
    Open inbound TCP 4001 in your firewall if you want others to connect to you. Keep RPC on localhost unless you intend to serve public JSON-RPC.
  3. Confirm sync — your head_height should track the public RPC:
    curl -s -X POST http://127.0.0.1:8545 -H 'content-type: application/json' \
      -d '{"jsonrpc":"2.0","id":1,"method":"boing_health","params":[]}'
    # Compare head_height with the public RPC at https://testnet-rpc.boing.network/
  4. Optional: validate — fund ~100+ BOING from the faucet, then follow Run a validator (Express Validate tab or boing validator register).

Deeper ops: RUNBOOK (PDF) · TESTNET-VALIDATOR-GUIDE.md · NODE-OPERATOR-COMMANDS.md.

Bootnodes

Bootnodes are the first peers your node dials. Public testnet currently publishes one hosted address (Fly boing-testnet-1). Full plain-language guide: Bootnodes.

/ip4/169.155.48.188/tcp/4001

Apps on this testnet

Same chain 6913. Activity may count toward your Testnet Passport — not a promise of tokens.

Developers: install @boing-network/boing-sdk@^0.5.41 (scoped package name). Hub quests: Community users · Developers.

Honest limits

  • Testnet only — mainnet (6914) is not live; no TGE date here.
  • Single hosted validator path for day-to-day public traffic (boing-testnet-1); not multi-region HA.
  • One official bootnode — do not use the retired boing-testnet-2 address.
  • No incentivized rewards until rules are published and marked live.
  • Testnet BOING has no cash value; the chain may reset.
  • Blocks idle when there are no transactions — a faucet request produces a block.

Prebuilt packages

/api/networks lists Windows, Linux, and macOS downloads plus a ready node_command_template (includes open-validator consensus flags for fresh sync).

Checking network listing…

Integrator contract ids (DEX, registries)

For app builders. Live truth is still boing_getNetworkInfo.end_user on the public RPC.

Canonical CP pool

0x5b60d6f8514d1a8a40340fa354951d778b0821cd3ff7e534d0bea50f67d38976

LP vault

0xac7a635931b192f5cff054e9994242f54fbda579a46eba21d9787600971ec90f

LP share token

0x2f460046eb700ff8c7eebe6f4c409465a9111f32210edcc478a2a0de9d0ec2db

Linked NFT ↔ token registry

0xebf9f0190f415852f90d0e60343126201248ab96273fdbf8acc5fe5fa03c3dd8

Builder attestation registry

0x734077a9f926077d39e84ec278b77b7b600c840f7101809646d8797a6a9e1816

Specs: RPC-API-SPEC · PDF

Docs