Supported networks
The Kaspa networks PolicyVault can run against, and how a deployment's network is fixed and verified.
PolicyVault distinguishes networks explicitly at every layer — network identity is never inferred or silently promoted.
Networks
| Network | networkId | Typical use |
|---|---|---|
mainnet | mainnet | Real value. The hosted production deployment at https://app.policy-vault.org runs here. |
testnet-10 | testnet-10 | Development and testing. The default for a self-hosted development instance. |
How a deployment's network is fixed
A PolicyVault server is configured with an explicit KASPA_NETWORK_ID and KASPA_RPC_URL — an unrecognized network id fails closed at configuration load time, and there is no default RPC endpoint a mainnet process could silently inherit from a testnet configuration.
The mainnet dual-flag unlock
Running against mainnet additionally requires two independent, explicit opt-ins at the configuration layer, plus an explicit RPC URL — mainnet is never something a deployment ends up on by omission or default. On mainnet, PolicyVault additionally refuses to start with test-only signing hooks or legacy creation paths enabled.
Network agreement is checked continuously, not just once
Before any live operation, PolicyVault verifies that its configuration, the specific request being made, the vault's own manifest, and the connected Kaspa node all agree on network identity. Your connected wallet (KasWare)'s selected network is checked against the server's configured network on every connection and every network-change event — a mismatch disables signing controls and discards any in-progress request rather than silently retargeting it to a different network. See Wrong network.
Address prefixes
Kaspa addresses carry a network-family prefix (kaspa: for mainnet, kaspatest: for the testnet family) — but a prefix alone cannot distinguish between testnet variants (for example, testnet-10 versus a hypothetical testnet-11), so PolicyVault treats the prefix as one additional check, never a replacement for the wallet-network-equals- server-network verification above.
See also: Connect KasWare, API versions.