How does x402 batched-settlement latency on Arc testnet work in practice, and which published material supports the explanation?
9/30/2026, 12:57:53 PM · llm:deepseek:deepseek-v4-flash + heuristic (fallback from llm:mimo:mimo-v2.5) on 1 step
> ⚠ Low confidence — 1 sub-claim remains below the evidence threshold within budget. Treat this as provisional.
On the Arc testnet, x402 batched-settlement latency is measured across thousands of submitBatch calls, with settlements finalizing in roughly 180 milliseconds — a measured median of 178ms and a p95 of 240ms . This sub-second behavior is attributed to Arc's BFT consensus, which delivers sub-second finality, so a Gateway-batched payment confirms in well under a quarter second and is not block-time-bound the way an Ethereum L1 transaction is .
The published material supporting this explanation is the "Arc Settlement Benchmarks" article, "Measuring x402 settlement latency on Arc" . The CoinDesk source does not address x402 batched-settlement latency on Arc testnet; it discusses Tron's role settling USDT stablecoin transfers, so it provides no support for this question.
Evidence ledger — quotes verified before rewards
How does x402 batched-settlement latency work in practice on the Arc testnet?
100%“Across thousands of submitBatch calls on Arc testnet, x402 batched settlements finalize in roughly 180 milliseconds (measured median 178ms, p95 240ms).” [S1] Measuring x402 settlement latency on Arc
“Arc's BFT consensus delivers sub-second finality, so a Gateway-batched payment confirms in well under a quarter second — it is not block-time-bound the way an Ethereum L1 transaction is.” [S1] Measuring x402 settlement latency on Arc
Which published material supports the explanation of x402 batched-settlement latency on the Arc testnet?
0%No reward-qualifying evidence
Cited sources and planned rewards
- 1Measuring x402 settlement latency on ArcArc Settlement Benchmarks100%$0.015 planned
Decision log · 51 steps
Breaking down: "How does x402 batched-settlement latency on Arc testnet work in practice, and which published material supports the explanation?"
Identified 2 research target(s) to investigate; these are not established facts
Deep mode: up to 4 paid/cached reads plus one bounded gap-expansion pass when needed.
Discovered 21 verified source(s)
Recalled 60 past runs on this subject — how these sources performed when they were available.
ERC-8004 reputation loaded — composite scores on this subject.
Claim-aware portfolio selected 2/2 positive proposal(s): 1 cached + 1 fresh, predicting 2/2 claim(s) above the evidence floor with $0.002000/$0.015000 fetch USDC reserved.
Free-preview pre-check maps an actionable source to every sub-claim (2/2); paid reading may proceed within the budget.
Already cached and still relevant (matches x402, batched, settlement, latency, arc); reuse for free instead of paying again. — selected for the claim-aware evidence portfolio (targets claims 1, 2; 0 fetch USDC, 1 attention slot).
Strong topical match on settlement, work, addresses sub-claim 1; worth the 0.002 USDC toll. — selected for the claim-aware evidence portfolio (targets claim 1; $0.002000 fetch USDC, 1 attention slot).
Already cached and still relevant (matches settlement); reuse for free instead of paying again. — the free-preview coverage check could not connect this source to any sub-claim, so no toll is authorized.
Already cached and still relevant (matches x402); reuse for free instead of paying again. — the free-preview coverage check could not connect this source to any sub-claim, so no toll is authorized.
Already cached and still relevant (matches batched, settlement); reuse for free instead of paying again. — cached bytes are free, but this read does not clear the attention gate (EV 0.17, minimum 0.45, with a required claim target).
Weak match (no key terms); not worth 0.003 USDC.
Weak match (no key terms); not worth 0.002 USDC.
Weak match (no key terms); not worth 0.002 USDC.
Already cached and still relevant (matches settlement); reuse for free instead of paying again. — the free-preview coverage check could not connect this source to any sub-claim, so no toll is authorized.
Already cached and still relevant (matches work); reuse for free instead of paying again. — the free-preview coverage check could not connect this source to any sub-claim, so no toll is authorized.
Weak match (no key terms); not worth 0.002 USDC.
Weak match (no key terms); not worth 0.004 USDC.
Weak match (no key terms); not worth 0.003 USDC.
Weak match (only latency); not worth 0.003 USDC.
Weak match (only settlement); not worth 0.004 USDC.
Already cached and still relevant (matches published); reuse for free instead of paying again. — the free-preview coverage check could not connect this source to any sub-claim, so no toll is authorized.
Weak match (no key terms); not worth 0.002 USDC.
Weak match (no key terms); not worth 0.002 USDC.
Weak match (no key terms); not worth 0.002 USDC.
Already cached and still relevant (matches x402, settlement); reuse for free instead of paying again. — cached bytes are free, but this read does not clear the attention gate (EV 0.17, minimum 0.45, with a required claim target).
Already cached and still relevant (matches x402); reuse for free instead of paying again. — the free-preview coverage check could not connect this source to any sub-claim, so no toll is authorized.
Agent spend wallet ready: 0x29028Fe1122E17Fe7863A22701e863FE4DaE1aFB (balance sufficient)
Reused cached Arc Settlement Benchmarks — Measuring x402 settlement latency on Arc (free) — S1
Paying $0.002 toll to read CoinDesk: Bitcoin, Ethereum, Crypto News and Price Data — Crypto Long & Short: Inside the chain settling $150 billion of stablecoins a week…
Paid $0.002 to CoinDesk: Bitcoin, Ethereum, Crypto News and Price Data — Crypto Long & Short: Inside the chain settling $150 billion of stablecoins a week (settled a018fd18-1…) — S2
Sub-claim "How does x402 batched-settlement latency work in practice on…": 100% covered by S1
Sub-claim "Which published material supports the explanation of x402 ba…": 100% covered by S1
S1 directly answers the first sub-claim: it reports measured x402 batched-settlement latency on Arc testnet (median 178ms, p95 240ms, roughly 180ms) and explains the mechanism (Arc BFT consensus sub-second finality, Gateway-batched payment not block-time-bound). S1 also serves as the published material supporting the explanation, being an abstract titled 'Arc Settlement Benchmarks' with a URL. S2 is about Tron stablecoin settlement and is irrelevant. No requested part remains missing.
All sub-claims already well-covered (sufficiency passed with 0 gaps) — skipping re-evaluation to save latency.
Final check — "How does x402 batched-settlement latency work in practice on…": 100% assessed by S1
Final check — "Which published material supports the explanation of x402 ba…": 100% assessed by S1
Final coverage assessment — S1 directly answers the first sub-claim with concrete latency figures and an explanation of why x402 batched settlements on Arc testnet are fast (BFT consensus, Gateway batching, not block-time-bound). S1 also serves as the published material supporting that explanation. S2 is about Tron stablecoin settlement and is irrelevant. No requested part remains missing.
Synthesizing a grounded answer from 2 source(s)…
Relevance review returned; only checked excerpts can retain support, and review cannot raise it.
Verified — S1 supports claim 1 at 100%: “Across thousands of submitBatch calls on Arc testnet, x402 batched settlements finalize in roughly 180 milliseconds (measured median 178ms, …”
Verified — S1 supports claim 1 at 90%: “Arc's BFT consensus delivers sub-second finality, so a Gateway-batched payment confirms in well under a quarter second — it is not block-tim…”
Below reward gate — S1 supports claim 2 at 20%: “Across thousands of submitBatch calls on Arc testnet, x402 batched settlements finalize in roughly 180 milliseconds (measured median 178ms, …”
Rejected 0 invalid evidence span(s) and 1 unsupported citation marker(s); rejected markers cannot receive citation rewards.
Drafted answer citing 1 source(s)
Confidence: Low — 1 sub-claim remains below the evidence threshold.
Arc Settlement Benchmarks contributed 100% → reward $0.015
Settled $0.015 citation reward → Arc Settlement Benchmarks (8e01a969-f…)
Done. Spent $0.017 across 2 confirmed/simulated payment(s) to creators.
Portable research receipt
Take the evidence trail with you
One deterministic JSON bundle binds the answer, visible decisions, exact article versions, claim evidence and a Circle-settlement snapshot under SHA-256. Retain the digest to detect later changes; the self-check is not a publisher or Keryx signature.
Exact receipt still current
1 exact cited article version still match Keryx's current index.
Carries this dispatch’s question as context — never its answer. The next dispatch is read from sources bought for it.