Finalizing the Transition: ShadeSwap Resumption & Accelerated Feather Snapshot Timeline

Shade Protocol
3

Burn Deadline Extended to August 21

TLDR

  • The SHD → Feather ($FTR) burn deadline is moving from August 5 to August 21, 2026 at 18:00 GMT+0. This is the final, permanent hard cutoff. There will be no further extensions.

  • Full Web3 interface for Shade is launching on August 5th.

  • Why: overwhelming community demand. The 7-day SHD unbonding period left a meaningful cohort of holders short on runway to unstake, get liquid, and burn in time. We heard you.

  • If you’re in by August 5, you are already captured. We have been taking rolling snapshots of the burn contract, and everyone who has burned is already secured in a completed snapshot. You do not need to do anything else.

  • If you burn between August 5 and August 21, understand the risk. We will keep taking rolling snapshots through the 21st, but we cannot guarantee Secret Network’s block uptime or the availability of surrounding infrastructure during that window. Burn as early as you can — do not wait until the 21st.

  • Nothing else about the migration changes. SCRT Labs is dropping official Cosmos L1 support on September 1. Any tokens left inside smart contracts at their September snapshot will more than likely be permanently lost.

  • The governance picture is genuinely unsettled right now. There is heavy tension across the ecosystem and no clear consensus on what happens next. That uncertainty is not background noise — it is the risk to anyone burning after the 5th.

Dear Community,

Two weeks ago we compressed the Feather snapshot deadline to August 5 to get a clean dataset locked well ahead of Secret Network’s September 1 L1 sunset. That decision was correct, and we stand by the reasoning behind it.

But the community response has been loud and consistent: the 7-day SHD unbonding lock, stacked on top of the wind-down steps, left a real group of committed holders scrambling. People who fully intend to transition to Feather were at genuine risk of missing the window through no fault of their own — simply because they started unbonding a few days later than ideal.

We would rather give those holders room to make it than lock a slightly cleaner dataset a week earlier. So we are extending the burn.

Here is exactly what is changing, what is not changing, and the honest tradeoff that comes with the extra time.

1. The New Deadline: August 21, 2026

The SHD deposit and burn contract will now permanently close on August 21, 2026, an eight-day extension from the previous August 5 cutoff.

This is the final deadline. We are not building in any further flexibility, and no additional extensions will be granted. When the contract closes on the 21st, it closes for good, and any SHD that has not been burned will not qualify for the $FTR allocation.

The reason for the extension is narrow and specific: the length of the SHD unbonding period. A 7-day unbond, plus the time needed to unwind LP and lend positions and get fully liquid, meant the August 5 date was unforgiving for anyone who came to the process late. August 21 gives those holders the runway to finish.

2. Rolling Snapshots — What “In by the 5th” Actually Means

We have not been waiting for a single deadline to capture the state. We have been taking rolling snapshots of the burn contract on an ongoing basis.

Practically, this means:

  • Everyone who burns on or before August 5 is already secured. Your burn has been — or will be — captured in a completed snapshot, and that record is safe regardless of what happens to the network afterward. If you are in by the 5th, you are done. You do not need to monitor anything or take further action.

  • Between August 5 and August 21, snapshots continue. Every burn in that window will be picked up by a subsequent rolling snapshot, exactly as before — as long as the network is healthy enough to process your transaction and for us to read it.

That second condition is the crux of this update, so we are going to be direct about it.

3. The Honest Caveat: We Cannot Guarantee the Network After the 5th

We built the original August 5 date specifically to lock our dataset well before any September 1 migration turbulence. By extending into the second week of August, we are trading a margin of safety for a margin of time.

We are giving you that time. But we have to be candid about what it costs.

For any burn after August 5, we cannot guarantee Secret Network’s block uptime or the availability of the surrounding infrastructure — RPC endpoints, indexers, and the tooling the burn flow depends on. When a foundational L1 approaches a support cutoff, the risk of validator churn, degraded block production, RPC blackouts, and general instability rises sharply and unpredictably. If the chain halts, stalls, or the infra you need to submit a burn goes dark during the August 5–21 window, we may not be able to help you complete or recover that transaction.

And this is not a distant, theoretical worry. Right now there is significant governance tension across the ecosystem, and no one — including us — can tell you with confidence what happens next. The path from here to the September migration is contested and unsettled, and that lack of consensus is precisely the danger. Contested governance on a sunsetting chain is how validators drop off, how RPCs go dark, and how a network becomes unreliable with little warning. The volatility itself is the direct risk. We are not going to pretend we can forecast a situation that the people running the infrastructure cannot forecast either.

To be unambiguous:

  • Burning by August 5 = guaranteed capture. Your allocation is already locked in a completed snapshot.

  • Burning August 5–21 = we will still snapshot you, but at your own network risk. If Secret’s infrastructure degrades before your burn confirms, that is a scenario outside our control.

The extension exists to give latecomers more of an opportunity, not to encourage anyone to wait. If you can burn now, burn now. Every day you delay past the 5th is a day you are relying on a sunsetting chain to stay up.

4. Everything Else Stands

None of the underlying migration reality has changed:

  • SCRT Labs is migrating $SCRT to Arbitrum and dropping official Cosmos L1 support on September 1, 2026. Any tokens left inside smart contracts at their September snapshot will more than likely be permanently lost.

  • ShadeSwap and SILK state remain unfrozen so you can unwind positions and get liquid. Use them to exit cleanly — do not leave capital sitting inside pools, lend positions, or wrapped assets.

  • stkd-SCRT still carries a 21-day unbond. If you are still holding it and have not started unbonding, the math no longer works for the burn window — you should have triggered it already. SHD’s 7-day unbond is the one the August 21 date is built around.

5. What To Do Right Now

If you have not yet transitioned, do not treat the extension as breathing room. Treat it as a final grace period on a chain that is winding down.

  1. Unstake immediately. Trigger the 7-day SHD unbond today. Every hour of delay eats into your safety margin against the 21st.

  2. Clear your contracts and pools. Withdraw 100% of ShadeSwap liquidity, repay and close SILK / ShadeX lend positions, and unwrap all SNIP-20 / privacy-wrapped assets back to native form.

  3. Burn as early as you can. Once your SHD is liquid, visit the official Shade Burn Contract interface, enter your verified EVM address, and submit the one-way burn. Aim to be in by August 5 to lock a guaranteed snapshot. If you genuinely cannot, burn as far ahead of August 21 as possible — do not gamble on the network’s final days.

Closing

We extended this deadline because the community asked, and because the people asking are exactly the committed holders Feather is being built for. Giving them the room to make the transition is worth the added complexity.

But we owe you the full picture, not just the good news. The extra week is real, and so is the risk that comes with operating on an L1 in its final weeks of official support. Everyone in by the 5th is already home free. Everyone after that: we’ve got your snapshots rolling, but the clock — and the network — are no longer fully in our hands.

Get liquid. Burn early. Don’t wait for the 21st.

Feather is working, with lending live and TVL growing across multiple chains. Let’s finish the transition cleanly and build what comes next.

Official updates: Telegram — @ShadeProtocol