> 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-setup-flow.md).

# Detailed Guardians Setup Flow

CryptoLegacy assigns guardians, sets approval thresholds, encrypts guardian data, stores backups, and tests access securely on-chain.

## **Guardians Setup for CryptoLegacy Contract**

* **Default Guardians**:
  * Beneficiaries automatically become Guardians (this can be modified).
  * Default approval threshold: **2 of 3** Guardians required for emergency withdrawals.
  * Emergency withdrawals trigger a **30-day challenge period** before distribution.
* **Adding Additional Guardians**:
  * Invite two friends to serve as additional guardians. There’s no limit - this is just an example.
  * Collect their addresses and public encryption keys.
  * Set the approval threshold to **4-of-7 guardians**. You can choose any number from 1 up to the total number of guardians.
  * Set Guardians' challenge timeout to **5 days**.
  * Confirm these settings by sending a transaction.
* **Data Storage**:
  * Guardian addresses are stored as hashes on-chain.
  * Original Guardian addresses and encryption keys are stored locally in your browser.

## **Backup Encryption**

* Backup is automatically encrypted using your public encryption key.
* Store encrypted backup by sending a transaction to the smart contract event.

## **Guardian Data Encryption**

* Automatically encrypt wallet and asset addresses for each Guardian using their public encryption keys.
* Store this encrypted data by sending a transaction to the smart contract event.

## **Guardian Access and Testing**

* Guardians do **not** have direct access to encrypted messages.
* Request Guardians verify encryption by testing with a provided test message.


---

# 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-setup-flow.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.
