Ampere Protocol

Ampere Protocol is a stablecoin liquidity layer on Sui built using the Orbitals AMM design. Instead of splitting liquidity across dozens of pairwise pools (USDC/USDT, USDC/DAI, etc.) and forcing users into multi-hop routing, Ampere aggregates many stablecoins into a single shared pool. Since stables trade near the same peg most of the time, Orbitals concentrates liquidity around the near-$1 zone, giving traders near-1:1 swaps with low slippage and consistent quotes. LPs can choose “peg bands” (tight vs wide ranges) to balance capital efficiency vs depeg coverage—deep liquidity in normal conditions, and protection from being drained at unfair prices during depegs. On Sui, Ampere benefits from fast execution and can be composed into seamless DeFi flows.

Highlights • Built on Sui: fast finality + scalable execution for smooth stable swaps • Unified stable liquidity: one pool supports many stables → fewer hops, less fragmentation, better execution • Better UX: simple “stable convert” experience with predictable pricing • LP risk tiers: tight bands for maximum efficiency, wider bands for depeg insurance • Composable: can be routed by wallets/bridges/DeFi apps as the default stable swap primitive • Resilience: keeps the stable basket functional even when one asset drifts from the peg

We built Ampere natively on Sui by implementing the Orbitals AMM in Move. The protocol is organized using Sui’s object-centric model: a shared Pool object holds global configuration/state, while LP positions are separate on-chain objects that represent a user’s chosen peg band (tight/medium/wide). This makes accounting explicit, safe, and easy to index. We expose clean entry functions (add_liquidity, remove_liquidity, swap, quote) and leverage Sui’s fast execution for a smooth “stable convert” experience. On the app side we use Sui’s Programmable Transaction Blocks (PTBs) to bundle steps—e.g., swap + deposit/repay/bridge—in one atomic transaction, improving UX and reducing failed partial flows. The standout “hacky” bit is how we surface Orbitals’ banded risk model in the UI (risk meter + auto-routing): swaps default to ultra-tight near-peg liquidity, and if a stable drifts, the system naturally routes to wider bands instead of letting tight liquidity get drained.