Canopy airdropCNPY

What qualified participants did

1. Earned reward points on the Canopy testnet by building, running quests and using community apps
2. Signed in to the official claim portal with the EVM wallet used during the testnet campaign
3. Created or selected a Canopy destination wallet to receive CNPY
4. Submitted points, optionally several times, before the pre-mainnet snapshot closed the window
5. After mainnet, checked the named Canopy wallet in the official app; no further action was required

Where things stand

Canopy describes itself as a Web3 infrastructure layer built for AI-assisted development, where developers write ordinary code and the network handles consensus, validation and deployment. Its CNPY token is used as collateral for network security: native CNPY can be staked, directed to app committees and used for fees and governance.

The airdrop for testnet participants has closed. In an August 2026 post, Canopy opened a portal where users submitted the reward points they had earned on testnet. The mainnet launch post, dated 7 September 2026, says the submission window is closed, that eligibility and allocations were based on submissions on record, and that distribution goes to the Canopy wallet each participant named, with no further action needed.

We mark the status as ended because the qualifying window and the submission step are over. Canopy has not published a total airdrop size, a conversion rate or an explicit statement that every distribution has completed, so anyone who submitted and sees no balance should contact support through the official Discord rather than any third party.

How the testnet points campaign worked

According to the submission post, points were earned on the Canopy testnet through building, running quests and playing community apps. To be considered, users signed in to the portal with the EVM wallet used during the campaign, which let the portal read their points, and then created or chose a Canopy destination wallet. Each new submission added the points earned since the previous one, so users could update their total until the snapshot.

The post was careful about what submission meant. It did not guarantee eligibility, an allocation, a token amount or a distribution date; eligibility and allocations were set after the snapshot. CNPY was to be distributed at the token launch to the destination wallet named in the submission.

On anti-abuse rules, the terms summary in the post says eligibility and allocations are at the sole discretion of Canopy Network Corp., and that Sybil activity, restricted regions, below-minimum points, and gaming or botting may lead to disqualification. The exact thresholds are not published.

• Points came from testnet building, quests and community apps.
• Submission was required but did not guarantee an allocation.
• Sybil activity, botting and restricted regions could disqualify a wallet.

Moving CNPY and the risks to watch

CNPY also exists as a wrapped BEP-20 token on BNB Chain. Canopy published a guide on unwrapping it to the native chain through the Bridge section of app.canopynetwork.org. The bridge charges a flat 1 CNPY plus a 0.01 CNPY network fee, so very small transfers are not worth bridging, and the user needs a little BNB for gas. Native CNPY is required for staking and governance; the wrapped version on BNB Chain cannot be staked.

Creating a Canopy wallet in the app involves a password that Canopy does not store and cannot recover, so losing it can mean losing access. Before approving a bridge transaction, compare the contract address with the Official Links page in the Canopy docs, and reject it if it does not match exactly.

Canopy repeatedly warns that it will never message users first and will never ask for a seed phrase or private key. The official links page also warns about fake airdrops, giveaways, claim pages and token migrations. Because the airdrop required no claim after submission, any site now asking you to "claim" CNPY for the testnet campaign should be treated as a scam.

The unwrap itself is a single wallet confirmation labelled "redeem". The bridge then waits for at least six BNB Smart Chain confirmations, which the guide says usually takes about a minute, before native CNPY appears in the Canopy wallet. The most common mistakes the guide lists are using the Wrap tab, which sends tokens in the opposite direction, and connecting a different EVM wallet from the one holding the wrapped tokens, which shows up as a zero balance.

What to take from this drop

Canopy ran a fairly standard testnet-to-mainnet campaign: earn points by using the test network, submit them with a destination wallet, and receive tokens at launch. The useful lesson is the two-wallet design, where the EVM wallet proved the activity and a separate native wallet received the tokens.

For anyone who missed it, there is no open qualifying activity listed in the official posts we read. Staking native CNPY behind a validator is described as a way to take part in network security, but that is ordinary staking, not an airdrop, and it carries the usual slashing and price risk.

We will update this page if Canopy publishes final distribution figures or announces a new incentive program.