Wido Docs
What is Wido
Wido /wide-oh, as widely open/ is a multi-chain zap infrastructure. We build SDKs and Widgets that let dApps enable cross-chain zaps with any token.
In today's web3, too many transactions are needed to move tokens into desired destinations. Users need to use DEXes and Bridges before depositing their funds. dApps are losing users because of that friction. Web2-style payments are not possible.​
Single-click actions are table stakes in web2. Web3 won’t go mainstream until we match that.
Zaps try to solve this problem by combining multiple transactions. But Zaps have three key problems:
  1. 1.
    Zaps are only single-chain.
  2. 2.
    Zaps only work with a handful of tokens and protocols.
  3. 3.
    Zaps require new Zap contract deployments to support new vaults and protocols.
We also see many new entrants building SDKs and Widgets offering DEX and Bridge aggregation, enabling any-to-any token swaps with a single click. Those solutions are missing support for non-liquid tokens. We need a solution that would work with any token, regardless of its liquidity.
Wido is the first to enable liquidity migration for any token or contract across any chain or rollup.
Wido supports true any to any liquidity migrations thanks to its three unique design characteristics:
  1. 1.
    Wido works multi-chain and multi-rollup, only possible thanks to cross-chain messaging enabled by platforms like Layer Zero.
  2. 2.
    Wido works with any token, even tokens with no liquidity. Possible thanks to our unique routing mechanism.
  3. 3.
    No contracts need to be deployed to support new tokens or protocols. No Solidity expertise is required. We have a no-code tool that anyone can use to add support for their protocol. This minimizes the time to create support for new vaults from weeks to minutes.
Last modified 1mo ago
Copy link