Owner

The wallet that creates and ultimately controls a vault.

The owner is the Kaspa wallet (keypair) that creates a vault and holds final authority over it. The owner's public key is compiled directly into the vault's covenant at creation — it is not a role assigned in a database, and it cannot be reassigned by editing application metadata.

What only the owner can do

What the owner does not need to do

The owner does not need to approve or be involved in every individual agent spend — that is the entire point of delegation. Once a policy is set, an agent can spend within it without further owner action, unless that specific spend requires approvals under the vault's own rules.

Owner identity in the app

The dashboard derives the owner field directly from your connected wallet's public key at the moment you create a vault — you never type or paste it. Application-level "roles" in an organization (Administrator, Treasurer, and similar labels) are separate, purely informational metadata; see Owner/agent/approver authority boundaries for why those labels never substitute for actual on-chain owner authority.

Losing owner access

If the owner's wallet key is lost, there is no PolicyVault-side recovery mechanism — nobody operating PolicyVault, hosted or self-hosted, can restore it. This mirrors ordinary Kaspa wallet custody: protect the owner's seed phrase the way you would protect any wallet holding funds.

See also: Owner recovery (recovering a vault's funds using the owner key), Agent/Delegate.