Five steps
- Install the CLI. Download the zip for your platform from the testnet-v0.1.13 release (
release-linux-x86_64.zip,release-macos-aarch64.zip, orrelease-windows-x86_64.zip), unzip it, and put theboing-<platform>binary on yourPATHasboing:# Linux example (macOS: release-macos-aarch64.zip / boing-macos-aarch64) curl -LO https://github.com/Boing-Network/boing.network/releases/download/testnet-v0.1.13/release-linux-x86_64.zip unzip release-linux-x86_64.zip chmod +x boing-linux-x86_64 && sudo mv boing-linux-x86_64 /usr/local/bin/boing boing token --helpOr build from source (Rust stable):
git clone https://github.com/Boing-Network/boing.network.git && cd boing.network && cargo build --release -p boing-cli(binary:target/release/boing). - Get a signing key. Create a wallet in Boing Express, then open the Reveal private key section at the bottom of the Wallet tab (password required) and set it only in your local shell:
Never commit it or paste it into chat. Use a dedicated testnet wallet.# PowerShell $env:BOING_SECRET_HEX = "<64-hex private key>" # bash/zsh export BOING_SECRET_HEX=<64-hex private key> - Fund it. Request testnet BOING from the faucet. A token deploy costs about 10–20 BOING, so you may need two requests (one every 60 seconds).
- Deploy a token.
The CLI prints your token address. Addboing --rpc-url https://testnet-rpc.boing.network token deploy --symbol TKN --name "My Token" --initial-supply 1000000--dry-runto see the signed transactions without sending them. - Verify.
Or look up the token address on Boing Observer. Transfer withboing --rpc-url https://testnet-rpc.boing.network token balance --token <token address> --holder <your address>boing token transfer --token … --to … --amount ….
Ways to create a token
- No code: the deploy wizard on boing.finance (Boing Testnet, signed with Boing Express).
- CLI:
boing token deploy, shown above. - TypeScript:
boing-sdkbuildReferenceFungibleDeployMetaTx(see the repositoryboing-sdk/README.md).
All three use the canonical reference fungible template (QA purpose token). The minimal template allows exactly one mint (fixed supply), and the first caller becomes admin. Details: repository docs/BOING-REFERENCE-TOKEN.md.
Other CLI commands
boing init: scaffold a dApp projectboing dev: start a local dev chain (RPC onhttp://127.0.0.1:8545)boing deploy: check RPC reachability before deployingboing token mint | transfer | balance | bytecode
RPC
Default port: 8545. Full method list and error codes: Documentation → RPC API (mirrors repository docs/RPC-API-SPEC.md). Use boing_health or boing_getNetworkInfo for chain id, limits, and developer.dex_discovery_methods. TypeScript: in-repo boing-sdk/ (see repo boing-sdk/README.md).
Crates (reference)
| Crate | Description |
|---|---|
boing-primitives | Types, hashing (BLAKE3), cryptography |
boing-consensus | PoS + HotStuff BFT |
boing-state | State store (sparse Merkle commitments; Verkle upgrade path in specs) |
boing-execution | VM + parallel scheduler |
boing-tokenomics | Emission and block-timing constants |
boing-automation | Scheduler, triggers, executor incentives |
boing-governance | Governance helpers for the protocol stack |
boing-telemetry | Logging and RPC telemetry helpers |
boing-qa | Deploy-time QA rules used by execution |
boing-cli | boing init, boing dev, boing deploy, boing token |
boing-p2p | libp2p networking |
boing-node | Node binary |
