# Chapter 0: Choosing the Right Path for Your Crypto Legacy

Most crypto holders prioritize security — but often overlook one critical question:

What happens to your crypto if you cannot act?

The decision you make today determines whether you retain control while you are present — and whether predefined rules exist for how your crypto is handled when you are not — or whether your assets risk confusion, irreversible loss, or human conflict at the worst possible moment.

Here are the common approaches, and why they often fail:

* **Multisig Wallets:**\
  Popular, but coordination-dependent. If one participant is unavailable, execution may be blocked indefinitely. Balances are visible, increasing security and social pressure risks.
* **Mnemonic Sharing (Seed Phrases):**\
  Simple, but fragile. A single leaked, lost, or misused fragment can result in permanent and immediate loss, with no reversibility or control.
* **Custodial Exchanges:**\
  Convenient, yet discretionary. Assets depend on third parties, exposed to hacks, insolvency, or regulatory intervention.
* **Traditional Legal Inheritance:**\
  Slow, expensive, and jurisdiction-bound. Courts and lawyers cannot execute on-chain transactions and often introduce long delays and loss of privacy.
* **Social Recovery Wallets:**\
  Appealing in theory, but dependent on long-term human trust and coordination, which degrades over time.
* **Multi-Party Computation (MPC):**\
  Technically advanced but brittle. If enough key shares are lost or compromised, access is permanently gone. MPC does not provide native on-chain execution logic for delays, recovery, or staged distribution.
* **DIY Solutions (Custom Smart Contracts):**\
  Attractive for advanced users, but complex and risky. A single mistake can permanently lock assets, and individual implementations rarely match battle-tested systems.

And then there is CryptoLegacy.

CryptoLegacy is not a replacement for self-custody.\
It is a system designed to define what happens **when self-custody alone is no longer sufficient**.

Hidden. Secure. Transferable.

* **Hidden Privacy:**\
  Assets, balances, and role relationships remain private until predefined on-chain conditions allow execution.
* **Trusted Guardians:**\
  Guardians are individuals you select in advance. They do not control assets and cannot access funds directly. Their role is limited to confirming owner unavailability according to predefined thresholds, enabling execution without discretionary decisions.
* **Assets Remain Under Owner Control:**\
  CryptoLegacy contracts do not hold assets during normal operation. Assets remain in the owner’s wallets until predefined conditions permit transfer.
* **Built-in Recovery:**\
  Recovery addresses provide a predefined override mechanism, allowing remaining contract-held assets to be withdrawn if circumstances change, without rewriting history or reversing completed transfers.
* **Deterministic Execution:**\
  Transfers follow predefined rules and timing. Execution is automated at the rule level, not through discretionary intervention.
* **Flexible by Design:**\
  Beneficiaries, wallets, and distribution parameters can be updated over time, while the core execution model remains stable across assets and chains.

CryptoLegacy does not promise outcomes.\
It defines and enforces execution rules in advance.

Your crypto deserves more than secure storage.\
It deserves a defined execution path when the owner cannot act.

**Your keys. Your crypto. Your legacy.**


---

# 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/execution-scenarios/chapter-0-choosing-the-right-path-for-your-crypto-legacy.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.