{"id":"canopy","hidden":false,"ipfs":"QmQ7RQQV81w3TMNnqnxTCNNSRTgpRjyumqZEp6jKwZ49nC","language":"en","transactionHash":"0x36257c908aef508d91aac8385f6b90a0d8aa072e7bc3872fcd2c0b34b310ebf4","created":"2026-09-16T18:19:13.499Z","updated":"2026-09-16T18:37:00.411Z","title":"Canopy","summary":"Canopy is a projects-and-protocols that provides an infrastructure stack and a restaking-based security network to deploy, bootstrap, and secure application-specific blockchains quickly.","content":"**Canopy** is an AI-native [blockchain](https://iq.wiki/wiki/blockchain) platform for creating, launching, and developing onchain applications through application-specific networks called Nested Chains. Its infrastructure provides development tools, shared security, governance, interoperability, and a path for Nested Chains to operate as independent networks. [\\[5\\]](#cite-id-wk78q36ppb) \n\n## Overview\n\n![](https://ipfs.everipedia.org/ipfs/QmeKbz4tFX3fvrHkceZP4x4H1RgwqfqtFoT5P1mQqNTchF)\n\nCanopy is an AI-native platform for creating, launching, and developing onchain applications through application-specific networks called Nested Chains. It simplifies development by letting builders start with an idea, use AI to develop and refine application logic, and create prototypes or working applications without first managing [consensus mechanisms](https://iq.wiki/wiki/consensus-mechanism), [validators](https://iq.wiki/wiki/validator), or other [blockchain](https://iq.wiki/wiki/blockchain) infrastructure. The Canopy Stack supports application development using languages including Go, TypeScript, Python, Kotlin, and C#, while the Canopy Terminal provides a process for moving completed applications from development to deployment. Each Nested Chain can have its own application logic, rules, economic model, and governance, giving developers greater control over the environment in which their applications operate.\n\nAfter launch, Nested Chains can use Canopy Network's shared [validator](https://iq.wiki/wiki/validator) infrastructure and cryptoeconomic security while developing their own user and economic activity. Canopy supports interoperability between Nested Chains without third-party bridges and provides scaling mechanisms that let applications expand across layers or laterally. Its [validator](https://iq.wiki/wiki/validator) ecosystem uses CNPY as [collateral](https://iq.wiki/wiki/collateral), and [validators](https://iq.wiki/wiki/validator) can restake [collateral](https://iq.wiki/wiki/collateral) to support multiple Nested Chains. As an application matures, it can continue using Canopy's shared infrastructure or transition toward operating as an independent [Layer 1](https://iq.wiki/wiki/layer-1) network, providing a path from an application initially supported by shared infrastructure to a more autonomous [blockchain](https://iq.wiki/wiki/blockchain) network. [\\[4\\]](#cite-id-qhuzy1raws) \n\n## Features\n\n### P2P Security\n\n![](https://ipfs.everipedia.org/ipfs/QmdFp776oQmfbSdjRAGoJekP2b9hUNLgCQFufYQzTSiVxY)\n\nCanopy Network's Peer-to-Peer Security model uses a recursive architecture designed to provide security and infrastructure for newly launched application-specific [blockchains](https://iq.wiki/wiki/blockchain) while addressing the cold-start challenges associated with independent [Layer 1](https://iq.wiki/wiki/layer-1) networks. New chains initially operate under a Security Root chain, which uses its [total locked value](https://iq.wiki/wiki/tvl) to help protect against hostile takeovers, provides access to an established [validator](https://iq.wiki/wiki/validator) set, connects the new chain to the broader Canopy ecosystem, and enables liquidity through token swaps with external networks. The model also lets tokens and economic activity circulate between participating chains through mechanisms such as block rewards, connecting the security and liquidity of different networks. As individual chains mature and become sufficiently independent, they can themselves serve as Security Roots for subsequent chains, creating a recursive structure in which established networks provide security and infrastructure for newer ones. The architecture combines an application development model similar to [Ethereum's](https://iq.wiki/wiki/ethereum) [dApp](https://iq.wiki/wiki/decentralized-application) environment with the greater network independence associated with [Layer 0](https://iq.wiki/wiki/layer-0) infrastructure, with the security structure expanding as additional [blockchains](https://iq.wiki/wiki/blockchain) join the network.  [\\[6\\]](#cite-id-sflebwum1e) \n\n### Progressive Sovereignty\n\nProgressive Sovereignty is a Canopy framework that lets [blockchains](https://iq.wiki/wiki/blockchain) gradually operate independently of external protocols and infrastructure. Sovereign [blockchains](https://iq.wiki/wiki/blockchain) are designed to scale independently, resist censorship by parties outside their stakeholder base, retain complete [blockchain](https://iq.wiki/wiki/blockchain) history and data ownership, and maintain historical finality when joining or leaving a Security Root. They can also leave or rejoin a Security Root without changing the underlying software, allowing networks to transition toward greater independence over time. [\\[7\\]](#cite-id-46m6litfws) \n\n### Capital Efficient Restaking\n\n![](https://ipfs.everipedia.org/ipfs/QmRtHhKw9G6hy1FPyPqzejAKQV75rDe5BvCjKNRoETF8MD)\n\nCanopy's Capital-Efficient Restaking model lets [validators](https://iq.wiki/wiki/validator) use existing locked tokens as [collateral](https://iq.wiki/wiki/collateral) to secure multiple Nested Chains without providing additional stake for each network. [Validators](https://iq.wiki/wiki/validator) can opt in to support individual chains and receive the respective chain's native token as compensation, while additional rewards may be available through the Security Root based on the amount of committed stake. The Security Root DAO determines how many Nested Chains a [validator](https://iq.wiki/wiki/validator) can support. This model lets new chains obtain security through [validator](https://iq.wiki/wiki/validator) participation and community support, rather than requiring them to independently attract substantial capital for initial security. [\\[8\\]](#cite-id-gti8et44d0) \n\n### Chain Halt Rescue\n\nCanopy's Chain Halt Rescue mechanism helps Nested Chains recover from prolonged periods of non-liveness, where a consensus failure prevents new blocks from being produced. These halts can result from [validator](https://iq.wiki/wiki/validator) outages, protocol non-determinism, or software bugs and may require identifying the underlying issue, updating and distributing [blockchain](https://iq.wiki/wiki/blockchain) software to a sufficient portion of the [validator](https://iq.wiki/wiki/validator) set, and coordinating [validators](https://iq.wiki/wiki/validator) to restart the network. Canopy's nested architecture allows the Security Root to automatically recover a Nested Chain from a halt, reducing the need for extended manual coordination among [validators](https://iq.wiki/wiki/validator). This mechanism is intended to shorten recovery periods and maintain continuity of [blockchain](https://iq.wiki/wiki/blockchain) operations when a Nested Chain experiences a consensus-related disruption. [\\[9\\]](#cite-id-8xpk4b2v56) \n\n### NestBFT\n\nNestBFT is Canopy's [Byzantine Fault Tolerant](https://iq.wiki/wiki/byzantine-fault-tolerance) [consensus mechanism](https://iq.wiki/wiki/consensus-mechanism) for the Root Chain and Nested Chains, designed to provide fast finality, [validator](https://iq.wiki/wiki/validator) fault tolerance, and protection against attacks such as [Sybil](https://iq.wiki/wiki/sybil-attack), [DDoS](https://iq.wiki/wiki/distributed-denial-of-service-ddos-attack), grinding, and long-range attacks. It combines [Proof-of-Stake](https://iq.wiki/wiki/proof-of-stake) with Proof-of-Age: PoS provides stake-based consensus, bonding, and economic security, while Proof-of-Age uses Verifiable Delay Functions (VDFs) to establish verifiable elapsed time and help [nodes](https://iq.wiki/wiki/node) select the correct chain when syncing. The protocol uses a leader-election system based on a practical Verifiable Random Function, with [validator](https://iq.wiki/wiki/validator) stake influencing the likelihood of becoming a leader, while cryptographic inputs make selection difficult to manipulate. NestBFT also uses BLS multi-signature aggregation and a structured communication process to reduce consensus resource requirements.\n\nThe consensus process consists of multiple phases covering leader election, proposal, voting, locking, and block commitment, with more than two-thirds of voting power required to pass voting stages. [Validators](https://iq.wiki/wiki/validator) first determine leader candidates using the VRF mechanism, after which a leader proposes a block and [validators](https://iq.wiki/wiki/validator) validate and vote on it. Subsequent precommit and commit stages establish the block's finality, after which validators propagate the finalized block to their peers. If a phase fails, recovery mechanisms allow validators to exchange their current rounds and move to a higher safe round through the protocol's pacemaker, enabling consensus to continue without requiring the network to restart from the beginning. [\\[10\\]](#cite-id-uc5755mdns)  [\\[11\\]](#cite-id-dxcb4u9uea) \n\n### Canopy KMS\n\nCanopy KMS is a purpose-built key management system that provides signing infrastructure for Canopy's high-value [blockchain](https://iq.wiki/wiki/blockchain) keys without functioning as a wallet. It separates transaction requests from the systems that hold and use private keys, authenticating and evaluating every request against predefined policies before execution. Rather than returning signed transactions to callers, Canopy KMS builds, signs, and submits approved transactions itself, using a fail-closed policy system that can reject requests that do not meet required conditions. The system supports multiple cryptographic schemes, including ed25519 for Canopy-native transactions, secp256k1 for [EVM](https://iq.wiki/wiki/ethereum-virtual-machine-evm) operations, and BLS12-381 for [multisignature](https://iq.wiki/wiki/multi-signature-wallet) and threshold-signature functions. Its signing infrastructure supports operations such as treasury management, cross-chain transfers, [multisignature](https://iq.wiki/wiki/multi-signature-wallet) signing, chain creation, and liquidity management, with controls tailored to each transaction type.\n\nCanopy KMS also provides key management services for Nested Chains launched on Canopy, allowing chain operators to use shared signing infrastructure instead of building their own systems. Chain creators can manage treasury wallets for individual chains through the KMS, with configurable spending policies. The system can also support managed bridge operations, including contract deployment, relayer and operator identities, and liquidity management, with each operation subject to the same policy-based signing controls. This creates a common signing boundary for Canopy and its Nested Chains while keeping private keys isolated from the applications and services that request transactions. [\\[12\\]](#cite-id-qluqq9sfq4) \n\n## CNPY\n\nCNPY is the native token of the Canopy network and is used for [transaction fees](https://iq.wiki/wiki/transaction-fee), network security, and [validator](https://iq.wiki/wiki/validator) incentives across the Security Root and its Nested Chains. Users pay [transaction fees](https://iq.wiki/wiki/transaction-fee) in CNPY, with fees based on transaction requirements and network conditions, while [validators](https://iq.wiki/wiki/validator) and delegators bond CNPY to participate in consensus and support committees that secure individual Nested Chains. Bonded CNPY serves as collateral for [validator](https://iq.wiki/wiki/validator) participation, with rewards distributed for following the protocol and penalties, including slashing, applied to malicious or invalid behavior. The network can also use existing bonded CNPY to subsidize security for eligible Nested Chains, allowing new chains to access shared [validator](https://iq.wiki/wiki/validator) security without establishing an independent [validator](https://iq.wiki/wiki/validator) set or raising separate security capital. Governance can direct part of token issuance toward the [DAO](https://iq.wiki/wiki/dao) Treasury to fund activities supporting the broader Canopy ecosystem. [\\[1\\]](#cite-id-2ddnv7yo0n)  [\\[3\\]](#cite-id-7s7ar7dknm) \n\n### Tokenomics\n\nCNPY has a total supply of 560M tokens and has the following distribution: [\\[1\\]](#cite-id-2ddnv7yo0n)  [\\[3\\]](#cite-id-7s7ar7dknm) \n\n* **CNPY Block Producers**: 70%\n* **CNPY Staker Delegate**: 10%\n* **Nested Chain Validators**: 10%\n* **Nested Chain Staker Delegate**: 10%\n\n## Governance\n\n![](https://ipfs.everipedia.org/ipfs/QmR2N7gKQcAB4rz5yXH9tupD8b1hZR9k8mgiFpZVBz3EDA)\n\nCanopy's United Governance model gives [validators](https://iq.wiki/wiki/validator) a central role in setting each chain's protocol rules, while allowing other ecosystem participants to submit governance polls and proposals. Straw polls enable on-chain voting to measure community sentiment, with voting results separated between accounts holding liquid tokens and [validators](https://iq.wiki/wiki/validator) holding locked tokens. Formal proposals can make certain protocol parameter changes without modifying the underlying code and distribute funds from a chain's [DAO](https://iq.wiki/wiki/dao) treasury. At the broader ecosystem level, Canopy's nested architecture lets individual Nested Chains retain control of their own networks while coordinating through validator representation in Security Roots. Nested Chains can choose to join or leave Security Root systems and can collaborate on shared standards, initiatives, and dispute resolution across the ecosystem. [\\[11\\]](#cite-id-dxcb4u9uea) \n\n## Partnerships\n\n* Sonic Boom Ventures\n* Scytale\n* Arrington Capital\n* [Fenbushi Capital](https://iq.wiki/wiki/fenbushi-capital)\n* SNZ\n* KR1\n* Borderless\n* CodeCraft Group\n* Stakely\n* Lavender Fire\n* Stake Craft\n* Rhino Stake\n* Kingnodes\n* Easy 2 Stake\n","recentActivity":null,"operator":{"id":"0xacb6c5AD52b8f605299B0d774CE97F26e3DB80c2"},"categories":[{"id":"projects-and-protocols","title":"Projects & Protocols"}],"tags":[{"id":"Layer1"},{"id":"AIPlatform"},{"id":"Bridge"},{"id":"Infrastructure"},{"id":"DeFi"}],"images":[{"id":"QmRTrMFQrJprA69i4RHxPcUoKuLS6Z7FjHL3Q9X3mS3hH8","type":"image/jpeg, image/png"}],"media":[{"name":"xye0qYGfseftSUwB.png","id":"QmdFp776oQmfbSdjRAGoJekP2b9hUNLgCQFufYQzTSiVxY","size":null,"type":null,"source":"IPFS_IMG"},{"name":"HRhhJDYe3pBFIiEz.png","id":"QmRtHhKw9G6hy1FPyPqzejAKQV75rDe5BvCjKNRoETF8MD","size":null,"type":null,"source":"IPFS_IMG"},{"name":"DDfMQGOrQRE4ZgoM.jpeg","id":"QmR2N7gKQcAB4rz5yXH9tupD8b1hZR9k8mgiFpZVBz3EDA","size":null,"type":null,"source":"IPFS_IMG"},{"name":"Li5LHgo05Sb73wrB.jpeg","id":"QmeKbz4tFX3fvrHkceZP4x4H1RgwqfqtFoT5P1mQqNTchF","size":null,"type":null,"source":"IPFS_IMG"}],"linkedWikis":{"founders":["adam-liposky","andrew-nguyen"],"blockchains":["ethereum"],"speakers":[]},"events":[],"founderWikis":[],"blockchainWikis":[{"id":"ethereum","title":"Ethereum"}],"metadata":[{"id":"rootdata_profile","value":"https://www.rootdata.com/Projects/detail/Canopy?k=MjI2NTY="},{"id":"website","value":"https://www.canopynetwork.org/"},{"id":"twitter_profile","value":"https://x.com/CNPYNetwork"},{"id":"github_profile","value":"https://github.com/canopy-network/canopy"},{"id":"linkedin_profile","value":"https://www.linkedin.com/company/canopy-network/"},{"id":"coingecko_profile","value":"https://www.coingecko.com/en/coins/canopy"},{"id":"references","value":"[{\"id\":\"2ddnv7yo0n\",\"url\":\"https://coinmarketcap.com/currencies/canopy/\",\"description\":\"CoinMarketCap description of Canopy's premise and framework\",\"timestamp\":1789562239915},{\"id\":\"s4drtgz427\",\"url\":\"https://x.com/CNPYNetwork\",\"description\":\"Canopy identifies Adam Liposky as founder\",\"timestamp\":1789562239915},{\"id\":\"7s7ar7dknm\",\"url\":\"https://canopy-network.gitbook.io/docs/canopy-network/canopy-economics\",\"description\":\"CNPY as native token\",\"timestamp\":1789562239915},{\"id\":\"qhuzy1raws\",\"url\":\"https://canopy-network.gitbook.io/docs/canopy-network/canopy-overview\",\"description\":\"Canopy Overview self-description and recursive architecture\",\"timestamp\":1789562239915},{\"id\":\"wk78q36ppb\",\"url\":\"https://www.canopynetwork.org/\",\"description\":\"Canopy branding around AI-assisted development\",\"timestamp\":1789562239915},{\"id\":\"sflebwum1e\",\"url\":\"https://canopy-network.gitbook.io/docs/canopy-network/core-features/peer-to-peer-security\",\"description\":\"Matured chains become security roots for the next generation\",\"timestamp\":1789562239915},{\"id\":\"46m6litfws\",\"url\":\"https://canopy-network.gitbook.io/docs/canopy-network/core-features/progressive-sovereignty\",\"description\":\"Definition of sovereignty and its required properties\",\"timestamp\":1789562239915},{\"id\":\"gti8et44d0\",\"url\":\"https://canopy-network.gitbook.io/docs/canopy-network/core-features/capital-efficient-restaking\",\"description\":\"Onboarding via social consensus and restaking\",\"timestamp\":1789562239915},{\"id\":\"8xpk4b2v56\",\"url\":\"https://canopy-network.gitbook.io/docs/canopy-network/core-features/chain-halt-rescue\",\"description\":\"Definition and common causes of chain halts\",\"timestamp\":1789562239915},{\"id\":\"uc5755mdns\",\"url\":\"https://canopy-network.gitbook.io/docs/canopy-network/core-features/nestbft\",\"description\":\"NestBFT as the BFT consensus across Canopy chains\",\"timestamp\":1789562239915},{\"id\":\"dxcb4u9uea\",\"url\":\"https://canopy-network.gitbook.io/docs/canopy-network/understand-the-protocol/consensus\",\"description\":\"NestBFT used for Root and Nested Chain layers\",\"timestamp\":1789562239915},{\"id\":\"qluqq9sfq4\",\"url\":\"https://canopy-network.gitbook.io/docs/canopy-network/canopy-kms\",\"description\":\"Canopy KMS as dedicated signing infrastructure\",\"timestamp\":1789562239915}]"},{"id":"previous_cid","value":"QmQ7RQQV81w3TMNnqnxTCNNSRTgpRjyumqZEp6jKwZ49nC"},{"id":"commit-message","value":"Update tags for Canopy wiki"},{"id":"previous_cid","value":"QmQ7RQQV81w3TMNnqnxTCNNSRTgpRjyumqZEp6jKwZ49nC"}],"user":{"id":"0x8af7a19a26d8fbc48defb35aefb15ec8c407f889"},"author":{"id":"0xacb6c5AD52b8f605299B0d774CE97F26e3DB80c2"},"views":4}