[ Vault Authorization Layer ]
[Independent transaction authorization]
The Vault
:: vault_authorize(tx)
:: execution_gate_active
The Vault acts as an independent authorization layer, evaluating transaction intent, policy, and risk before execution occurs — even if wallets, apps, or endpoints are compromised.
[ Authority lives outside the client ]
[Deployment]
One Vault. Two deployment models.
The Vault runs the same authorization engine in every environment. Only the execution context changes.
[Enterprise mode]
Automated, infrastructure-native.
- • Embedded directly into transaction flows, APIs, and backend systems.
- • Machine-to-machine authorization at execution time.
- • No human approval required.
- • Designed for platforms operating at scale.
[Public mode]
Independent authority for users and teams.
- • Hardware or secure software Vault.
- • Human-in-the-loop when required.
- • Independent of wallet providers.
- • Final authority outside the application layer.