Platform administrative permissions
| Permission holder | Primary operations | Constraints | Disclosure |
|---|---|---|---|
| User AA Vault owner | Standard order execution, AA Vault upgrade authorization, deposits, and withdrawals | The owner address matches the Vault’s on-chain record, and upgrades also pass module validation | Query the Vault owner() |
| Diamond owner | Diamond facet updates, platform allowlists, and core configuration | Executes protocol configuration changes as a core governance permission | Owner address and governance method are published with deployment information |
| UUPS module owner | Upgrades BridgeModule, IssuanceModule, RedeemModule, and other modules | Most modules use the same governance boundary as the Diamond owner | Query proxy implementation addresses and upgrade events |
| SettlementPool owner | Configures assets, settlers, price bands, paused state, and inventory operations | Owner permissions operate with multisig custody, on-chain events, and monitoring | Addresses and governance thresholds are published with pool configuration |
| Cross-chain/redemption signer | Issues system signatures for controlled redemptions | Expiration, asset, amount, chain ID, replay protection, and allowance rules apply together | Signer configuration is published with the redemption mechanism |
User balances are recorded by on-chain contracts. Governance accounts use contract functions to perform upgrades, allowlist changes, and pool management; every operation generates an on-chain transaction and events. Jasper Vault will publish owner addresses, multisig thresholds, MPC custody methods, and governance delays alongside formal deployment information.