Skip to main content

Documentation Index

Fetch the complete documentation index at: https://pond.dflow.net/llms.txt

Use this file to discover all available pages before exploring further.

JIT Routing (Just-in-Time Routing) re-optimizes a trade’s route at execution time, so the fill reflects current onchain prices instead of a stale quote. Some onchain venues, especially prop AMMs (proprietary automated market makers), update their prices fast enough that the route DFlow picks at quote time can be outdated by the time the transaction lands. JIT routing closes that gap by moving the routing decision onchain.

​
Why static routing struggles

  • Routes are computed offchain and locked into the transaction at quote time.
  • Prop AMM prices can move between signing and execution.
  • The trade either fills at a worse price or fails on slippage.

​
How JIT routing works

  1. Quote time. DFlow computes an initial route from current market data and embeds it in a transaction built so the route can be updated onchain.
  2. Execution time. JIT routing re-checks prop AMM prices just before executing each leg onchain. If a better path exists, it reroutes inside the same transaction.

​
When JIT routing engages

No builder configuration or extra parameters required. JIT routing engages when both of the following are true:
  • The trade goes through the Trading API (/order or /quote).
  • The route includes a prop AMM leg. Routes without one execute as static paths.
Prediction market trades execute through Concurrent Liquidity Programs (CLPs), which are not prop AMMs. JIT routing does not apply.

​
What builders get

  • Lower realized slippage. Trades fill against current onchain prices, not stale quotes.
  • Higher success rates. Fewer transactions fail because the market moved between signing and execution.
  • Tighter slippage limits. Less need for wide buffers to absorb pre-execution drift.