Awarded once after a correct answer.
Prove portability rather than assume it
Useful first : Digital asset custody: beyond key storage · MPC wallets and threshold signing
Reading path · 14 / 18 · Advanced
A provider assessment should follow the service dependency rather than its product name.
The essentials
A provider assessment should follow the service dependency rather than its product name. Identify which party controls signing, policy administration, data access and recovery. Include subcontractors and shared infrastructure where their failure could affect the service. A contract description is a starting point for verification, not the test result.
How it works
An exit plan distinguishes access to records from the ability to operate assets elsewhere. Exported statements may support reconciliation while remaining insufficient to reconstruct wallet policy or signing capability. Specify formats, dependencies, personnel and expected transfer durations.
What to watch
Test both an orderly migration and a stressed exit where the provider is unavailable. Keep dual-running reconciliation, cancellation rules for pending requests and a controlled cut-over. Exit readiness needs periodic reassessment when keys, contracts, infrastructure or service scope change.
Build your analysis
Data portability and operational portability answer different questions. A file may preserve balances while leaving the institution unable to sign, identify client entitlements or monitor pending transfers independently. Trace dependencies on provider software, authentication, key shares, network access and contract administration. Ask which dependencies remain after the service contract ends.
Extend the workshop
Draft an exit rehearsal with a limited fictional asset set. State the starting balances, destination arrangements, permissions, records and acceptance checks. Run two narratives: a cooperative migration and an unavailable provider. A successful export in the first narrative is not evidence that signing or recovery works in the second.
Understand the details
A test report should state exactly what was recovered, by whom, using which independent resources and in how much time. A provider-assisted demonstration does not establish recovery without that provider. Document remaining dependencies so decision makers can assess the residual exposure.
Boundaries and common mistakes
Do not copy real signing secrets into an exercise document. Use a controlled test arrangement and retain attestations or results rather than confidential key material.
The mechanism at a glance
- 01Map dependency
- 02Define exit evidence
- 03Test unavailability
- 04Reconcile migration
Read these as connected concepts, not necessarily consecutive steps.
Read the explanation
A test report should state exactly what was recovered, by whom, using which independent resources and in how much time. A provider-assisted demonstration does not establish recovery without that provider. Document remaining dependencies so decision makers can assess the residual exposure.
Put the mechanism into context
A fictional provider offers daily CSV balances and promises “full portability”. Your institution cannot recreate signing policy without a service it hosts. Compare the evidence for data portability and operational exit. Define a test that would expose the dependency.
Apply it in the workshop →What this mechanism does not guarantee
Do not copy real signing secrets into an exercise document. Use a controlled test arrangement and retain attestations or results rather than confidential key material.
The distinction that changes the analysis
An export may contain balances without the identifiers, approvals or recovery material needed to operate elsewhere. Rehearse the destination process using the actual export format. A successful download is only one part of a usable exit plan.
Explain it yourself
Revisit the case above. Name what is established, what remains to be checked and the evidence needed to conclude. A strong answer addresses both sides of the diagram.
Apply the lesson to a case
A fictional provider offers daily CSV balances and promises “full portability”. Your institution cannot recreate signing policy without a service it hosts. Compare the evidence for data portability and operational exit. Define a test that would expose the dependency.
Balances describe positions; they do not provide authority to move them. Test the precise recovery arrangement, including policy data, availability of participants and a reconciled cut-over.
Prepare a correction note
Describe the passage and the proposed correction. This creates a local note for you to share; it sends nothing. Do not include personal or confidential information.