Answered from live records · 2026-09-15
How does Sato Swap handle slippage and deadlines?
It is passed to the venue's own router as that venue's parameter, defaulted by the request schema, and a policy may cap it — over the cap the request is refused with both numbers, as of 2026-09-15.
Slippage and deadline, end to end. Sato Swap implements neither: it carries yours to a router that does, caps it where an operator said to, and reports the comparison. A quote is not a fill, and nothing here is a price opinion.
| Item | What happens |
|---|---|
| Where your number goes | Into the venue's own quote, as that venue's own slippage parameter. Sato Swap does not implement slippage protection — it carries yours to a router that does, and names the router. |
| When you omit it | The request schema in lib/swap/quoteRequest.ts supplies its default and bounds the maximum. A default is not a recommendation: the right number depends on the pair's depth, which we do not measure. |
| The policy ceiling | max_slippage_bps. Over it, the request is refused under slippage_over_max, carrying both the limit and the value asked for. |
| Deadlines | An optional quote validity. Over max_deadline_s, refused under deadline_over_max with the seconds compared. |
| What a quote is not | Not a fill. A quote is one venue's answer at a moment; what you get is settled on-chain by that venue's router, against depth that moved while you were reading it. |
| Price impact | Not modelled and not claimed. Quoted output is the sixth signal in the venue ladder, behind liveness, the observed record of our own daily checks and verification state — a better number from a venue that then does not answer is worth less than an answer. |
How this was answered
The slippage and deadline fields of the request schema in lib/swap/quoteRequest.ts, and the two policy checks in evaluatePolicy() that bound them — slippage_over_max and deadline_over_max, each reported with its limit and the observed value.
Every answer on this page is produced by one named function over Sato Hub's live records on the date shown. Nothing is typed by hand, no figure is carried over from a previous day, and an answer with nothing behind it says unknown rather than zero. The Sato Score measures how open, active and verifiable a project is — it is not a safety, quality or returns grade.
Go deeper
More questions
Sources — the projects' own repositories and docs
Cite this page
Sato Hub. "How does Sato Swap handle slippage and deadlines?." Sato Hub, updated 2026-09-15, accessed 2026-09-16. https://satohub.ai/answers/how-does-sato-swap-handle-slippage-and-deadlinesData last refreshed 2026-09-15; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0 and the machine-readable copy is linked in the page's Dataset metadata.