NASDANK Docs
Open app
Trade/Ultra swap

Ultra swap

Ultra is NASDANK's own swap interface. It routes through the Uniswap UniversalRouter, shows you the route it will take, simulates before you sign, and charges 1% in the wrapped gas token.

What a market swap actually sends

Ultra builds a single execute(bytes commands, bytes[] inputs, uint256 deadline) call on the UniversalRouter. The command sequence is short and worth reading, because it tells you exactly where the fee is taken.

DirectionCommands, in order
Buy — gas token → coinWRAP_ETHPAY_PORTIONSWAPSWEEP (sweep on V4 only)
Sell — coin → gas tokenSWAPPAY_PORTIONUNWRAP_WETH

The swap opcode itself is venue-specific: V3_SWAP_EXACT_IN, V2_SWAP_EXACT_IN or V4_SWAP.

The fee is always taken in wrapped gas token

PAY_PORTION skims 100 basis points — 1% of the wrapped-gas-token leg to the Ultra treasury. On a buy that happens after the wrap and before the swap, so the swap trades post-fee. On a sell it happens after the swap and before the unwrap. Either way you are never charged the fee in the coin.

The 1% Ultra fee

Rate
1%
100 bps, fixed
Currency
WETH / WBNB
Never the traded coin
Applies to
Ultra only
Not to other routers
Funds
Referrals
15 / 5 / 0.3% three tiers deep

This is separate from and additional to the coin's own pool fee. A 1% Custom coin traded through Ultra costs 1% to the pool and 1% to Ultra. Trading the same pool through any other router costs the pool fee only.

Money safety on every swap

Four things happen before your wallet is ever asked to sign:

  1. Quote on chainNot from the indexer. QuoterV2 for V3, the V4 Quoter for V4.
  2. Compute a fresh minimum receivedFrom that quote and your slippage setting, at the moment of sending.
  3. SimulateAn eth_call of the exact transaction. If it reverts, the swap is abandoned with a real reason rather than sent hopefully.
  4. Then signAnd only then.
A minimum received must be a minimum

If an interface shows a "minimum received" that is not actually encoded as amountOutMinimum in the transaction, it is a decoration and not a protection. Check the calldata if you are unsure. Ultra encodes it.

Slippage

Presets of 0.1%, 0.5% and 1%, or type your own. The setting feeds directly into the minimum-received calculation.

On a fresh, thin pool, slippage is not the main risk

A new launch has all its depth in one position and very little of it near spot. A modest buy can move the price several percent legitimately, and a tight slippage setting will simply make your transaction revert. That is the setting doing its job.

Route disclosure

Ultra shows the execution route it will use — which venue, which pool, which fee tier. This matters more than it sounds: a coin may have pools at several tiers, and the deepest one is not always the one a naive router picks. If the route shown is not the pool you expected, that is worth investigating before signing.

Bridging

Ultra carries a Bridge tab for moving the gas token between chains. Two things to know:

Inbound bridging into Robinhood Chain has been intermittent

Transfers destined for chain 4663 have been observed to refund first and then fill hours later. If a bridge appears to have failed and refunded, do not assume it is finished — check the destination before re-sending, and keep the refund receipt.

Wallet support

  • Standard EIP-6963 browser wallets are supported and discovered automatically.
  • A wallet that cannot add or reach Robinhood Chain cannot be used there, however well it works elsewhere. The network needs to actually be reachable by the wallet's own RPC.
  • The chain switcher acts on the wallet you are connected with. If you have several wallet extensions installed, connect the one you intend to use before switching networks.

Beyond market swaps

Ultra also carries Limit, DCA and Counter orders, which are signed rather than sent and executed by a keeper when their trigger fires. Those have their own rules and their own failure modes — see Standing orders.

© NASDANK Not affiliated with Robinhood Markets, Inc. Risk disclosures nasdank.fun