top of page
Search

Stablecoin Custody: Separate Authority and Test Access Recovery

14 hours ago
3 min read

A custody policy can look complete yet fail when a signer leaves. Normal operations, temporary absence, device loss and suspected compromise require different responses. Governance should cover each scenario.

The issue is not selecting a particular product. It is separating authority, technical capability and recovery powers without creating a single person who can bypass the controls.

 

Separate four powers

Initiation, commercial approval, signing and reconciliation are different tasks. The person proposing a payment should not automatically be able to change its beneficiary, sign it and remove its evidence. Smaller organisations can combine roles, provided conflicts and compensating controls are explicit.

A technical quorum is not a corporate delegation. Two valid signatures do not prove internal authority to bind the company. Conversely, management approval does not restore missing technical access.

 

Hypothetical case: two signatures from three

Assume a system requiring two of three authorised signers. This is a teaching design, not a universal architecture recommendation. The control reviewer has no signing capability.

Event

Planned response

Retained evidence

Routine payment

Invoice approval followed by two authorised signatures

Decision, beneficiary and reconciliation

Temporary absence

Other two signers act within existing limits

Absence record and valid authority

Permanent departure

Controlled revocation and system update

Approval and effective access removal

Device loss

Tested recovery without improvised secret sharing

Exercise record and identity checks

Suspected compromise

Incident response, movement restrictions and appropriate replacement

Timeline and security decision

Three signers are not independent if all rely on one phone, one recovery account or one administrator able to reset everything. The displayed quorum does not establish effective separation.

Separation of roles before a payment is approved.

 

Test recovery without exposing secrets

Review backup location, access conditions and requester authentication. Do not put private material into an audit file or shared messaging channel. The exercise records the procedure and result, rather than the keys themselves.

NIST’s key-management recommendations distinguish recovery from compromise handling. They are a general reference, not instructions specific to every wallet. Adapt the process to the actual arrangement, especially where a custodian controls the keys or uses a different architecture.

 

Include administrative and contractual recovery

With a provider, the critical issue may be resetting an administrator, maintaining authorised-person records or changing withdrawal rules. The contract should explain recourse, stated timelines and the customer’s position during outage or insolvency. A technical backup does not resolve an uncertain legal claim.

NYDFS’s September 2025 custody guidance illustrates the importance of custody structures and customer disclosures within its own perimeter. It does not automatically govern every business and provider worldwide.

Controlled access recovery and custody continuity.

 

Revocation must work in the actual arrangement

Removing a name from an internal directory is insufficient while technical access survives. On-chain multisignature changes depend on the contract; MPC arrangements on their specific mechanisms; custodians on administrative permissions and policies. Technical specialists establish what must be changed or replaced. BECTRA examines governance and control evidence without handling secrets or certifying code security.

Fictional rehearsal: a signer leaves. Management approves removal; the technical owner executes the supported procedure; an independent reviewer tests that the former access fails while authorised operation remains possible. Use an appropriate test environment without unnecessary exposure of live assets. Retain permission versions, test results and exceptions. Revoked corporate authority with surviving technical capability is a failed result.

 

Make the rehearsal lead to a decision

BECTRA’s proposed authority matrix and continuity scenario help the responsible specialists test whether authorised access can be restored while preserving independent controls. If recovery depends on one unavailable individual, address the governance weakness before increasing exposure.

 

Further reading

 

 

 

 

Sources

Sources checked on 17 October 2026. Teaching cases are hypothetical; the proposed methods and decisions are BECTRA analysis.

 
 
 

Comments


Commenting on this post isn't available anymore. Contact the site owner for more info.

Contact

BECTRA

Paris, France

​

  • Linkedin

Merci pour votre envoi !

© 2024 by Cabinet BECTRA.

bottom of page