As the premier decentralized exchange on zkSync Era, Sophon, Linea and Scroll, SyncSwap has shown that focusing on innovation and UX improvements can produce a great product experience.
One challenge with the current UX is that as the blockchain space fragments into more rollups, users have assets scattered across different chains. For example, a user might want to deposit on one chain, but have the source assets on other chains. Currently that requires leaving the app and going to other tools (like bridges).
Nexus solves this issue by providing an in-app flow that allows the user to directly provide the needed asset without having to leave the app. For SyncSwap, this would allow token swaps without first bridging, or depositing off-chain assets directly into liquidity pools.
We also deeply care about the integration experience to go as effortless as possible, hence the integration can simply be done on the frontend side, just add the nexus react component, pass a few configs based on your dapp and user choices and that’s it!
The purpose of this document is to compare the before vs after integrating nexus into SyncSwap’s frontend based on various milestones, while touching on the benefits for each step forward.
https://www.tldraw.com/f/KqX9dV4VYUcZBlGbTc-g1?d=v-642.-943.8438.5208.D3KnGiLfDECrhkKvATUiC
What it does: Users can deposit into any SyncSwap pool through their token of choice, as long as they have that token on ANY of the supported chains.
Example: Want to add USDC/ETH liquidity but your USDC is on Polygon and ETH is on Arbitrum? No problem. One transaction handles everything.
Technical approach:
<NexusBridge/> react component whenever a user has insufficient balance for a token they’ve opted for.