Target architecture and deployment profiles
Luvion's target architecture is an algorithm-neutral, high-threshold authorization network for critical onchain authority. Luvion Protocol Guard is the first commercial product built on that architecture.
This page describes the target protocol and its deployment profiles. It is not a claim that every component is already deployed or production-ready. Current evidence is tracked in the compatibility matrix and implementation status.
Architecture layers
| Layer | Responsibility |
|---|---|
| Authorization control plane | Canonical intent, policy evaluation, separated approvals, request state, and evidence export |
| Distributed authorization protocol | Committee selection, threshold signing, key epochs, refresh, reconfiguration, and recovery |
| Execution adapters | Safe, timelock, proxy, bridge, mint and burn, custody, or equivalent enforcement points |
| Evidence and verification | Authorization certificates, execution receipts, independent witnesses, and intent-execution matching |
Standard authorization path
Canonical Intent
-> Policy Evaluation
-> Separated Approvals
-> Dynamic Committee Selection
-> High-Threshold Authorization
-> Controlled Execution Handoff
-> Verifiable Evidence
In a controlled pilot, execution remains a controlled handoff. Mandatory or non-bypassable enforcement begins only after the target execution point verifies Luvion authorization and every alternate path for the same protected operation has been migrated, removed, or explicitly excluded from the protection claim.
Deployment profiles
| Profile | Purpose | Current evidence boundary |
|---|---|---|
| 3-of-5 pilot profile | Controlled design-partner validation | Demonstrated on controlled infrastructure; not an independent production network |
| 5-of-7 launch profile | Early multi-operator launch configuration | Authorization-certificate path tested; production operator independence and key custody remain gates |
| 22-of-33 high-assurance profile | Whitepaper reference for operations that cannot accept small-group control risk | FROST authorization-certificate path tested; not a live 33-node production network |
Thresholds remain configurable by operation risk. The 22-of-33 profile is a high-assurance reference, not a mandatory configuration for every customer.
Product wedge and expansion
Protocol Guard begins with EVM protocol upgrades and administrator-authority changes through Upgrade Guard and Admin Guard. The same authorization architecture can later extend to supply authority, bridge administration, emergency controls, and protocol treasury operations after each operation has an accepted policy, adapter, and enforcement boundary.