Coming to Kraken! Meet SODA.
Coming to Kraken! Meet SODA.
With the release of the SODAX SDK v2, every team integrated with the SODAX SDK can now offer their users AAVE, LINK, DAI and WBTC on Polygon for swaps, borrowing and lending.
Four new Polygon assets are now live through the SODAX SDK and tradable from across 18+ integrated networks.
Partner applications integrating SODAX can route Solver-coordinated trades, lending and yield flows for the full new set without per-asset routing or liquidity infrastructure of their own.
One SDK integration. One growing asset set. The same execution system already shipping with our partners.
Four new Polygon assets join the SODAX-supported asset set within SDK v2. From now, every team integrated with the SODAX SDK can offer their users exposure to WBTC, AAVE, LINK and DAI on Polygon, available from across SODAX's 18 integrated networks, with the Solver coordinating execution and the SDK normalizing the underlying complexity.
For existing builders, the headline is short: a batch of new assets became part of the SODAX-supported asset set, and you didn't need to do anything more to support them than switch them on.
The new Polygon listings cover the most foundational DeFi primitives on the network:
WBTC, the BitGo-custodied 1:1 representation of Bitcoin, on Polygon.
AAVE, the governance token of the largest decentralized money market, on Polygon.
LINK, the native token of the Chainlink decentralized oracle network, on Polygon.
DAI, Sky's long-standing decentralized stablecoin, on Polygon.
SODAX does not issue or custody any of these assets. SODAX is the cross-network execution system now routing them.
With these 4 Polygon assets live in the SODAX SDK, partner applications can now surface, for their own users:
Cross-network swaps in and out of each asset on Polygon, from any other integrated asset, natively settled on both sides. No wrapped derivatives to track on the user's side, no manual routing, no app-hopping between tabs.
Cross-network trading and yield routing, with supplying, borrowing and collateral use cases live where supported on each asset, surfaced wherever the user already is.
Solver-coordinated execution. A user expresses an intent (e.g. "get me into WBTC on Polygon from USDC on Base"), the Solver finds the path, sources liquidity across networks, and settles natively on each side.
The integration is abstracted in the SDK. Wallets, DEXs, lending protocols and front-ends already shipping with the SODAX SDK can offer the full new set through their existing surfaces, typically a token-list refresh away.
SODAX is infrastructure for modern money. A cross-network execution and liquidity system spanning 18+ networks, including Ethereum, Solana, Arbitrum, Base, Avalanche, Sui and more. A Solver-based execution system coordinates trading, lending, borrowing, staking and settlement across networks.
Builders integrate SODAX through a modular SDK to bring cross-network features into their own products without standing up execution infrastructure of their own.
Each new asset added to the SODAX-supported asset set, like the 4 Polygon assets announced here, becomes addressable to every team already integrated. No additional work on their side.
Most teams expanding their asset coverage trade off depth for breadth: a new asset means a new integration, a new code path to maintain, new liquidity to source. Every additional asset compounds the maintenance surface.
The SODAX SDK inverts that pattern. New assets land on the SDK, and partner applications inherit them through the same integration they shipped on day one. The Solver coordinates routing and sourcing liquidity, the SDK normalizes execution, and partner teams stay focused on product.
These 4 Polygon listings are the latest assets to follow that path. The coming weeks bring a steady pipeline of further assets across SODAX's integrated networks, all reachable through a single integration.
If you want these new Polygon assets (and the rest of the SODAX-supported asset set) live in your product, explore our SDK at sodax.com. Existing integrators can update to v2 of the SDK and pick them up without further engineering.
