Wrong network

KasWare and the PolicyVault server disagree on network — signing is disabled until this is fixed.

#Symptom

The dashboard shows a clear WRONG NETWORK state, and signing controls are disabled.

#Why this happens

PolicyVault checks that your wallet's currently selected Kaspa network matches the network this specific deployment is configured for, on every connection and on every network-change event inside your wallet. This deployment never guesses or silently retargets a request to a different network than what it's configured for — a mismatch is always shown plainly rather than allowed to proceed ambiguously.

Common cause: the hosted production deployment at https://app.policy-vault.org runs on Kaspa mainnet; a self-hosted development instance typically runs on testnet-10. If your wallet is set to the other network than the deployment you're using, you'll see this.

#What to do

1. Open KasWare and check which network is selected.
2. Switch it to match the deployment you're using — see Supported networks for which network a given deployment expects.
3. PolicyVault re-verifies network agreement automatically once you switch; signing controls re-enable once both sides agree.
4. Any request that was in progress when the mismatch occurred is discarded, not silently resumed — rebuild it after the network is corrected.

#What this protects against

Network confusion is a real risk with any blockchain application — a transaction meant for a test network accidentally signed against a real one (or vice versa) could have real consequences. Disabling signing entirely on a mismatch, rather than trying to "figure out what you meant," is a deliberate fail-closed choice.

See also: Connect KasWare, Supported networks.