What can a swap quote cache safely reuse?

A cache is safe only when its key captures every input that can change the meaning of its result. Token pair alone is insufficient for a swap quote.

Partition by purpose

A proposed quote key includes provider version, chain, input and output assets, amount, trade direction, slippage, enabled sources, fee configuration and relevant account roles. Any field omitted from the key needs a documented reason it cannot influence the response.

The 0x distinction between price and firm quote illustrates why a cached browse estimate should not automatically become an executable request. Account-specific allowance and balance issues need their own freshness rules.

Control shared caches

A backend or CDN must not share an account-bound transaction across users. Review response cache headers and application storage together. The general HTTP semantics do not know whether a JSON object is a reusable price or a wallet-specific authorization request.

Negative caching also needs care. A no-route result can change with market state, while a malformed token address will not improve after a short delay. Give those outcomes different lifetimes.

Measure cache hits by object type and monitor stale-result rejection. A high hit rate is not success if users repeatedly approve a route that must be rebuilt. Before launch, use two accounts and two fee configurations to prove that the cache never crosses those boundaries.