Skip to navigation

Custody Models

View as Markdown

Start by deciding who should participate in asset control and who can operate and recover the required devices. A product name, workspace role or approval rule does not replace that decision.

Compare the arrangements

ArrangementShare custodyPreparation
Fully managedThe platform operates the signing infrastructure; the customer uses account permissions and business workflowsDefine operators, approval rules and reconciliation responsibilities
Joint custodyThe platform and customer each hold part of the signing material under the selected wallet planArrange customer participants, availability and backups; confirm which combinations meet the signing threshold
Self-custodyThe customer holds the wallet’s key sharesOperate the required devices and retain the material needed for recovery

Personal, team and enterprise products can expose different choices. Use the custody plan shown during setup to confirm the actual participants and threshold. Self-custody describes share possession; it does not automatically mean every application, identity or coordination dependency is independent of the platform.

Approval and signing are separate

An approval determines whether an operation is permitted through the application workflow. MPC signing requires enough eligible share holders to participate. Approvers and signing participants may be different people or devices.

Whitelists, delays, limits and approval rules are application controls. They do not, by themselves, cryptographically prevent a set of share holders that already satisfies the signing threshold from signing outside that workflow.

Before choosing

Confirm who initiates transfers, approves them, participates in signing, broadcasts transactions and reviews records. Also agree how an unavailable participant or lost device will be handled.

The current setup records the custody choice as fixed for that workspace. Do not plan on switching custody by changing a setting later; a different arrangement may require a new workspace and a coordinated asset migration. Confirm the supported procedure with the onboarding team.