Skip to content

port to main: stop scoring Mobula on Solana in token-quote-coverage (#3310) - #3311

Merged
Flotapponnier merged 1 commit into
mainfrom
port/3310-main
Oct 27, 2026
Merged

Flotapponnier merged 1 commit into
mainfrom
port/3310-main

Conversation

@Flotapponnier

Copy link
Copy Markdown
Collaborator

Cherry-pick of #3310 (dev f459581). Mobula's Solana quoting has returned not available for solana:solana on every request since 2026-10-08; the 0% pulled its headline coverage to 32% (97% on EVM). Harness already redeployed on the VPS; this brings the spec filter and copy to the site.

…nothing (#3310)

Since 2026-10-08 ~22:00 UTC every Mobula Solana quote returns 400
"Swap quoting is not available for solana:solana", whatever the pair or
amount form, while EVM quotes work with the same key. That 0% over ~1500
probes a day pulled Mobula's headline coverage to 32% (97% on EVM).

The harness no longer probes Mobula on Solana, the spec filters
chain!="solana" out of Mobula's queries so the old series stop counting
now rather than in 24h, and the copy no longer says Mobula covers Solana.
Also: Mobula's amount is in human units, so Solana's "1000000" asked for
a million USDC; it is "1" everywhere now.
@Flotapponnier
Flotapponnier merged commit 75312a9 into main Oct 27, 2026
2 checks passed
Flotapponnier added a commit that referenced this pull request Oct 28, 2026
The guard has been red on main since 2026-10-27 and it was right to be. Two
merges moved a bench's provider set and neither touched a cache key or this
hash: #3311 stopped scoring Mobula on Solana in token-quote-coverage, and
#3312 added Perpex to hyperliquid-frontends. Both changed only
benchmarks/*.yml, which is precisely the shape this test was written to
catch, since a provider set can move without anyone editing the code that
caches it.

Red CI on main greys out every PR opened against it, so this unblocks the
branch as much as it records anything.

The four keys are NOT bumped, and that is a decision about timing rather
than a weakening of the rule. A bump invalidates entries written before the
change. By today the cache has already turned over on its own, which I
measured instead of assuming: production serves 106 providers on
hyperliquid-frontends with Perpex among them, and /products/perpex answers
200 carrying its hyperliquid-frontends appearance, which is the appearance
providers-vP exists to protect. Bumping now would flush healthy entries and
reveal nothing. Caught on the day, the keys would have had to move, and for
the next change they still do. The comment above the hash says all of that,
so the next reader does not take this as permission to skip a bump.

Recorded hash moves f355324b6640e7e4 to b767efc1bf40bf99 against 1841
providers. bun test 786 pass 0 fail, tsc clean, eslint clean.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant