Networks
SolidPeer serves four BCH networks. They're addressed in the URL path:
https://solidpeer.io/<system>/<network>/<token>
| Network | Purpose | Billing rate |
|---|---|---|
mainnet |
Production BCH chain | 1× CC per call |
chipnet |
Pre-activation test chain | 0.5× CC per call |
testnet4 |
Public testnet | 0.5× CC per call |
regtest |
Operator-controlled regtest | 0.5× CC per call |
Testnets and regtest cost half the mainnet rate. The discount applies at every charge site — reservations, commits, and cache-hit billing.
Network coverage per system
All four networks are available on all three systems:
- BCHN JSON-RPC: full node, all networks.
- Fulcrum (Electrum): indexed view, all networks.
- Chaingraph (GraphQL): indexed view, all networks. Mainnet chaingraph has a longer initial sync than the testnets; if you create your account before the indexer has caught up, mainnet GraphQL queries may return partial data.
Choosing a network
Use chipnet for integration testing against a chain shape close to mainnet. It activates protocol upgrades earlier than mainnet, so it's the right place to verify your code handles new features.
Use testnet4 for the same shape as mainnet with no real-money risk and free faucet-funded coins.
Use regtest for CI pipelines and local development — your tokens can call regtest just like the others, but blocks are mined on demand.
Use mainnet for production traffic.
Per-token network scope
When you mint a token you choose which networks it can reach. A token scoped to ["chipnet"] only routes to chipnet upstreams; calls to its mainnet URL return 403 network_not_allowed. Default scope is ["mainnet", "chipnet", "testnet4"] — regtest is opt-in.
Network status
Per-network upstream health is exposed at:
GET https://solidpeer.io/_status
This is a public endpoint — no authentication, no rate limit. Use it for a quick "is the upstream up?" check before issuing real traffic.