Need your CNPY on Canopy first? Every screen of the unwrap: canopynetwork.org/blogs/unwr…

A long-range attack uses old keys that once held a supermajority to rewrite history after their stake is gone. Apps on Canopy can checkpoint to the Security Root via each Certificate Result. Nodes verify the canonical chain against it. Graduate, and the checkpoints export too.

The Security Root, where every Canopy validator bonds CNPY, runs as a committee under the same rules as any app. So a validator can secure app committees (the validators running one app's consensus) without also validating the Security Root. You choose which committees you run.

An app block on Canopy pays four stakers by default: 70% to the CNPY validator that made it, 10% each to a CNPY delegate, a validator staking the app's token, and a delegate staking it. Committees can pay that in CNPY and the app's token. Back an app in both, earn in both.

RestakePercentage = CommitteeRestake / TotalStake When that reaches 33% for a committee, across validator and delegate stake, the app earns protocol issuance. The Security Root checks every block. The only way in: stakers directing bonded CNPY to it. canopynetwork.org/blogs/the-…

Every Security Root block issues 80 CNPY, roughly one block every 20 seconds. 56 goes to the DAO Treasury. 24 is split equally across every app committee at or above the 33% restake threshold. Each new app that qualifies shrinks every app's slice. Stakers decide which apps qualify.

A delegate bonds CNPY and lists committees but runs no app nodes and signs no blocks. Its stake counts toward each listed committee's 33% subsidization threshold, so delegators decide which apps receive issuance. It's also eligible for a 10% reward share, drawn by stake weight.

Two minutes. That's how long it takes to move CNPY from BNB Smart Chain to Canopy. On Canopy, bonded CNPY is the only collateral securing apps. Stake it with a validator, or delegate it and help decide which apps receive issuance all while receiving rewards. Step-by-step guide: canopynetwork.org/blogs/unwr…

When an app on Canopy halts, the recovery tools sit with the Security Root. It can reassign the app's validators, restart its consensus, or roll back its state. On a standalone chain, the same fix waits on two-thirds of the validator set upgrading and restarting together.

A validator with 10,000 CNPY bonded and three committees listed participates in all three, with 10,000 CNPY of voting power in each, slashable in any of them. The same collateral backs multiple consensus instances at once. Apps join the network with no new capital.

Your CNPY on BSC can be traded. That's all it can do. It can't stake, restake, earn committee rewards, pay fees or vote. Every app on Canopy is secured only by bonded native CNPY. Where you hold decides how much collateral backs the network. Bring it home 🌿 Unwrap at app.canopynetwork.org/trade/…

Every chain tells you that you own your app. Ask what happens when you try to leave. @AdamLiposky on what sovereignty actually means here: you own the application, you own the validator set, you own the token. Canoliq proved it on September 22, the first third-party chain to graduate on Canopy with its full history intact. 🌿 canopynetwork.org/blogs/cnpy…

Good read from @hackernoon on where crypto's lapsed users actually come back from. The short version: lower the bar to build, and the builders return. That is the whole idea behind Canopy. hackernoon.com/the-crypto-se…

Two very different apps went live on Canopy in the past 10 days, and both got there the same way. Canoliq (@canoliq): liquid staking. Praxis (@praxis_fdn): an onchain prediction market. One launch path: build with the Canopy Stack, launch through Terminal, run as your own network. canopynetwork.org/blogs/two-…

An app on Canopy isn't a dead end. Apps in the Canopy ecosystem both receive security from Canopy, as well as provide it. These apps can then become ecosystems of their own - with side apps that augment base utility and sub-apps which interoperate with the base application. It’s a simple way separate, yet augment base app utility without changing the underlying code. That's how you build a world, one app at a time 🌿

The builder behind Praxis, @MakDaVeli, is self-taught with no traditional coding background. He builds everything through AI-assisted workflows, entirely from his phone. In his words: someone without a conventional dev background can ship something real on Canopy if the idea and execution are solid. A full prediction market, built as a sovereign app, by one person. This is what Canopy is for.