Swing

Swing is a decentralized cross-chain crypto protocol that aggregates liquidity from decentralized exchanges (DEX) and bridges across major blockchains. It powers trading for thousands of popular cryptocurrencies.

The founder, Viveik Vivekananthan, started with a strong desire to create a cross-chain liquidity solution for projects on the Polkadot and Ethereum ecosystems. It has since become evident that the value proposition this technology offers to crypto users, and the revenue Swing can start generating in the immediate future will grow exponentially if the project can offer cross-chain liquidity capabilities across all major blockchains.

The first targets include Polygon, Binance Smart Chain, Avalanche, Arbitrum, Optimism, HECO, Near, Solana, Terra, Harmony, and Fantom.

With a mission and a vision that stretch far beyond the Ethereum and Polkadot ecosystems, it makes sense to embrace a new name that matches the ambitions of the cofounders. Swing’s base of 14,000 Telegram users is continuing to grow fast and the rebrand will only heighten the excitement and awareness of the project in the crypto community.

Trade and swap cross-chain liquidity

Swing's cross-chain swap feature allows two tokens to be exchanged in a trust-less manner quickly. We aggregate DEX liquidity across every major blockchain including Ethereum, Polygon, Avalanche, Binance Smart Chain, Arbitrum, Optimism, Polkadot, Solana and more!

Move liquidity between blockchains

Seamlessly transfer liquidity with low slippage on any chain and provide liquidity to DEXes, yield farms, lending/borrowing and staking protocols.

Earn Swing Tokens

Participate in our staking program and earn token cashflows in the form of Swing as positive slippage is generated on our trading platform.

Power your project with Swing API (coming soon)

Interested in using Swing to power cross-chain trades or add TVL to your protocol? Reach out and we'll get in touch directly!

The Swing protocol smart contracts will be audited, and it is designed with security as its top priority. The code will be audited twice by professional security firms during our testnet and cross-chain deployment.

Swing Protocol solves the cross-chain liquidity fragmentation problem in two distinct phases:

• Phase One: deploying single-chain aggregator contracts on each blockchain to aggregate DEX liquidity on every major blockchain
• Phase Two: Multi-chain contract communication interactions via trustless bridge solutions using Connext, Hop (for EVM-compatible chains), Rainbow, Snowfork, Wormhole and many more.

Single-chain aggregator implementation

The first phase of Swing is to deploy aggregators to all the major blockchains including Ethereum Layer 1, Ethereum Layer 2s (Arbitrum, Optimism), Polygon, BSC, Avalanche, xDAI, Heco, Fantom, etc.

Cross-chain Bridge Implementation

Swing will work with multiple bridges for cross-chain swaps. A minimum criteria is that it is trust-minimized and a generalized solution for multiple EVM chains.

The above is an example flow of how a cross-chain swap works with one example of a bridge we aggregate across.

The user sends a request to Swing's backend in order to get an expected return from liquidity pools on the same chain and cross-chain. To better demonstrate the process, we assume the user starts from Ethereum and he/she gets a better price from the liquidity pool on Polygon. Once he/she approves the token and triggers swap through Swing frontend, Swing frontend will send a POST request to Swing backend, which connects to Connext. It will trigger the following steps within the Connext bridge:

1. After Connext router receives requests from Swing backend, it will respond with sealed bids containing commitments to fulfilling the transaction within a certain time and price range.

2. Swing sends a transaction to Connext TransactionManager on Ethereum which locks up funds on Ethereum.

3. Router locks up a corresponding amount of liquidity on Polygon.

4. Swing signs a message and sends it to a relayer on Ethereum. The Connext relayer (which is typically another router) then submits the message to complete the transaction on Polygon and claim the funds locked by the initial router.

5. The relayer will send a request to the contract deployed on Polygon by Swing with the corresponding calldata.

After Connext triggers the contract deployed on Polygon, it will swap tokens on Polygon based on the path (which is included in the calldata) and deposit the destination token to the user's address (which is the same as their input address) on Polygon.