mirror of
https://github.com/luxfi/graph.git
synced 2026-09-24 00:26:07 +00:00
zeekayandHanzo Dev
e2a5e254d8
exchange-api answered /v1/quote, and it was the last TypeScript service standing in front of this one. Its route search could try two intermediaries, WLUX and LUSD, because those are the two someone typed into a list — while the indexer beside it holds the whole pool graph. Searching the real graph finds what the list cannot: WLUX to LUSD pays 1221887840049623 through LBLAST against 611022579164403 direct, twice as much, on the same block. A quote is two questions and they have different authorities. Which pools could carry the trade is the index's to answer, and that is why the endpoint belongs here. What a pool actually pays is the pool's: a constant-product pair is its two reserves, and that arithmetic is in this file, exact, in integers; a concentrated pool is a walk across whatever ticks the trade crosses, and only its quoter holds the tick map. Doing the concentrated case here was tried and measured before it was rejected. Treating a pool as constant-liquidity around slot0 is exact while a trade stays inside the current tick and wrong the moment it does not — 15% high on CYRUS/LUSD, 44% on Z/LUSD, 89% on TRUMP/LUSD, every error in the direction of promising output the pool cannot pay. Those are the pools holding their liquidity away from spot, which is most of a thin book. Closing the gap needs the tick map; the tick map is not indexed, and event-sourcing it is exactly what valuation.go already declined to do for reserves. Constant-product pairs are quoted here for the first time. QuoterV2 is a V3 contract and never knew them, so the one pair on Lux mainnet has been invisible to the swap form; it prices at 987158034397061298 for a token in against its 100/100 reserves, read live. The store cannot tell a pair from a pool — handlePairCreated records feeTier 3000 whichever it is — so the pool is asked, once, and the answer kept for as long as the process runs. A pool that answers neither is left out rather than guessed at. Eleven of thirteen live probes reproduce exchange-api's amount exactly. The two that differ are the better routes. The response shape is exchange-api's, unchanged, down to the empty route that a missing quote returns as a 200 — the swap form reads that as "no price" and retries a 404. Co-authored-by: Hanzo Dev <[email protected]>