Skip to article

Beltfinance stablecoin swaps

Last updated -

Belt Finance uses a stable-swap automated market maker (AMM) for exchanges within one network. Its historical cross-chain design combined Orbit Bridge with a three-chain pool for transfers between networks.

Documented stablecoin swap fee
0.1% per stablecoin swap in Belt Finance's v2 fee guide. This figure does not establish a current all-in cross-chain rate.
Historical v3 pool assets
The 3Tether pool used USDT on BNB Chain (BSC), USDT on HECO, and KUSDT on Klaytn.

Network scope and swap choices

The MDEX Team's HECO shutdown notice of November 20, 2024, reported HECO's planned January 15, 2025, shutdown. Historical route descriptions do not establish live availability, including for routes between BNB Chain and Klaytn.

Same-chain pool swaps and historical v3 cross-chain directions
Swap option Output asset and network Starting asset and route requirement
Same-chain stablecoin pool Another stablecoin that the pool supports, on the same network. A stablecoin accepted by that same-chain pool.
BNB Chain (BSC) to HECO USDT on HECO. USDT on BNB Chain (BSC); both networks and Orbit Bridge were required.
HECO to BNB Chain (BSC) USDT on BNB Chain (BSC). USDT on HECO; both networks and Orbit Bridge were required.
BNB Chain (BSC) to Klaytn KUSDT on Klaytn. USDT on BNB Chain (BSC); both networks and Orbit Bridge were required.
Klaytn to BNB Chain (BSC) USDT on BNB Chain (BSC). KUSDT on Klaytn; both networks and Orbit Bridge were required.
HECO to Klaytn KUSDT on Klaytn. USDT on HECO; both networks and Orbit Bridge were required.
Klaytn to HECO USDT on HECO. KUSDT on Klaytn; both networks and Orbit Bridge were required.

Router legs and AMM connections

The historical Belt Router design separated bridging requests from optional swaps on connected AMMs. Its crossChain() function could request a cross-chain swap alone or add a destination-chain swap.

The swapAndCrossChain() function added an origin-chain AMM swap before bridging, optionally followed by a destination-chain AMM swap. A separate swap() function handled an AMM swap on the selected chain.

The v3 design named PancakeSwap on BSC, MDEX on HECO, and KLAYswap on Klaytn as intended AMM connections.

Slippage and confirmation time

Stable-swap pricing targets low slippage between similarly valued pool assets. Slippage concerns the difference between an expected exchange price and the price achieved during execution.

Beltfinance stablecoin swaps: Slippage and confirmation time - diagram

View image file

Cross-chain swaps require bridging confirmations, so Belt Finance described them as slower than same-chain swaps. The historical confirmation estimates do not establish a present completion deadline.

Beltfinance stablecoin swaps: questions and answers

Which asset returns if a historical cross-chain swap fails?

Belt Finance's historical BNB-on-BSC to KLAY-on-Klaytn example has three stage-specific outcomes. A failed initial AMM swap returns BNB on BSC to the user. Failure of the intermediate stable-swap on Orbit Chain returns USDT on BSC. If the destination AMM swap fails, the user receives KUSDT on Klaytn. Those outcomes apply to that documented route design.