# CryptoLegacy Governance and Path to True Decentralization This section describes protocol-adjacent infrastructure. It does not modify or extend core execution guarantees. CryptoLegacy is designed with decentralization as a long-term goal, not a marketing promise. While the system is self-custodial, governance requires a careful transition to avoid introducing new risks. In the initial phase, governance is formed by early users and supporters holding **CryptoLegacy Lifetime NFTs**. DAO participation and voting are currently conducted **off-chain using Snapshot**, with voting power derived from NFT tiers. This phase allows the community to define core principles, including the **Manifesto**, **Mission**, and governance **rules**, without introducing execution risk into smart contracts. During early decentralization, critical protocol-adjacent components — most notably the **Plugin Registry** — may be managed via **DAO-controlled multisig wallets**. This approach balances decentralization with security, ensuring that plugin approvals and updates remain auditable and conservative while the ecosystem matures. Security firms and partner protocols may participate in this process to provide additional review and oversight. Most core CryptoLegacy smart contracts are non-proxied, and do not require ongoing governance intervention. Governance is intentionally limited to areas where flexibility is necessary, such as plugin approval, fee/configuration parameters, and cross-chain configuration. In the future, the DAO may choose to introduce an **ERC20 governance or utility token**, but no such decision has been made. If introduced, it would be governed by the community and designed to complement — not replace — the existing NFT-based governance model. Decentralization in CryptoLegacy is treated as a process, not a milestone. Each governance step is intended to reduce trust assumptions while preserving the security and predictability of execution. --- # 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/cryptolegacy-governance-and-path-to-true-decentralization.md?ask= ``` 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.