Cross-chain configuration.
Bring the relevant teams into changes to trusted peers, receive contracts and critical configuration.
Inspect the configuration exampleCurrentProposed
20
32
Receive confirmations · same OApp
Decentralizedauthorization.
Coordinate approvals and enforce authorization for protocol upgrades, cross-chain configuration changes, and critical permissions.
Which changes need Luvion?
Start with changes that affect who can act, what can run, or which messages are trusted.
Protocol upgrades.
Bind the approval to the exact implementation address and initialization parameters.
See the upgrade checksCurrentProposed
A
B
Implementation address + upgrade parameters
Critical permissions.
Give changes to administrators, roles and authorization rules an explicit approval path.
Map the authority pathA shared decision. An exact operation.
01
Define the operation.
Agree on the details before authority changes hands.
Bind the target, parameters and validity window to one reviewable request.
Review the request02
Authorize together.
Bring separate approvals to the same operation.
Business approval and threshold authorization are distinct steps, each tied to the request.
Follow the authorization03
Keep the evidence.
Follow what was authorized through to its observed result.
Keep the proposal, approvals, authorization and execution evidence available for review.
Inspect the result
After integration, who holds control?
Keep the approval roles you need. Make the protected execution path explicit.
Do we keep our existing wallets?
Wallets and approvers keep their defined roles. Signing formats and execution routes need an adapter; Safe, AA and custody integrations require their own validation.
Which permissions change?
Give the protected upgrade or admin entry to the Gate or reviewed adapter. Inspect owner, delegate, role admin, modules and emergency routes before activation.
Who can change the Gate or policy?
In V3, Gate code and governance membership are fixed at deployment. Network recovery needs customer and recovery quorums plus a delay. Business-policy changes require coordinated review and configuration updates.
Can the former admin bypass it?
Only closing every alternate route makes the protected path mandatory. Retained owners, delegates, modules or emergency permissions can still bypass it; the permission migration must be tested.
Why an independent authorization network?
Business approval, authorization and evidence should have separate owners. Independence comes from different operators, key custody and failure domains.
Target network architectureIndependent verificationEach operator checks the request and its approval evidence.
Separate observationObservers hold no approval rights or signing shares.
Bring one critical operation.
Bring a past upgrade or configuration change. Together, we’ll map its authority path, reproduce the expected operation and a parameter substitution, and inspect the execution evidence.