User Guide

Rug Exchange currently executes swaps on mainnet only. If you are in mainnet mode, you are using real funds.

Keep a small SOL buffer in your wallet for transaction fees. Protected and Private required can add a small extra SOL cost when the landed swap uses Jito.

Review the quoted minimum received amount before confirming. This value is enforced in the transaction.

Click Connect Wallet in the header or on the main action button.

If your wallet cannot sign messages, switch to a supported wallet (for example Phantom, Solflare, Backpack, or Coinbase Wallet).

The exchange opens with wallet sign-in and invite access checks. If your wallet is not admitted yet, enter a valid invite code or join the waitlist from the access screen.

1. Choose the input and output tokens.

2. Enter the amount to swap. Use MAX only when you understand fee reserve behavior.

3. Pick an execution mode: Cheapest (RPC only), Protected (Jito preferred with RPC fallback), or Private required (Jito only).

4. Review route, fee, slippage, and minimum received.

5. Click Review Swap, then Confirm Swap.

6. Approve in your wallet. Protected mode can ask your wallet to sign both a Jito primary transaction and an RPC fallback transaction.

7. Wait for confirmation. After success, the UI shows whether the landed transport was Jito or RPC.

1. Open /liquidity and select the venue you want.

2. propAMM is the current router-backed LP venue. Strongtower LP is available for LP actions, but the exchange Rug LP swap lane stays propAMM-backed until router support for strongtower is enabled.

3. Connect your wallet, review the position panel, then build a deposit or withdraw draft.

4. The UI only submits after you sign the draft transaction in your wallet.

5. If the pool is still protocol-owned, the strongtower panel will show that bootstrap is still required before public LP is allowed.

The router selects a route and includes minimum-out checks in the signed transaction.

Protected mode prefers Jito for private transport and can fall back to RPC. Private required fails closed instead of using public RPC.

If route quality changes or liquidity is unavailable, the app may show warnings or block submission until conditions improve.

If the router enters degraded pricing mode, the swap panel will show that quotes are coming from a fallback multi-source midpoint quorum and that spreads or max size may be temporarily tightened.

Always verify token symbol and amount before signing.

No route available: try a smaller amount or a different token pair.

Stuck on wallet signature: open your wallet and approve/reject the pending request.

Transaction failed: confirm you have enough SOL for fees and retry with a smaller size or a fresh quote.

Private required failed: Jito was unavailable or too slow; retry later or switch to Protected if public RPC fallback is acceptable.

Need more help: contact your team channel.

Invited users can create per-wallet bot API keys at /settings/api-keys.

Agent bootstrap skill: /skill.md.

Quick start: connect wallet, create a labeled key, copy the one-time secret, then configure your bot auth headers and signature.

Keys are bound to the wallet that created them. Bot requests may only quote, build swaps, and relay transactions for that same wallet.