# Detailed Guardians Setup Flow

## **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: 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:

```
GET https://docs.cryptolegacy.app/detailed-flows/detailed-guardians-setup-flow.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
