A protocol is winding down and asked holders to burn first — what an undisclosed allocation promises

Shade Protocol is shutting down its applications on Secret Network, and its exit offer asked holders to permanently destroy their SHD tokens before 18:00 UTC on August 21 in order to qualify for a future allocation of a new token called Feather. The allocation ratio, the amount, the price and the distribution date were all left undisclosed. That deadline has now passed, but the wind-down has not finished, and the part that still matters for anyone holding positions is getting funds out of the protocol's contracts.

The burn itself worked through a form on Shade's app: submit SHD, record an Ethereum-compatible address, and the transaction destroys the tokens irreversibly. By the project's own explanation, the process did not guarantee a specific amount, price or timeline for Feather. Missing the deadline cost eligibility, and meeting it cost the SHD. On Friday morning the app displayed 4,658,007 SHD under a global total burned figure and 3,718,238 under a supply label, though that second number is not a verified count of tokens still eligible to burn.

Shade's deadline notice also carried a warning about a separate event, a proposed September 1 snapshot for migrating SCRT, Secret Network's own token. Secret governance has since gone the other way. Voters rejected proposal 360, which would have migrated SCRT to Arbitrum, and it was not executed. That plan would have excluded sSCRT, bridged SCRT, IBC assets and balances sitting in liquidity pools or other contracts from the snapshot, so those exclusions no longer apply to anyone.

What passed instead was proposal 365, a community-continuance upgrade for the existing Layer 1 scheduled at block 26,790,327, under which existing SCRT stays on the current chain, including positions held inside contracts. Separately, SCRT Labs plans to end its own development and support for the Cosmos-based Secret L1 on September 1, with the approved community plan aiming to keep the network running under new stewardship. One September 1 concern fell away, in other words, and a different one remains.

Shade continues to urge users to withdraw from pools, lending products and wrapped-asset positions, and that instruction is the practical core of any wind-down. Contracts generally keep working after a team stops maintaining them, but the interface you use to reach them may not, and a front end that quietly stops being updated is one of the ordinary ways positions end up stranded.

Two things are worth carrying out of this if you are new. An irreversible action taken in exchange for undisclosed terms is a bet on a team's goodwill rather than a claim on anything specific, and a countdown is a device for compressing the time you spend thinking about that difference. And when a project announces it is winding down, unwinding what you already hold in its contracts comes before chasing whatever new token is being offered. Confirm governance outcomes through the network's own channels rather than through replies or direct messages, because wind-downs are exactly the moment when imitation migration and claim sites appear. This is information, not advice.