SLON · BRIDGE & SWAP

The SOL to slonSOL bridge is closed. Deposits are not accepted.

Read this before you send any SOL. If you cannot afford to lose the SOL, do not send it.
slonSOL SUPPLY
—
SOL LOCKED
—
BACKING
—
STATUS
—
1. Deposits are closed.
Do not send SOL. The bridge is off on the current chain, so SOL sent now cannot be credited as slonSOL. The deposit address has been taken off this page. The SOL already in custody is shown above as SOL LOCKED.
2. When the bridge is enabled, the bridge operator mints slonSOL to your wallet 1 SOL → 1 slonSOL, to the same wallet you sent from, on the SLON testnet.
3. Use slonSOL: hold it, swap it for SLON once the AMM is live, or redeem it (see the slonSOL → SOL tab).

Each slonSOL is meant to be matched 1:1 by SOL in the custody wallet above. That wallet is held by the operator, not by a program. A chain restart erases slonSOL balances on SLON while the SOL stays in the custody wallet. Live figures are at the top of this page.

1. Burn slonSOL on the SLON testnet (Redeem) — specify your Solana-mainnet recipient.
2. The operator releases SOL from custody to your mainnet address. This is a manual step: no code sends the Solana transfer automatically, and the bridge is switched off on the current chain.

CLI today: bridge_redeem <wallet> <blockhash> <amount> <nonce> <mainnet_recipient>
A one-click redeem button lands with wallet-connect (next).

slonSOL ↔ SLON (native)AMM — coming soon

The on-chain AMM (AeX402, program 3AMM53MsJZy2Jvf7PeHHga3bsGjWV4TSaYz29WUtcdje) is being deployed to the SLON testnet. The slonSOL/SLON swap pool goes live right here once liquidity is seeded.