# Detailed Contract Setup Flow

## **Create CryptoLegacy Contract** 

* **Beneficiaries**:
  * Beneficiaries provide their addresses and public encryption keys.
  * Add 5 beneficiaries (provide their addresses and public encryption keys).
  * Set a 1-month delay per beneficiary (of course, you can choose any period).
  * Distribute equal shares (20% each) over 10 years. You can customize any parameter.
* **Deployment**:
  * Pay DAO donation and deploy the contract via the Factory.
  * Guardians and Recovery plugins are automatically added.
* **Data Storage**:
  * Beneficiary addresses are stored as hashes.
  * Original addresses and encryption keys are saved locally in your browser.

## **Token Approval**

* You have:
  * 3 multisig wallets holding assets.
  * 4 regular wallet addresses.
* Approve all tokens from all wallets to the new CryptoLegacy contract.
* Wallet and ERC20 token addresses are automatically saved locally in your browser.

## **Backup Encryption**

* Your backup is automatically encrypted with your public encryption key.
* Send a transaction to store the encrypted backup within a smart contract event.

## **Beneficiary Data Encryption**

* Wallet and asset addresses are automatically encrypted for each beneficiary using their public encryption keys.
* Send a transaction to store the encrypted data within a smart contract event.

## **Beneficiary Access and Testing**

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

## **Update timeout on CryptoLegacy Contract**

* Each 6 months send transaction to update timeout.


---

# 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-contract-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.