Shade Bridge Tutorial – Generalized IBC, Axelar, Cosmos Connectivity + Privacy

Greetings community,
In this tutorial, we will walk you through the Shade Bridge – an interface that allows you to seamlessly bridge assets between different blockchains using the power of IBC. Additionally, we will walk you through the use of Axelar + Shade Wrap to give your ERC-20s privacy and the ability to interact with Shade DeFi.
To use the bridge, navigate to https://app.shadeprotocol.io/bridge
Shade Bridge – Generalized IBC + Privacy
The following are a list of key features of the Shade Bridge:
- Generalized IBC token transfers (Osmo <—> ATOM etc.)
- Transfer assets into Shade DeFi ecosystem
- Convert your public IBC assets into privacy-preserving equivalents
- Bridge private tokens like SHD & SILK to the broader Cosmos
The Shade Bridge is a key piece of Cosmos infrastructure that allows the internet of blockchains and their respective tokens to seamlessly leverage the power of IBC. Not only that, but never before has it been easier to empower your assets with privacy and onboard them into Shade DeFi!
The following is a list of supported blockchains on the Shade Bridge:
- Secret
- Osmosis
- Cosmos
- Stride
- Comdex
- Axelar
- Agoric
- Kujira
- Juno
- Stargaze
- Akash
- Gravity

Shade Bridge Tutorial Requirements
In order to use the Shade Bridge you will need the following:
- Keplr installed
- Tokens for gas / transfer
- ~1-2 minutes
To use the bridge, navigate to https://app.shadeprotocol.io/bridge

After navigating to the Shade Bridge, you will be presented with 4 key options:
- Where you are sending assets from
- Where you are sending assets to
- Which asset you are sending
- How much
First, select where you are sending assets from.











Portfolio

Axelar + Shade Wrap: ERC-20 privacy
The following are a list of key features of Shade Wrap:
- Convert ERC-20s into privacy-preserving equivalents
- Transfer Ethereum assets into Shade DeFi ecosystem
- Wrap any IBC assets with privacy
- Unwrap any private asset into the public version of the asset
Shade Wrap is particularly useful for any Shade Bridge assets that successfully transferred onto Secret Network but failed to be wrapped into their privacy-preserving equivalents. Users can easily navigate to the wrap page to finish the final step of the process of the multiexecute transaction only partially succeeds on the Shade Bridge.
Additionally, Shade Wrap can be used on any Ethereum assets that have been transferred into Secret Network using the Axelar bridge. The following is a list of supported Ethereum assets on the Shade Wrap page:
- WETH
- WBTC
- FRAX
- DAI
- USDT
- USDC
Axelar + Shade Wrap Tutorial

In order to use Axelar + Shade Wrap you will need the following:
- Keplr installed
- Metamask installed
- Eth gas
- SCRT gas
- ~15-20 minutes
To use the Axelar bridge, navigate to https://satellite.money/
To use Shade Wrap, navigate to https://app.shadeprotocol.io/wrap
Conclusion

Shade Protocol is an ambitious array of application-layer products focused on a simple end user experience that involves the incorporation of privacy by default. These interconnected privacy-preserving DeFi products built on Secret Network will change DeFi as we know it — empowering the next generation of value creation and exchange. Shade Protocol is launching Silk: a privacy-preserving over-collateralized stablecoin pegged to a basket of global currencies and commodities, built on Secret Network.
Without privacy, DeFi is incomplete. Traditional financial markets offer a degree of privacy for users, and as a result offer up greater protections in some capacity than existing DeFi markets. Shade Protocol will be the world’s first truly cohesive decentralized and privacy-preserving financial applications — ushering in a golden era for Web3. Shade Protocol will always push for privacy by default, privacy as an expectation, and privacy as the key to unlocking the full value of a decentralized future.
But we can’t do this without community. We need you to join our community and help make Silk and Shade Protocol a reality.
Join The Shade Protocol Community
The information provided in this Post pertaining to Shade Protocol, its crypto-assets, business assets, strategy, and operations, and is for general informational purposes only and is not a formal offer to sell or a solicitation of an offer to buy any securities, options, futures, or other derivatives related to securities in any jurisdiction and its content is not prescribed by securities laws. Information contained in this Post should not be relied upon as advice to buy or sell or hold such securities or as an offer to sell such securities. This Post does not take into account nor does it provide any tax, legal or investment advice or opinion regarding the specific investment objectives or financial situation of any person. Shade Protocol and its contributors and shareholders make no representation or warranties, expressed or implied, as to the accuracy of such information and Shade Protocol expressly disclaims any and all liability that may be based on such information or errors or omissions thereof. Shade Protocol core contributors reserve the right to amend or replace the information contained herein, in part or entirely, at any time, and undertakes no obligation to provide the recipient with access to the amended information or to notify the recipient thereof. The information contained in this Post supersedes any prior Post or conversation concerning the same, similar or related information. Any information, representations or statements not contained herein shall not be relied upon for any purpose. Neither Shade Protocol nor any of its core contributors shall have any liability whatsoever, under contract, tort, trust or otherwise, to you or any person resulting from the use of the information in this Post by you or any of your representatives or for omissions from the information in this Post. Additionally, Shade Protocol core contributors undertakes no obligation to comment on the expectations of, or statements made by, third parties in respect of the matters discussed in this Post.