# Protocol Mechanics

- [Read This First](https://docs.cryptolegacy.app/protocol-mechanics/read-this-first.md)
- [Our Vision](https://docs.cryptolegacy.app/protocol-mechanics/our-vision.md): CryptoLegacy focuses on long-term value, security, and deterministic on-chain execution — without speculation, discretion, or dependency on human coordination.
- [Canonical Definitions](https://docs.cryptolegacy.app/protocol-mechanics/canonical-definitions.md)
- [Protocol Execution Invariants](https://docs.cryptolegacy.app/protocol-mechanics/protocol-execution-invariants.md)
- [How CryptoLegacy Works](https://docs.cryptolegacy.app/protocol-mechanics/how-cryptolegacy-works.md): CryptoLegacy defines on-chain execution rules for asset transfer and recovery when the owner cannot act. Execution is configured in advance and triggered by timeouts or guardian confirmations.
- [Secure Asset Data Transfer with CryptoLegacy](https://docs.cryptolegacy.app/protocol-mechanics/secure-asset-data-transfer-with-cryptolegacy.md): CryptoLegacy encrypts asset metadata client-side with wallet-derived keys and records it on-chain. Data is usable only through protocol-defined execution paths, preserving privacy and self-custody.
- [How CryptoLegacy Contract Periods and Guardian Controls Work](https://docs.cryptolegacy.app/protocol-mechanics/how-cryptolegacy-contract-periods-and-guardian-controls-work.md): Explains the fixed 6-month check-in, 3-month challenge, and distribution phases. Guardians trigger protocol-defined execution paths when the owner cannot act, while recovery handles remaining assets.
- [Cross-chain Integration for Lifetime NFTs and Referral Program](https://docs.cryptolegacy.app/protocol-mechanics/cross-chain-integration-for-lifetime-nfts-and-referral-program.md): Lifetime NFTs and referral codes work across multiple blockchains via deBridge. NFTs are minted once and locked cross-chain, while referral codes are created once and reused across supported networks.
- [CryptoLegacy Plugins Extend Contract Functionality](https://docs.cryptolegacy.app/protocol-mechanics/cryptolegacy-plugins-extend-contract-functionality.md): CryptoLegacy contracts use modular, audited execution plugins registered on-chain to extend allowed actions without changing core execution rules or authority boundaries.
- [CryptoLegacy NFT: Lifetime Access and DAO Rights](https://docs.cryptolegacy.app/protocol-mechanics/cryptolegacy-nft-lifetime-access-and-dao-rights.md): A single Lifetime NFT replaces recurring DAO donations, enables cross-chain access, and provides tier-based DAO governance rights.
- [CryptoLegacy Governance and Path to True Decentralization](https://docs.cryptolegacy.app/protocol-mechanics/cryptolegacy-governance-and-path-to-true-decentralization.md): CryptoLegacy governance evolves from NFT-based DAO voting and multisig control toward fully decentralized, on-chain governance.
- [CryptoLegacy: Security-First Approach to Asset Transfer and Recovery](https://docs.cryptolegacy.app/protocol-mechanics/cryptolegacy-security-first-approach-to-asset-transfer-and-recovery.md): CryptoLegacy secures assets by defining deterministic execution paths for transfer and recovery, without custody, manual intervention, or trust-based controls.
- [CryptoLegacy: Privacy Is Important for Execution When the Owner Cannot Act](https://docs.cryptolegacy.app/protocol-mechanics/cryptolegacy-privacy-is-important-for-execution-when-the-owner-cannot-act.md): CryptoLegacy protects privacy by encrypting sensitive data locally and recording it on-chain. Decrypted data is usable only within protocol-defined execution paths when the owner cannot act.
- [CryptoLegacy: Protocol Integrations for Flexibility](https://docs.cryptolegacy.app/protocol-mechanics/cryptolegacy-protocol-integrations-for-flexibility.md): CryptoLegacy integrates with external protocols through execution plugins, allowing predefined actions during Distribution without changing custody, authority, or core execution rules.


---

# 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/protocol-mechanics.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.