Luvion documentation
Luvion is the non-bypassable distributed authorization infrastructure for critical onchain authority. Its first product, Luvion Protocol Guard, protects privileged operations such as upgrades, signer rotation, minting, burning, bridge administration, and emergency controls. When Protocol Guard is integrated as the required execution path and alternate authority paths are closed, those operations must pass through an intent-bound, high-threshold authorization path before execution.
We're looking for three teams to validate one critical workflow with Luvion. Selected partners receive a free, scoped non-production pilot. Up to two qualifying partners may receive a lifetime waiver of base software licence fees within an agreed scope.
Start here
- 15-minute quickstart runs the controlled local pilot and produces a sanitized acceptance report.
- What is Luvion? explains the product category and the problem it is intended to solve.
- How Luvion works follows one operation from intent creation to execution evidence.
- Protected operations defines the first operation types and why they are the initial product wedge.
- Compatibility matrix is the source of truth for what is validated, interface-only, reference design, or research.
- Target architecture and deployment profiles preserves the complete whitepaper architecture and separates pilot, launch, and high-assurance configurations.
- Dynamic committees and key lifecycle covers committee selection, rotation, proactive refresh, reconfiguration, DKG, key epochs, and coordinator failover.
- Cryptographic backends separates the current FROST path from algorithm-neutral interfaces and ML-DSA research.
- Authorization evidence and witnesses defines certificates, execution receipts, independent witnesses, and rollback detection.
- Trust boundaries separates the control plane, signer domains, execution, evidence, and alerting responsibilities.
- Safe and timelock integration describes the first reference enforcement design and its current implementation boundary.
- Optional Lit and PKP backend explains the validated optional backend and its limited role in the Luvion architecture.
- Design-partner pilot defines a reusable, non-production validation package.
- Security boundary defines the deployment conditions for mandatory protection.
- Current implementation status separates tested pilot capabilities from target protocol features.
- Protocol objects defines the versioned records that bind policy, authorization, execution, and evidence.
- Release evidence connects pilot claims to a source revision, automated gates, and explicit evidence gaps.
- Failure recovery defines fail-closed response rules for signer, adapter, witness, alert, and host failures.
- Events and webhooks documents the durable operational alert contract and its current boundary.
The short version
When integrated as the required execution path, Luvion makes protected critical onchain authority impossible to exercise without explicit, distributed, and verifiable authorization.
Luvion combines exact intent binding, versioned policy checks, separated approvals, high-threshold distributed authorization, mandatory execution enforcement, and independently verifiable evidence into one control layer.