> For the complete documentation index, see [llms.txt](https://docs.cryptolegacy.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cryptolegacy.app/detailed-flows/detailed-guardians-emergency-asset-withdrawal-and-distribution-start.md).

# Detailed Guardians Emergency Asset Withdrawal and Distribution Start

Guardians initiate emergency withdrawal; if owner doesn’t cancel in 5 days, guardians decrypt wallet data and transfer all assets on-chain.

* Guardian **#1** sends a transaction initiating an emergency withdrawal and distribution.
* Guardians **#2, #3, and #4** send transactions confirming the emergency withdrawal.
* **4 of 7 Guardians threshold** reached; a **5-day timeout** begins.
* As the contract Owner, you may send a transaction to **cancel** during this 5-day period.
* Alternatively, **2 of 3 Recovery addresses** may also send transactions to cancel during this period.
* You **do not cancel** within the 5-day timeout.
* After the 5-day timeout expires, neither the Owner nor Recovery addresses can cancel.
* After expiration, any Guardian automatically retrieves wallet and ERC20 address data, decrypting it with their private encryption keys.
* Any Guardian sends a transaction transferring **all assets** from wallets to the CryptoLegacy contract.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.cryptolegacy.app/detailed-flows/detailed-guardians-emergency-asset-withdrawal-and-distribution-start.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
