Luvion documentation
Luvion is building decentralized, high-threshold authorization infrastructure for critical digital asset operations. Its target network brings independently operated nodes, epoch-based dynamic committees, exact intent binding and separated approvals into one authorization path before execution.
The long-term scope includes protocol administration, asset issuance and institutional treasury and custody workflows. Luvion Protocol Guard is the first product: a pre-execution authorization control layer for critical onchain authority, starting with EVM upgrades and high-risk administrator operations. This is the initial product focus, not the limit of the network's design.
Current delivery is in controlled, non-production validation. See Current implementation status.
The core repository is private. See Source and documentation access for review and integration materials.
Start with an upcoming configuration change or a recent protocol upgrade. We prepare a short workflow draft from public or agreed non-sensitive material; your team can correct it asynchronously or in a 20-minute conversation. Together, we identify a concrete problem worth testing before scoping a pilot.
Review the current implementation
Start with one cross-chain configuration change. The walkthrough connects the interactive demo, selected source, exact checks and execution evidence. October validation records identify the reviewed core baseline and distinguish local checks from historical testnet runs.
Start here
- Watch product demos: eight short, real-client workflow walkthroughs with English and Chinese editions.
- What is Luvion? explains the overall goal, first product and problem it is intended to solve.
- Nodes, target network and economics explains operator independence, high-threshold authorization and the planned role of LUV in the formal network.
- How Luvion works follows one operation from intent creation to execution evidence, separately from the committee lifecycle.
- Protocol-upgrade example explains the current product workflow and its versioned validation boundaries.
- Start a controlled pilot explains scope, access to integration material and joint acceptance for one agreed workflow.
- 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
Luvion is building decentralized, high-threshold authorization infrastructure for critical digital asset operations.
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.