> For the complete documentation index, see [llms.txt](https://docs.bloxchain.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bloxchain.app/platform-bloxchain.app/recovery.md).

# Recovery & incidents

**Audience:** Admin · **Platform:** bloxchain.app + on-chain policy

Recovery keys, incident response, and when to use the **Recovery** protected role.

## Test recovery (testnet only)

Practice on a **disposable** Sepolia contract — never on mainnet with real value.

1. Assign **Recovery** to a dedicated wallet under [Security settings](/platform-bloxchain.app/overview-1/security-settings.md).
2. Document who holds Recovery and when it may be used.
3. Trigger the recovery path per your schema on testnet only.
4. Connect Recovery wallet → **Deployment → Security**.
5. Verify owner and roles in [My access](/platform-bloxchain.app/overview/my-access.md).

Protocol: [SecureOwnable](/protocol/secure-ownable.md)

## Preparation (before an incident)

* [ ] Document Owner, Broadcaster, Recovery addresses offline
* [ ] [Production readiness](/developers/production-readiness.md)
* [ ] Test recovery on testnet annually
* [ ] Contact tree — [Support](/resources/support.md)

## Incident categories

| Category                        | First actions in the app                                                                                                                                     |
| ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Compromised operator wallet** | Remove wallet from [Roles & members](/platform-bloxchain.app/overview-1/roles-and-members.md); review [History](/platform-bloxchain.app/overview/history.md) |
| **Compromised Owner**           | Recovery path if configured; pause new [requests](/platform-bloxchain.app/overview/submit-request.md) org-wide                                               |
| **Stuck pending txs**           | [Approve and sign](/platform-bloxchain.app/overview/approve-and-sign.md) or cancel when permitted                                                            |
| **Wrong allowlist**             | Update [Allowlists](/platform-bloxchain.app/overview-1/allowlists.md); audit past executions                                                                 |
| **Protocol vulnerability**      | [Responsible disclosure](/security/report-vulnerabilities.md); freeze operations                                                                             |

## On-chain vs off-chain

Bloxchain cannot roll back mainnet transactions. Recovery means **governed** corrective operations and key rotation — not database restores.

## Migrating to a new contract

Official **CopyBlox** workspaces are **non-upgradeable**. When you need new logic or a clean security boundary:

1. **Deploy or import** a new workspace ([Deploy](/platform-bloxchain.app/contracts/deploy.md) or [Import](/platform-bloxchain.app/contracts/import.md)).
2. **Reconfigure** policy on the new address ([Configure overview](/platform-bloxchain.app/overview-1.md)).
3. **Move assets** through governed operations from the old workspace to the new one.
4. **Update integrators** — SDK `contractAddress`, app tab, and allowlists must point at the new workspace.
5. **Decommission** the old workspace — remove operators and stop new traffic.

Test on **Sepolia** first. See [Deployment — Immutable vs upgradeable](/developers/deployment.md#immutable-vs-upgradeable).

## Post-incident

1. Root cause analysis
2. Update RBAC — [RBAC best practices](/developers/rbac-best-practices.md)
3. [Checklist](/platform-bloxchain.app/contracts/checklist.md) before resuming mainnet volume

![Incident response](/files/SxTIwrXv6mtWGZ7RXjic)

## Developers

SDK and org-wide runbooks: [Disaster recovery (developers)](/developers/disaster-recovery.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.bloxchain.app/platform-bloxchain.app/recovery.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.