What does "Measuring x402 settlement latency on Arc" reveal about finality?
9/18/2026, 1:24:10 PM · llm:deepseek:deepseek-v4-flash (fallback from llm:mimo:mimo-v2.5)
The dispatch, itemised.
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/3 positive proposal(s): 2 cached + 0 fresh, predicting 2/2 claim(s) above the evidence floor with $0.000000/$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.
Exact title match for the question: lab-measured x402 batched-settlement finality on Arc testnet. Already cached, so free reuse; directly addresses both what finality means here and the measured latency. Best source for claimIndex 0 and 1. — selected for the claim-aware evidence portfolio (targets claims 1, 2; 0 fetch USDC, 1 attention slot).
Cross-protocol overview of end-to-end x402 settlement timing, useful for defining 'x402 settlement latency' and 'finality' (claimIndex 1) and as a secondary check on claimIndex 0. Cached, so free; lower reputation (6/100) so use only as corroboration. — selected for the claim-aware evidence portfolio (targets claims 1, 2; 0 fetch USDC, 1 attention slot).
Explains the x402 standard (HTTP 402 as an agent payment rail), which grounds the mechanism behind x402 settlement latency and finality (claimIndex 1). Cached and free; strong past citation rate (59%) 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.
States USDC transfers settle in seconds with finality on most L2s — a useful baseline for what finality means in onchain settlement (claimIndex 1), though not Arc- or x402-specific. Cached, so free. — cached bytes are free, but this read does not clear the attention gate (EV 0.35, minimum 0.45, with a required claim target).
Batched settlement primitives are the mechanism x402/Gateway uses on Arc, so it helps explain why latency and finality behave as measured (claimIndex 1). Cached and free; tangential but relevant. — cached bytes are free, but this read does not clear the attention gate (EV 0.30, minimum 0.45, with a required claim target).
Idempotency/retry safety is adjacent to settlement finality semantics (when a payment is truly done), giving context for claimIndex 1. Cached and free, but only loosely on-topic. — cached bytes are free, but this read does not clear the attention gate (EV 0.20, minimum 0.45, with a required claim target).
Stripe fraud-at-AI-startups data has no bearing on x402 settlement latency or finality on Arc; not worth the $0.002 toll.
Ethereum Foundation AI-agent triage post concerns protocol security workflows, not x402 latency or Arc finality.
ECB merchant crypto-acceptance survey is about adoption rates, not settlement latency or finality.
Ontologies/semantic-web piece for AI agents is unrelated to x402 settlement timing or Arc finality.
Metadata-only Simon Willison opinion post with no preview text; cannot support any subclaim and would cost $0.003.
Metadata-only LLM-benchmark post, off-topic and no readable preview.
Metadata-only Vitalik defi essay; no preview text and not about x402 latency or Arc finality.
Coinbase response to the WSJ is a corporate rebuttal, irrelevant to settlement latency/finality measurement.
Russia crypto-law news concerns regulation, not x402 settlement timing or finality.
Dollar-vs-euro onchain gap analysis is about stablecoin composition, not latency or finality.
Esoteric soul-journey article, wholly unrelated to the question.
Claude 5 context-engineering post, unrelated to x402 settlement or Arc finality.
First-party Keryx buyer-recovery notes mention x402 but cover purchase journaling, not settlement latency or finality; low reputation (20/100) and no relevant target.
Agent spend wallet ready: 0x29028Fe1122E17Fe7863A22701e863FE4DaE1aFB (balance sufficient)
Reused cached Arc Settlement Benchmarks — Measuring x402 settlement latency on Arc (free) — S1
Reused cached Web Payments Review — How long do x402 payments take to finalize? (free) — S2
Sub-claim "What does "Measuring x402 settlement latency on Arc" reveal …": 90% covered by S1 — S1 directly reports the measurement result: x402 batched settlements on Arc testnet finalize in roughly 180ms (median 178ms, p95 240ms), and Arc's BFT consensus delivers sub-second finality, so a Gateway-batched payment confirms well under a quarter second and is not block-time-bound like an Ethereum L1 transaction. This explicitly answers what the measurement reveals about finality. Minor gap: no deeper explanation of the finality mechanism beyond 'BFT consensus' and no discussion of how finality is defined or verified in the measurement.
Sub-claim "What is meant by "x402 settlement latency" and "finality" in…": 50% covered by S1, S2 — S1 gives operational context: x402 batched settlements via submitBatch calls, measured median/p95 latency, and finality as sub-second confirmation under Arc's BFT consensus, contrasted with Ethereum L1 block-time-bound settlement. S2 offers a contrasting definitional framing (settlement as waiting to be mined into a block, ~15s). However, neither source explicitly defines the terms 'x402 settlement latency' or 'finality' as such; the meaning must be inferred from usage. Partial answer only.
The primary question is well covered by S1 (0.9). The definitional sub-claim is only partially covered (0.5) because neither source explicitly defines 'x402 settlement latency' or 'finality'; the meaning is inferred from usage. Among affordable skipped sources (budget 0.02), 'Stablecoin Ledger — Why USDC settles instantly onchain' (0.003) is the most relevant, as it addresses onchain settlement and finality concepts that could clarify the definitional gap. Other skipped sources are off-topic (fraud, ECB merchant data, AI agents, crypto law, etc.) and would not help. Only one purchase is recommended to stay frugal; the remaining budget is insufficient to justify buying more marginally relevant items.
Filling gap — buying Stablecoin Ledger — Why USDC settles instantly onchain ($0.003)…
Paid $0.003 to Stablecoin Ledger — Why USDC settles instantly onchain (settled f9c2ef81-a…) — S3
Final check — "What does "Measuring x402 settlement latency on Arc" reveal …": 100% assessed by S1
Final check — "What is meant by "x402 settlement latency" and "finality" in…": 100% assessed by S1
Final coverage assessment — S1 directly answers the main question: it reports measured x402 batched settlement latency on Arc (median 178ms, p95 240ms) and states that Arc's BFT consensus delivers sub-second finality, so Gateway-batched payments confirm in well under a quarter second and are not block-time-bound like Ethereum L1. This also supplies the meaning of 'x402 settlement latency' and 'finality' in context: latency is the measured time for batched settlements to finalize, and finality is sub-second confirmation via BFT consensus. S2 offers a conflicting general view of x402 payments taking ~15 seconds, but it is not about Arc and does not define finality for the Arc measurement. S3 discusses USDC final settlement generally but not x402 on Arc. The requested sub-claims are answered by S1; no requested part remains missing.
Synthesizing a grounded answer from 3 source(s)…
Relevance review returned; only checked excerpts can retain support, and review cannot raise it.
⚖️ Sources disagreed on x402 settlement/finality timing — S1 x402 batched settlements on Arc finalize in roughly 180ms (median 178ms, p95 240ms) with sub-second finality, not block-time-bound like Ethereum L1. vs S2 x402 payments take about 15 seconds to settle, similar to Ethereum L1 block time, because each payment is its own transaction waiting to be mined into a block. → reported preference: S1 (S1 is more specific and internally consistent: it reports measured statistics (median 178ms, p95 240ms across thousands of submitBatch calls) and ties the result to a named consensus mechanism (Arc BFT) and batching (Gateway-batched), whereas S2 is framed as a reading/view and describes a generic per-transaction mining model that does not match the batched Arc context.)
Verified — S1 supports claim 1 at 90%: “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…”
Verified — S1 supports claim 2 at 60%: “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 60%: “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…”
Verified — S2 supports claim 2 at 40%: “In our reading, an x402 payment takes about 15 seconds to settle, similar to an Ethereum L1 block time, because each payment is its own tran…”
Below reward gate — S3 supports claim 2 at 20%: “USDC is a fully-reserved dollar stablecoin that settles peer-to-peer onchain in seconds.”
Rejected 0 invalid evidence span(s) and 1 unsupported citation marker(s); rejected markers cannot receive citation rewards.
Drafted answer citing 2 source(s)
Confidence: Moderate — source preferences are explained, but conflicting evidence limits confidence.
Arc Settlement Benchmarks contributed 85% → reward $0.017
Web Payments Review contributed 15% → reward $0.003
Settled $0.017 citation reward → Arc Settlement Benchmarks (6ab3a6b7-d…)
Settled $0.003 citation reward → Web Payments Review (bcc87de0-0…)
Done. Spent $0.023 across 3 confirmed/simulated payment(s) to creators.
Arc Settlement Benchmarks
batched
Web Payments Review
batched
"Measuring x402 settlement latency on Arc" reports that x402 batched settlements on Arc testnet finalize in roughly 180 milliseconds, with a measured median of 178ms and p95 of 240ms across thousands of submitBatch calls . This is attributed to Arc's BFT consensus delivering 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 .
On the meaning of the terms: the source does not provide an explicit definition of "x402 settlement latency" or "finality." From the passage, settlement latency is characterized operationally as the time for x402 batched settlements to finalize (reported as ~180ms median 178ms, p95 240ms) , and finality is characterized as the confirmation property delivered by Arc's BFT consensus (sub-second finality, confirming in well under a quarter second) . No further definitional detail is supplied in the provided passages, so any fuller definition of these terms is a gap in the sources.
Note on disagreement: S2 states that an x402 payment takes about 15 seconds to settle, similar to an Ethereum L1 block time, because each payment is its own transaction waiting to be mined into a block . This conflicts with S1's account of ~180ms finality for batched settlements on Arc . S3 discusses USDC settling onchain in seconds and final settlement for machine-to-machine commerce, but does not address x402 or Arc specifically, so it does not resolve the conflict.
Evidence ledger — quotes verified before rewards
What does "Measuring x402 settlement latency on Arc" reveal about finality?
90%“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
What is meant by "x402 settlement latency" and "finality" in the context of "Measuring x402 settlement latency on Arc"?
60%“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
“In our reading, an x402 payment takes about 15 seconds to settle, similar to an Ethereum L1 block time, because each payment is its own transaction waiting to be mined into a block.” [S2] How long do x402 payments take to finalize?
Footnotes — each one pays its author
- 1Measuring x402 settlement latency on ArcArc Settlement Benchmarks85%+$0.017
- 2How long do x402 payments take to finalize?Web Payments Review15%+$0.003
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
2 exact cited article versions 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.