From 0378d0efcb39466d81b783e98144a0b59693b28a Mon Sep 17 00:00:00 2001 From: rob thijssen Date: Wed, 7 Oct 2026 18:01:49 +0300 Subject: [PATCH] fix(web): say the probe's request was refused, not that nothing was quoted The pause context showed 1Click filling two QTC buys (233 and 115 QTC, 14:18 and 14:57 UTC on 2026-10-07) while every probe was refused, from $100 to $100k and against both USDCs. The panel's heading, "Will anyone quote QTC?", and its "no quote" labels claimed more than the probe shows. It now names the request (exact input, no key, paying and receiving inside NEAR Intents, against USDC on NEAR or on Ethereum) and calls an outcome a refusal of that request. It points readers to the 1Click fills in each stretch's context, which show when other requests were filled. CLAUDE.md records the distinction. Refs #45 Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_015tyzzRVjH9AdwGtYwsH5VC --- CLAUDE.md | 9 ++++++++ web/src/components/QuotePanel.tsx | 36 ++++++++++++++++++++----------- 2 files changed, 32 insertions(+), 13 deletions(-) diff --git a/CLAUDE.md b/CLAUDE.md index 5b44368..60bfd32 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -609,6 +609,15 @@ and `quote_probe_raw` is pruned hourly. The page records and does not accuse: inventory existing while no quote was given has benign explanations, and the note says so. +**A refusal is of our request, not proof nobody was quoted.** On 2026-10-07 +1Click filled two QTC buys (233 and 115 QTC, 14:18 and 14:57 UTC, settled by +`solver-ref-2.near` through the hub `51e8f94d…`) while every probe, from $100 +to $100k against both USDCs, was refused. The probe asks one thing: keyless, +dry, both sides inside Intents. A buyer paying from another chain, with another +token, or with a partner key asks something else, and NEAR does not show +which. The panel names the request, says "refused" not "no quote", and lists +1Click fills in each pause's context so the two facts sit side by side. + **A token's symbol is not its identity.** `tron-d28a…omft.near` calls itself `USDT` — it is USDT on Tron — and the issue that started this read the contract name and called it TRON. Anyone can deploy a token called USDC, so a stablecoin diff --git a/web/src/components/QuotePanel.tsx b/web/src/components/QuotePanel.tsx index 0a00818..4471343 100644 --- a/web/src/components/QuotePanel.tsx +++ b/web/src/components/QuotePanel.tsx @@ -64,9 +64,9 @@ function stateOf(p: QuoteProbe): State { const RANK: Record = { withheld: 4, quoted: 3, unquoted: 2, failed: 1, none: 0 } const LEGEND: { state: State; label: string }[] = [ - { state: 'withheld', label: 'no quote, while a solver held enough to fill it' }, + { state: 'withheld', label: 'our request refused, while a solver held enough to fill it' }, { state: 'quoted', label: 'quoted' }, - { state: 'unquoted', label: 'no quote, and no solver held enough' }, + { state: 'unquoted', label: 'our request refused, and no solver held enough' }, { state: 'failed', label: 'the probe got no answer' }, ] @@ -135,11 +135,21 @@ export function QuotePanel({ chain, symbol: chainSymbol }: { chain: string; symb return (
-

Will anyone quote {symbol}?

+

Does 1Click quote {symbol}?

- 1Click, asked every minute, against what could have filled it + one request, asked every minute, against what could have filled it
+

+ The request: an exact-input dry quote with no key, paying and receiving + inside NEAR Intents, {symbol} against USDC on NEAR or on Ethereum. A refusal is a refusal of + this request, not proof nobody was quoted: 1Click filled two {symbol} buys on 7 October, at + 14:18 and 14:57 UTC, while every probe of this request was refused. A buyer paying from + another chain or with another token, or holding a partner key, asks a different question, + and NEAR does not show which. The 1Click fills listed under each stretch are how to tell + when that happens. +

+
{SPANS.map(([h, l]) => (