# The Solution: How CryptoLegacy Works

### The Solution: How CryptoLegacy Works

CryptoLegacy is **not a wallet** and **does not store your funds**.

It is an on-chain execution system that you configure **in advance**,\
so execution does not depend on human decisions later.

Below is how the system works in simple, practical terms.

***

#### 1. You create a CryptoLegacy contract

You create a personal CryptoLegacy contract.

During setup, you define:

* who should receive assets (beneficiaries)
* how assets should be transferred and distributed
* timing rules that control when execution is allowed

The contract does not hold funds.\
It only stores **rules and permissions**.

***

#### 2. You approve assets for future execution

Your assets remain in your own wallets.

You approve the CryptoLegacy contract\
to transfer specific assets **only if execution is triggered later**.

Nothing moves at this stage.\
Approval only makes future execution possible.

***

#### 3. (Optional) You configure guardians and recovery

You can optionally configure two additional roles.\
They serve different purposes and are activated under different conditions.

***

**Guardians**

Guardians exist to **avoid waiting for the inactivity timer**.

If something happens to you:

* guardians can collectively signal that execution should begin
* this allows the system to proceed **without waiting for inactivity**

Guardians:

* do not hold your keys
* do not control your funds
* cannot act individually
* can only trigger predefined execution paths

Guardians reduce **coordination delays**,\
but they do not introduce custody or discretion.

***

**Recovery**

Recovery is a stronger fallback mechanism.

Recovery addresses can:

* cancel an execution before final transfer
* stop guardian-triggered execution
* recover remaining assets if execution must be halted

Recovery exists for situations where:

* guardians fail or disagree
* execution must be stopped before finality
* remaining funds need to be secured

Recovery does not grant control in advance.\
It becomes active only under strict, predefined on-chain rules.

***

#### 4. During normal use, nothing happens

As long as you:

* interact on-chain
* update the activity timer as required

CryptoLegacy does nothing.

Your assets stay in your wallets.\
There is no custody and no execution.

***

#### 5. If you stop acting, a waiting period begins

If you do not update the activity timer:

* the system detects inactivity
* a waiting (Challenge) period begins

During this period:

* you can cancel execution if you regain access
* recovery roles can stop the process

No assets are transferred yet.

***

#### 6. How execution can begin

Execution can start in one of two ways.

1. **Inactivity path**
   * the owner stops acting
   * the waiting period completes
   * execution is allowed
2. **Guardian path**
   * guardians reach the required threshold
   * execution is allowed **without waiting for inactivity**

In both cases, the same predefined rules apply.

***

#### 7. Execution and distribution

Once execution begins:

* approved assets are transferred
* distribution follows the rules you defined
* claims proceed deterministically

At this stage:

* no human decisions are made
* no coordination is required
* execution cannot be reinterpreted

CryptoLegacy executes exactly what was defined in advance.


---

# 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/start-here/the-solution-how-cryptolegacy-works.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.
