WAXP documentation

Trade with the
whole route in view.

A practical guide to quotes, executable routes, wallet review, token capabilities, and failure recovery on WAXP Exchange.

01 · Routing

Best executable output—not the prettiest preview.

WAXP compares supported direct, multi-hop, order-book, automated-market-maker, and split candidates. Candidates compete by the amount expected to reach the receive side after the route can be represented as a bounded transaction.

Available sources may include Alcor, Defibox, Taco, NeftyBlocks, ADEX, and WAX Fusion when their current pools, markets, contracts, and transaction adapters are supported. A venue name in token metadata does not guarantee usable liquidity.

Selection ruleThe displayed winner must have positive output, a current route identity, and a transaction path the service can prepare for wallet review.
02 · Review

The route may refresh. Your approval never should.

  1. QuoteCurrent supported liquidity is searched and ranked.
  2. ChallengeThe selected route becomes an unsigned, receiver-bound transaction.
  3. PreflightThe exact transaction is checked against current chain state before the wallet opens.
  4. AuthorizeYour wallet displays and signs the reviewed transaction locally.

If liquidity moves or a compute check rejects the route, WAXP fails closed or shows a replacement for a new review. It does not silently ask the wallet to sign a different transaction.

03 · Protection

Slippage protects minimum received.

Slippage is the maximum allowed difference between the reviewed output and the minimum the transaction accepts. A smaller percentage offers tighter protection but may fail more often in moving or transfer-fee markets.

Token contracts can deduct value during transfer. When the server has exact evidence of that behavior, WAXP may require or recommend a higher threshold and will show the new minimum before wallet review.

Choose your default slippage →
04 · Capabilities

A ticker is not a promise of execution.

Token identity is always ticker plus contract. Some listed tokens can be bought but cannot be sold, can be sold but cannot be received, or have no current executable route. WAXP publishes direction-specific capability restrictions when exact contract evidence proves a path cannot execute.

Unsupported directions are blocked before wallet review. A truthful “no route” is different from a broken transaction: it can simply mean current liquidity is absent or below a contract minimum.

Inspect the token catalog →
05 · Fees and output

Inspect what the transaction actually does.

Venue fees, pool fees, order-book economics, price impact, and token transfer behavior can affect received output. WAXP ranks supported candidates using current route economics, then shows minimum received and the route before authorization.

Blockchain resource requirements and external venue behavior remain outside WAXP custody. Always verify token contracts, amounts, memos, and actions in your wallet.

06 · Failures

Recover with evidence.

Quote moved
Refresh and review the new output and route.
Balance too low
Refresh the exact contract balance or enter a smaller amount.
Unsupported direction
The token contract or venue path is blocked before wallet signing.
Support code
Copy the complete `swap_…` value with direction, amount, wallet, and approximate time.
Troubleshoot or report a problem →
Non-custodial boundary

WAXP never needs your recovery phrase.

WAXP services prepare and validate unsigned transactions. They do not possess your private key and cannot sign or broadcast for you. Never share a seed phrase, private key, recovery phrase, or wallet password with support.