Swing Integrates Across Protocol to Deepen Liquidity Directed to Swing
Swing has added Across to its growing list of Bridges.
A cross-chain application is only as good as its liquidity sources. There’s little point in creating a dApp that allows you to trade on half a dozen EVM chains, after all, if there’s precious little to trade there. That’s why we created the Swing – or one of the reasons at least: to provide the assets users need, when they need them and where.
That being the case, it brings us great pleasure to announce that Across Protocol has been integrated into Swing. “The bridge Ethereum deserves,” as it bills itself, Across Protocol is so much more, supporting cross-chain asset transfers between EVM chains. All of which make it the sort of liquidity solution that sits nicely within Swing , which is why we decided to integrate it into our cross-chain liquidity ecosystem.
Swinging Across the Cross-Chain Forest
It’s a jungle out there in DeFi-land. EVM chains, non-EVM chains, bridges, protocols and aggregators. All serving up varying degrees of liquidity and token-swapping services, but all of it fractured and splintered to all corners of the kingdom. Balkanized in fact. The Swing Widget, API and SDK were conceived as a solution to this problem by uniting these disparate liquidity sources into a single point of access.
Due to the way network effects work, the Swing API, SDK and Widget are strengthened with every new source of liquidity that’s added into the mix – particularly when it’s a major provider such as Across. For its users, the primary pain point Across Protocol solves is the need to wait hours or days when bridging funds to rollups and L2s. Across reduces this wait time to minutes at most.
At present, Across supports the movement of funds between Ethereum, Arbitrum, Optimism, and Polygon. These are the EVM networks where the majority of all onchain liquidity resides. Indeed, Across maintains a balance of liquidity on these networks, with a concentrated hub of liquidity on Ethereum. Relayers make capital available to end users and receive repayment from this liquidity system; that’s how it’s able to deliver cross-chain transfers so quickly.
These same liquidity pools can now be accessed by Swing’s smart contracts, which feed into our API. Tokens such as WBTC, ETH, DAI and USDC can all be swapped through the liquidity provided by Across and captured by the Swing Ecosystem. It’s a symbiotic solution in which all parties prosper.
In case you’ve forgotten, the purpose of Swing is to make it easier for developers to create cross-chain dApps. Specifically, it allows them to create outstanding decentralized applications without being sidetracked by all of the housekeeping this task traditionally entails.
At a bare minimum, operating within an omni-chain landscape calls for running multiple nodes, which can be slow to sync and costly to run due to bandwidth, storage, and server requirements. Swing Widget offers a low-code solution that allows dApp developers to concentrate on the core functions of the application, with Swing’s smart contracts keeping the cross-chain components talking the same language and swapping like-for-like assets in the background.
We’ve now reached the stage where over two dozen EVM and non-EVM chains are integrated with Swing. This is achieved courtesy of liquidity aggregated from a dozen cross-chain bridges and more than 30 DEXes. While Across Protocol won’t be the last integration we announce for Swing, it’s undoubtedly one of the most important.
Thanks to its arrival, the Swing ecosystem is significantly stronger and its value proposition is more compelling than ever. We march on!
Learn more about Across Protocol
👨💻 Get Started with Swing Today
📓 Learn more about Swing:
Website | Docs | Developers Hub
👥 Join the community: