Choose your guardians
Register a recovery group and the number of guardian authorizations required. The threshold is an explicit part of the identity’s recovery policy.
Configure guardians, a threshold, a timelock, and an abort path for Sigil’s on-chain identity recovery ceremony.
A permission is a condition, not a blank cheque.
A durable identity needs a recovery plan. Sigil’s dedicated ceremony lets an identity configure the conditions under which a replacement controller key can be accepted, with a waiting period and a way to abort an unwanted attempt.
Register a recovery group and the number of guardian authorizations required. The threshold is an explicit part of the identity’s recovery policy.
Initiation creates a recovery attempt that can accumulate guardian approvals. The process has defined states instead of an informal support request.
The configured timelock separates sufficient authorization from final key rotation. Interfaces can show when finalization becomes eligible.
The panic-abort key or the current authorized key can stop a pending ceremony under the protocol’s rules. Keep that recovery material separate from everyday signing.
Finalization checks the ready state and rotates the identity’s controller key. The recovery history remains attributable through signed transactions.
Register guardians, threshold, delay, and the panic-abort key while you control the identity.
Open a recovery attempt and collect the required guardian signatures.
Observe the timelock, abort if necessary, and finalize an eligible replacement key.
The ceremony depends on a previously registered recovery policy. Set it up while you control the identity and maintain the required recovery material.
No. The supported recovery workflow is the dedicated multi-step ceremony. The older generic recovery transaction is not enabled.