Safe and timelock integration
Safe and timelock deployments are the first reference integration because many protocols already use them for privileged administration. Luvion adds an intent-bound authorization gate while preserving the partner's wallet, governance process, and delay mechanism.
Reference flow
upgrade or admin request
-> canonical Luvion intent
-> policy and separated approvals
-> threshold authorization certificate
-> reviewed adapter verifies the configured authorization proof
-> Safe module or timelock path enforces the exact operation
-> exact operation executes
-> receipt is bound into Luvion evidence
Verification profiles
| Profile | Off-chain verification | On-chain verification | Status |
|---|---|---|---|
| Safe module or timelock integration | Certificate and policy verification as defined by the selected adapter. | A reviewed verifier or explicitly trusted attestation bridge binds authorization to the exact call. | Reference design; the proof format, verifier and bypass closure must be selected and tested. |
| Lit/PKP upgrade Gate | Dedicated Lit Action validates the configured authorization request and produces a PKP signature. | Upgrade Gate checks PKP authorization, operation digest, delay and replay state. | Controlled path; the historical BSC Gate flow used a 1-of-1 sandbox certificate. |
| Public configuration demo | Service verifies controlled local FROST; local attestor signs the operation/certificate binding. | Gate checks issuer, operator and local-attestor signatures, current baseline and timing. | Local chain example; the Gate does not verify FROST directly. |
FROST Ed25519 certificates are not EVM-native transaction signatures. An adapter must state which evidence the chain verifies and which off-chain verifier it trusts. See the configuration example and versioned implementation records.
Enforcement options
- Safe module: the module verifies a Luvion certificate before it can call the protected target.
- Safe guard: a transaction guard adds checks to its covered transaction path. Review module execution separately and configure the applicable module guard or restrictions; installing one guard does not automatically cover every path.
- Timelock executor: the timelock or a dedicated executor verifies the certificate immediately before executing the queued operation.
- Protocol adapter: a protocol-specific contract validates the certificate for upgrade, signer rotation, mint/burn, or emergency calls.
Required properties
The verifier must bind the chain, target, calldata or structured parameters, policy version, authorization key epoch, validity window, and replay boundary. It uses fail-closed validation and consumption records to make each certificate single-use.
Current status
The current pilot produces canonical intents, policy decisions, approvals, threshold authorization certificates, and evidence. The next implementation target connects those capabilities to a reviewed onchain Safe module or timelock verifier and completes partner acceptance for production protection.
The first partner pilot should begin in shadow mode, compare the Luvion decision with the existing process, then move one testnet operation behind the verifier after the authority and bypass checklist is complete.