> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.6mm.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.6mm.com/_mcp/server.

# Security and Recovery

> Plan roles, signing devices and recovery responsibilities for MPC wallets.

Security preparation starts with the selected custody arrangement. Account protection, transaction approval, MPC participation and recovery material serve different purposes.

## Assign responsibilities

Separate routine viewing, transfer initiation, approval, member administration and developer credential management where the product allows it. Check permissions in the intended workspace; access to one workspace does not establish authority over another.

For enterprise workflows, agree who reviews destination changes and outgoing requests. For device signing, the participant should inspect the displayed network, asset, amount, destination and context before accepting. A device confirmation should not be treated as a blind approval prompt.

## Keep credentials distinct

| Material                     | Purpose                                                           |
| ---------------------------- | ----------------------------------------------------------------- |
| Account authentication       | Access the user application                                       |
| API key and secret           | Authenticate backend API requests                                 |
| Customer authorization key   | Authorize the contents of an API withdrawal where required        |
| MPC key share                | Participate in the wallet's distributed signing process           |
| Backup and recovery material | Restore participation or perform the supported recovery procedure |

Store these according to their own responsibilities. An API key is not an MPC share; resetting an account password is not a wallet recovery operation. Upload public keys only through the relevant registration flow, never their corresponding private keys.

## Prepare recovery before use

Record the required participants, backup owners and recovery steps during onboarding. Keep backups in separate appropriate locations and test the supported recovery procedure in a controlled environment. Consider both a lost device and a platform service outage.

Self-custody does not allow the platform to recreate missing customer shares. If too few usable participants and backups remain to satisfy the wallet's requirements, access to assets may be lost. Joint custody also needs a documented recovery arrangement; do not assume platform participation guarantees recovery.

## Handle an unavailable participant

First distinguish a temporary connection problem, an unavailable device and lost signing material. Review the session and device status, then use the supported recovery or replacement process. Do not erase a device, change its application signing identity or assume shares can be moved before checking the recovery requirements.

Backup availability is not proof of a completed recovery test. Confirm which procedures and tools are included in your release before relying on them.