Docs
Ctrl K
Open the app
Getting startedTradingTokenFor agentsSDK file
Trading

How the speed works

Fastlane moves every slow step before the click. The click sends signed bytes to six Jito block engines and the RPC at the same moment and times the confirmation.

usual wallet, after the clickblockhashfeessimulatesign in popupsend to one RPCpollfastlane, after the clicksend x7 + confirmsix Jito engines and the RPC, in parallelblockhash, compute units, priority fee, tip, simulation and signature are done when the button shows its green dot

Before the click

  • Plan: /api/plan builds the instructions: a buy or sell on the pump.fun bonding curve while the coin is on it, a Jupiter route (PumpSwap and other pools) after it graduates, or a pump.fun create plus your first buy.
  • Blockhash: fetched every 2.5 s. Each new one re-signs every armed button, which takes microseconds and no network.
  • Compute units: the limit is what the simulation used, plus 15%. A tight limit is cheaper and schedules sooner.
  • Priority fee: the 75th percentile of the network's recent prioritization fees (at least 20,000 micro-lamports per CU), times 1, 2 or 4 as you choose.
  • Jito tip: 0.00001 SOL by default (up to 0.0005), a transfer to one of Jito's eight tip accounts, last in the transaction.
  • Simulation: simulateTransaction on the latest state, from your address. Only a transaction that passes is signed. Each button is rebuilt every 6 seconds and after each send.

The click

The browser posts the signed bytes at the same moment to the public Jito block engines (the global one, Frankfurt, Amsterdam, New York, London, Salt Lake City) with sendTransaction, and to the RPC with skipPreflight. No key is needed. Whichever path reaches the leader first lands it; the others are dropped as duplicates. The wallet then polls getSignatureStatuses every 120 ms until the transaction is confirmed. If the signed transaction is older than 15 seconds of simulation, it is rebuilt first, and that time counts in the ms.

Simulation and slippage

Every buy and sell carries a limit at your slippage (3% by default, 1% to 20% in the app): the most SOL a curve buy may cost, the least SOL a sell must return, or Jupiter's minimum out. If the price moves past it, the simulation fails and the button turns to blocked with the reason. Nothing is signed or sent, so nothing is spent. Between the last simulation and the click the price can still move; then the limit makes the transaction fail on chain for its network fee only, and the 0.5% fee is not paid because it sits in the same transaction.

The ms log

The wallet measures from the click to the confirmation with performance.now(). Each landed send is posted to /api/ms, which keeps it only if the signature is confirmed on chain without error. The home page counters read the same log. Your own log stays in your browser.

PreviousThe walletNextLaunchers