Skip to main content

​
How routers see your pool

Jupiter, Titan and OKX route to Hadron pools today. Each router runs an adapter that reads your pool’s accounts, recomputes the quoting equation off-chain and sends the swap.
  • Routers quote what’s on-chain, minus account-based triggers. They see a midprice update as soon as it lands.
  • With a staleness limit set, a pool past its limit drops out of routes until you update it.
  • Routers only route to Initialized pools.
A new pool can take up to 30 minutes to start receiving flow. Each router has its own rules for picking up pools, but as a rule of thumb, about $1,000 of inventory on both sides and a spread under 500 bps on each side is enough to receive flow.

​
Flow segmentation (spread triggers)

A pool can carry a SpreadConfig: a list of triggers, each matching something in the swap transaction. Matching triggers add up to one net adjustment for that trade.
  • Surcharges widen your price for flow you consider toxic, such as a competing venue’s pool, a known arbitrage wallet, or any router you don’t trust. A total of 10,000 bps or more blocks the trade.
  • Discounts tighten it for flow you want, such as users of a partner frontend that co-signs their trades. A discount has to match a transaction signer, so passing an account isn’t enough to claim it. The factor clamp still applies.
  • Jupiter is rolling out attested routes. Once they’re live, a trigger can price Jupiter flow by tier (Ultra, Manual, paid or free API).
  • To create a spread config, your pool authority needs to be allowlisted by Hadron. Send us the wallet. See Segmenting flow.