Canopy✓

Need your CNPY on Canopy first? Every screen of the unwrap:

In the five weeks since launch, @canoliq shipped five app updates. This pace is unheard of in web3. More time building features, more time gaining traction, less time spent hassling with infrastructure. This is Canopy.

Hold CNPY on BNB Smart Chain? Bring it home. A few clicks in the Terminal and it is native on Canopy, ready to stake. Watch the unwrap, full guide:

Canopy is built so AI coding agents can ship onchain apps. The Canopy Development Skill is the latest piece: all 18 public repos mapped for plugins in 5 languages, RPC, signing, canopy-ts, and localnet testing. To show you how easy it is, we used canopy-dev-skill to build a custom tip transaction for Canopy’s Go plugin and tested it end to end on a local chain in 10 minutes with no coding. All the output and leaderboard data in it come from a real run on that local chain, not mock-ups. Try it:

The bridge fee from BNB Smart Chain to Canopy is flat: 1 CNPY, plus a 0.01 CNPY network fee. It doesn't scale with the amount. Unwrap 2 CNPY and 0.99 arrives. Unwrap 100 and 98.99 arrives. Anything at or under 1.01 is dust. Sizing a test transfer? Trust the "You receive" line.

Swapping CNPY for BTC on Canopy needs no wrapped BTC and no change to Bitcoin. The seller's CNPY sits in a committee's escrow. The buyer locks the order in a Bitcoin transaction and pays the seller. The committee sees it and releases the CNPY. Bonded CNPY backs every step.

If your stack speaks Ethereum JSON-RPC, it already speaks Canopy. Same network, two interfaces. A Canopy tx hash resolves with 0x in front of it, and history goes back to mainnet launch. Nothing to rewrite, no new SDK.

Congrats to @fhenix on mainnet. CoFHE brings encrypted compute to Arbitrum and Ethereum: contracts work on data that stays encrypted end to end, so private positions and sealed bids don't have to leave the composable onchain stack. Proud to be partnered with the Fhenix team.

Fhenix mainnet is live. What started as an idea to bring FHE-powered confidentiality to blockchains is now production-ready infrastructure, for you to build with. CoFHE is now live on @arbitrum and @ethereum, bringing confidentiality to onchain assets without compromising composability.

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.

RT @bitget: Put your idle assets to work with Bitget Simple Earn! Enjoy up to 365% APY. New rates just dropped. Start earning now! Start here:

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.

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:

RT @stakingcabin: Building on @CNPYNetwork starts with an idea, not with code. Today, builders bring their own AI agent, such as Codex or @claudeai Code, to customize the Canopy stack on @github and then hand it back for deployment. The goal is to make turning an idea into a working application as simple as describing what you want to build.

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.