Shade Launch + SNIP Migration Update

Greetings community,

I wanted to give an update to the Secret Network community on the state of Shade Protocol product launches. As of right now, the following are mainnet ready (post SNIP25 launch and testing):

  • ShadeSwap
  • ShadeLend
  • Silk

As a result of the recent SNIP privacy disclosure, we are developing a migration interface to make the transition from old SNIPs to new SNIPs as simple as possible for the entire Secret Network community. Additionally, we are aiming for ShadeSwap to launch with SNIP25 tokens for liquidity pools so as to not fracture liquidity between the old and new standard (whenever possible). Another benefit is to simplify the UI/UX for users arriving from the broader Cosmos. Finally, Shade values the security and privacy of the SNIP standard.

The migration experience is live on testnet:

All that remains is SNIP25 deployment to mainnet for us to deliver these products to the Secret community. We are highly confident in the agile and rapid efforts of SLABs with their work on hardening the existing SNIP standard into the SNIP25 standard which will improve the overall baseline data security of the de facto token standard on Secret Network.

Currently, we are dedicating two developers to internal auditing & testing the provided SNIP25 standard to ensure it works as intended on both testnet and mainnet. After well over a year of development on these Secret DeFi products, we are extremely excited to ship these products and begin deepening DeFi liquidity on Secret Network. None of this would be possible without you the community, we appreciate all of your support and feedback during the various testnet phases.

-Carter W.


Greeting community,

As an update, linked here is a video of what this process looks like on testnet (and mainnet once SNIP25s are ready). Huge shout-out to Austin W. & Sisson for getting this migration product put together so rapidly!


Migration is officially live on Secret Network mainnet to SNIP25s:

Blog post:

1 Like

How does a user use decoy addresses to preserve recipient address privacy under this system?