Connect KasWare
How wallet connection works, what network to use, and what to expect the first time you connect.
PolicyVault does not have its own login or account system separate from your wallet. Connecting a wallet is how you identify yourself to PolicyVault — there is no separate password or PolicyVault-specific account.
What you need
- The KasWare browser extension installed, with a wallet created or imported inside it. PolicyVault never sees your seed phrase or private key — KasWare holds those, entirely outside PolicyVault.
- The correct network selected inside KasWare, matching the PolicyVault deployment you are using (see Supported networks). The hosted production deployment at https://app.policy-vault.org runs on Kaspa mainnet. A self-hosted development instance typically runs on testnet-10.
Connecting
- Open the PolicyVault dashboard.
- Choose "Connect Wallet." PolicyVault calls KasWare's standard connection request; KasWare shows its own approval popup naming the site requesting access.
- Approve in KasWare. PolicyVault receives your active address and public key from KasWare — never a private key.
- PolicyVault checks that KasWare's selected network matches the network this deployment is configured for. A mismatch is shown clearly as WRONG NETWORK and disables signing controls until it is fixed — PolicyVault never silently retargets a request to a different network. See Wrong network.
Your OWNER identity in any vault you create is derived directly from your connected wallet's public key — you never type or paste a public key yourself for this. PolicyVault accepts ordinary Kaspa wallet addresses throughout its UI and derives the exact cryptographic representation the covenant requires internally.
What happens on account or network changes
- Switching accounts inside KasWare while a request is in progress discards that in-progress request. PolicyVault never reinterprets an old signature under a new account.
- Switching networks inside KasWare is re-checked immediately; signing controls stay disabled until the wallet and the server agree again.
- Disconnecting clears the session; PolicyVault keeps only convenience state (like your preferred provider) in the browser — actual vault state, requests, and history live in the durable backend and are re-read fresh whenever you reconnect or reload.
Only one signer is supported in production today
KasWare is the only production browser signer PolicyVault integrates with today. PolicyVault's signer boundary is generic (the "Universal Signer Interface") specifically so other signers — mobile wallets, hardware devices, air-gapped/offline signers — can be added without changing any funds-critical logic; an offline CLI signer reference already exists for non-browser flows. See What wallets and signers do.
Next: Create your first vault.