What does "Measuring x402 settlement latency on Arc" reveal about finality?
9/23/2026, 9:00:17 AM · llm:mimo:mimo-v2.5 + llm:deepseek:deepseek-v4-flash on 2 steps
Illustrative demo content: synthetic sources and measurements are not factual research evidence. Source provenance and payment status are separate; inspect the receipt for settled, pending or simulated payments. Settlement does not authenticate a source's claims.
The source "Measuring x402 settlement latency on Arc" reveals that x402 batched settlements on Arc testnet finalize in roughly 180 milliseconds, with a measured median of 178ms and a 95th percentile of 240ms . It characterizes finality in this context as "sub-second finality" delivered by Arc's BFT consensus, meaning a Gateway-batched payment confirms in well under a quarter second and is not block-time-bound like an Ethereum L1 transaction .
Evidence ledger — supporting quotes
What specific findings or data does the source present regarding the latency of x402 settlement on Arc?
0%No supporting evidence
How does the source define or characterize 'finality' in the context of these settlement latency measurements?
0%No supporting evidence
Research evidence matrix
Compare research claims with cited sources and inspect recorded excerpts. An empty cell means no inspectable excerpt was recorded; it does not establish whether a claim is true, false, or disputed. Coverage and agent confidence are not measured accuracy.
| Research claim | Inspection status | [S1] Measuring x402 settlement latency on ArcPublication: Arc Settlement BenchmarksPublished: Not recorded |
|---|---|---|
| What specific findings or data does the source present regarding the latency of x402 settlement on Arc? | Illustrative demo excerpt | Inspect 1 excerptAcross thousands of submitBatch calls on Arc testnet, x402 batched settlements finalize in roughly 180 milliseconds (measured median 178ms, p95 240ms). |
| How does the source define or characterize 'finality' in the context of these settlement latency measurements? | Illustrative demo excerpt | Inspect 1 excerptArc'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. |
Reference export
1 article references. Recorded titles, links and dates; observed scholarly records also include supplied authors, DOI and journal metadata with read limits. Review metadata before using in a paper. Import RIS into Zotero with File → Import.
Cited sources and references
- 1Measuring x402 settlement latency on ArcArc Settlement BenchmarksSynthetic demo content ? illustrative only100%$0.02 planned
Decision log · 49 steps
Breaking down: "What does "Measuring x402 settlement latency on Arc" reveal about finality?"
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/4 positive proposal(s): 1 cached + 1 fresh, predicting 2/2 claim(s) above the evidence floor with $0.002000/$0.020000 fetch USDC reserved.
Free-preview pre-check maps an actionable source to every sub-claim (2/2); paid reading may proceed within the budget.
Title and preview directly match the question: 'Measuring x402 settlement latency on Arc' and mentions 'finality'. It's cached, so it's free to reuse. This source is the most targeted and is likely to answer both subClaims. — selected for the claim-aware evidence portfolio (targets claims 1, 2; 0 fetch USDC, 1 attention slot).
Preview asks 'How long do x402 payments take to finalize?' and is described as an 'overview of end-to-end settlement timing.' This directly relates to the finality aspect of the question and provides broader context. It's cheap at $0.002. — selected for the claim-aware evidence portfolio (targets claims 1, 2; $0.002000 fetch USDC, 1 attention slot).
Preview discusses x402 as a payment rail. While it doesn't directly measure latency, it's foundational context for the x402 standard being measured. It's cached and has high past citation rates (55%) on this subject. — the claim-aware portfolio chose a stronger, less redundant set inside the 4-source attention and $0.020000 fetch-budget caps, so this proposal stays unspent.
Preview mentions USDC settles with finality on L2s, which is related context for settlement finality. It's cached, but only tangential to the specific x402/Arc latency measurement. Low risk to reuse. — the claim-aware portfolio chose a stronger, less redundant set inside the 4-source attention and $0.020000 fetch-budget caps, so this proposal stays unspent.
Preview is about idempotency keys, which is a general distributed systems concept, not directly about x402 settlement latency or finality measurements on Arc. Not worth the read for this specific question.
Preview is about AI open source project management, not settlement latency or x402. No connection to the question despite the AI agent tag.
Preview is about AI agents testing Ethereum protocol code. While related to Ethereum/AI, it doesn't address x402 settlement latency or Arc-specific benchmarks.
Preview is metadata only with title 'Feeling sad about AI'. No content preview, not on the right chain (external), and no relevance to settlement latency.
Metadata only preview about LLM benchmarks. No relevance to x402, settlement, or latency. Not on the right chain (external).
Metadata only preview about low-risk DeFi. While onchain settlement is tangentially related, the preview doesn't indicate any content on x402 latency or Arc benchmarks. Not on the right chain (external).
Preview is about Keryx's own buyer recovery process, not about measuring x402 settlement latency. First-party source but not relevant to this specific research question.
Preview is about fraud at AI startups on Stripe. No connection to x402 settlement latency or Arc benchmarks despite the payments tag.
Preview is about recapping vintage game consoles. Completely unrelated to settlement latency, despite high past reputation on this subject (likely from different questions).
Preview is about building raised garden beds. Completely unrelated to settlement latency, despite high past reputation on this subject.
Preview is Coinbase's response to a WSJ article about proprietary trading. No relevance to x402 settlement latency or Arc benchmarks despite stablecoin tags.
Preview is about Russia's crypto law regarding trading vs payments. No connection to x402 settlement latency or Arc benchmarks.
Preview discusses onchain gap between dollar and euro stablecoins. While related to onchain settlement, it doesn't address x402 latency measurements on Arc. Moderate past citation rate (40%).
Preview is about esoteric teachings of the planet Isis. Completely unrelated to any payment or settlement topic.
Preview is about Trump's data center pledge. No relevance to x402, settlement, or latency. Not on the right chain (external).
Preview is about a town banning crypto mining and AI data centers. No connection to x402 settlement latency or Arc benchmarks despite crypto/mining tags.
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 Web Payments Review — How long do x402 payments take to finalize?…
Paid $0.002 to Web Payments Review — How long do x402 payments take to finalize? (settled beae22b7-d…) — S2
Sub-claim "What specific findings or data does the source present regar…": 100% covered by S1
Sub-claim "How does the source define or characterize 'finality' in the…": 100% covered by S1
S1 directly answers both sub-claims: it reports latency findings for x402 settlement on Arc (median 178ms, p95 240ms, roughly 180ms) and characterizes finality as sub-second BFT consensus finality that is not block-time-bound. S2 provides a conflicting general x402 timing view but does not address Arc finality, so it is only topical context and not a source of the requested Arc-specific answer.
All sub-claims already well-covered (sufficiency passed with 0 gaps) — skipping re-evaluation to save latency.
Final check — "What specific findings or data does the source present regar…": 100% assessed by S1, S2
Final check — "How does the source define or characterize 'finality' in the…": 100% assessed by S1
Final coverage assessment — S1 directly answers the first sub-claim with specific latency data (median 178ms, p95 240ms, ~180ms) and characterizes finality as sub-second BFT consensus finality, not block-time-bound. S2 offers a conflicting view (~15 seconds, block-time-bound) but does not define finality beyond settlement time. The second sub-claim asks how the source defines or characterizes 'finality' in the context of these measurements; S1 explicitly states 'Arc's BFT consensus delivers sub-second finality' and contrasts it with Ethereum L1 block-time-bound finality, which is a direct characterization. S2 does not define finality. Thus both sub-claims are directly supported by S1, with S2 providing a contrasting latency claim but no finality definition.
Synthesizing a grounded answer from 2 source(s)…
Relevance review returned; only checked excerpts can retain support, and review cannot raise it.
⚖️ Sources disagreed on The settlement time for x402 payments. — S1 Roughly 180 milliseconds (batched settlements on Arc testnet). vs S2 About 15 seconds (individual payments waiting to be mined into a block). → reported preference: S1 (The claim is specifically about measurements on Arc testnet from the source titled "Measuring x402 settlement latency on Arc," which directly answers the question. The other source provides a general reading not specific to Arc.)
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 2 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…”
Drafted answer citing 1 source(s)
Confidence: Moderate — source preferences are explained, but conflicting evidence limits confidence.
Arc Settlement Benchmarks contributed 100% → reward $0.02
Settled $0.02 citation reward → Arc Settlement Benchmarks (9da45754-d…)
Done. Spent $0.022 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.