What does "Measuring x402 settlement latency on Arc" reveal about finality?

Archived dispatch

Lowconfidence— Contains synthetic demo material; its measurements cannot support factual conclusions.

9/16/2026, 1:44:52 AM · llm:deepseek:deepseek-v4-flash (fallback from llm:mimo:mimo-v2.5)

§ IIThe reading1 cited

Lowconfidence— Contains synthetic demo material; its measurements cannot support factual conclusions.deep researchpreview plan 1/1 claimsportfolio 1/3 · evidence 100%

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.

"Measuring x402 settlement latency on Arc" reports that x402 batched settlements on Arc testnet finalize in roughly 180 milliseconds, based on thousands of submitBatch calls (measured median 178ms, p95 240ms) . 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 . The source is an abstract, so it does not provide further implementation details beyond these latency and finality figures.

Evidence ledger — recorded source excerpts

Research targets are unverified topics. Coverage is an estimate of excerpt support, not proof of entailment, factual truth or a complete answer.

Requested topic (unverified): “What does "Measuring x402 settlement latency on Arc" reveal about finality?”
0% estimated
No qualifying excerpt recorded

No inspectable non-demo excerpts are recorded for source inspection.

Research evidence matrix

Compare unverified research targets 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 do not prove entailment, measured accuracy or complete synthesis.

Research target by cited source evidence matrix
Research target (unverified)	Inspection status	[S1] Measuring x402 settlement latency on ArcPublication: Arc Settlement BenchmarksPublished: Not recorded
What does "Measuring x402 settlement latency on Arc" reveal about finality?	Illustrative demo excerpt	Inspect 2 excerpts Across thousands of submitBatch calls on Arc testnet, x402 batched settlements finalize in roughly 180 milliseconds (measured median 178ms, p95 240ms). 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.

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

Spent$0.02

To creators100%

Decisions0 bought · 1 cached · 18 skipped

llm:deepseek:deepseek-v4-flash (fallback from llm:mimo:mimo-v2.5)Arc Testnet · historical

Decision log · 42 steps

§ IThe decision$0.02 settled / $0.04

50%$0.02 under cap

Decompose

Breaking down: "What does "Measuring x402 settlement latency on Arc" reveal about finality?"

Decompose

Identified 1 research target(s) to investigate; these are not established facts

Decompose

Deep mode: up to 4 paid/cached reads plus one bounded gap-expansion pass when needed.

Discover

Discovered 21 verified source(s)

Discover

Recalled 60 past runs on this subject — how these sources performed when they were available.

Discover

ERC-8004 reputation loaded — composite scores on this subject.

Pre-check

Claim-aware portfolio selected 1/3 positive proposal(s): 1 cached + 0 fresh, predicting 1/1 claim(s) above the evidence floor with $0.000000/$0.020000 fetch USDC reserved.

Pre-check

Free-preview pre-check maps an actionable source to every sub-claim (1/1); paid reading may proceed within the budget.

DecideCACHE

Arc Settlement Benchmarks — Measuring x402 settlement latency on Arc$0.003 · EV 95%

Exact title match for the question: lab-measured x402 batched-settlement finality on Arc testnet. Already cached, so reuse is free and directly answers claim 0 on finality/latency. Highest-reputation relevant source (43/100, cited 9/19 runs). — selected for the claim-aware evidence portfolio (targets claim 1; 0 fetch USDC, 1 attention slot).

DecideSKIP

Web Payments Review — How long do x402 payments take to finalize?$0.002 · EV 60%

Cross-protocol overview of end-to-end x402 settlement timing, a useful corroborating angle on finality for claim 0; cached so no toll. Lower priority than the Arc-specific benchmark but non-redundant. — 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.

DecideSKIP

Stablecoin Ledger — Why USDC settles instantly onchain$0.003 · EV 45%

Preview states USDC transfers settle in seconds with finality on most L2s — background on finality semantics relevant to claim 0, and cached so free. Cited 7/14 runs 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.

DecideSKIP

Agent Economy Weekly — x402 turns HTTP 402 into an agent payment rail$0.004 · EV 40%

Explains the x402 payment rail mechanics (HTTP 402 inline agent payment), context for what settlement latency measures; cached and cited 8/14 runs. Peripheral to finality itself. — cached bytes are free, but this read does not clear the attention gate (EV 0.40, minimum 0.45, with a required claim target).

DecideSKIP

Onchain Micropayments Digest — Nanopayments and the $0.000001 floor$0.005 · EV 30%

Batched settlement primitives and gas-efficient floors relate to how x402 batches settle, tangentially informing latency/finality for claim 0; cached so no cost. — cached bytes are free, but this read does not clear the attention gate (EV 0.30, minimum 0.45, with a required claim target).

DecideSKIP

Distributed Systems Notes — Idempotency keys prevent double-spends$0.003 · EV 15%

Idempotency keys for retry safety is about double-spend prevention, not settlement finality or latency; too tangential to claim 0 despite decent past citation rate.

DecideSKIP

Stripe Blog — What Stripe data shows about fraud at AI startups$0.002 · EV 10%

Stripe fraud-at-AI-startups data has no bearing on x402 settlement latency or Arc finality; not worth the toll.

DecideSKIP

Ethereum Foundation Blog — The triage is the product: running AI agents against Ethereum's protocol code$0.002 · EV 10%

AI agents triaging Ethereum protocol code is unrelated to x402 settlement timing or finality on Arc.

DecideSKIP

Cointelegraph.com News — Crypto payments barely register among euro area merchants, ECB finds$0.002 · EV 10%

ECB merchant crypto-acceptance survey says nothing about settlement latency or finality mechanics.

DecideSKIP

Latent.Space — Ontologies Are So Back: Why AI Agents Are Reviving the Semantic Web$0.004 · EV 10%

Ontologies/semantic web for agents is off-topic for x402 settlement finality.

DecideSKIP

Simon Willison's Weblog — Feeling sad about AI$0.003 · EV 5%

Metadata-only, no preview content, and topically unrelated to settlement latency.

DecideSKIP

Hugging Face - Blog — BenchMIRT: What are LLM benchmarks actually measuring?$0.003 · EV 5%

LLM benchmark methodology is unrelated to x402/Arc finality; metadata-only as well.

DecideSKIP

Vitalik Buterin's website — Low-risk defi can be for Ethereum what search was for Google$0.004 · EV 10%

Low-risk DeFi essay touches onchain settlement broadly but not x402 latency or Arc finality; metadata-only, no preview to justify the toll.

DecideSKIP

The Coinbase Blog - Medium — In response to the Wall Street Journal$0.003 · EV 5%

Coinbase response to the WSJ about proprietary trading is irrelevant to settlement finality.

DecideSKIP

Decrypt — Putin Signs Russia's First Crypto Law: Trading Is Legal, Payments Stay Banned$0.002 · EV 5%

Russian crypto law/payments ban has no bearing on x402 settlement latency on Arc.

DecideSKIP

CoinDesk: Bitcoin, Ethereum, Crypto News and Price Data — Crypto Long & Short: Inside the 300-to-1 onchain gap between the dollar and euro$0.002 · EV 10%

Dollar-vs-euro onchain stablecoin gap is macro adoption commentary, not settlement finality timing.

DecideSKIP

Inner Axiom — The Codex — The Journey of the Soul$0.002 · EV 0%

Esoteric soul cosmology is entirely off-topic.

DecideSKIP

Conzit Labs — Cecilia Vega's Allegations: Censorship at CBS News Revealed$0.002 · EV 0%

CBS News censorship allegations are entirely off-topic.

DecideSKIP

Keryx Engineering (first-party) — Recovering a Keryx paid research job$0.002 · EV 10%

First-party Keryx buyer-recovery notes concern payment journaling, not x402 settlement latency or Arc finality; no target support.

Fetch

Agent spend wallet ready: 0x29028Fe1122E17Fe7863A22701e863FE4DaE1aFB (balance sufficient)

Fetch

Reused cached Arc Settlement Benchmarks — Measuring x402 settlement latency on Arc (free) — S1

Re-evaluate

Sub-claim "What does "Measuring x402 settlement latency on Arc" reveal …": 100% covered by S1 — S1 directly answers the question: x402 batched settlements on Arc finalize in roughly 180ms (median 178ms, p95 240ms), and Arc's BFT consensus delivers sub-second finality, so a Gateway-batched payment confirms in well under a quarter second and is not block-time-bound like an Ethereum L1 transaction. This explicitly addresses the finality implications of the latency measurements.

Re-evaluate

The single sub-claim is fully covered by S1, which provides explicit latency figures and the finality conclusion (sub-second BFT finality, not block-time-bound). No remaining budget needs to be spent; the skipped sources are either off-topic or would not add requested detail.

Sufficiency

Final check — "What does "Measuring x402 settlement latency on Arc" reveal …": 100% assessed by S1

Sufficiency

Final coverage assessment — The single sub-claim asks what the source reveals about finality. The supplied abstract directly answers this: x402 batched settlements on Arc finalize in roughly 180 ms (median 178 ms, p95 240 ms), and Arc's BFT consensus delivers sub-second finality, so Gateway-batched payments are not block-time-bound like Ethereum L1. This explicitly addresses finality with concrete latency figures and a consensus-level explanation. No requested part remains missing.

Synthesize

Synthesizing a grounded answer from 1 source(s)…

Evidence

Relevance review returned; only checked excerpts can retain support, and review cannot raise it.

Evidence

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, …”

Evidence

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…”

Synthesize

Drafted answer citing 1 source(s)

Verdict

Confidence: Moderate — 1 evidence-verified source cover every sub-claim, but corroboration or support strength is limited.

Attribute

Arc Settlement Benchmarks contributed 100% → reward $0.02

Settle

Settled $0.02 citation reward → Arc Settlement Benchmarks (6e069479-f…)

Done

Done. Spent $0.02 across 1 confirmed/simulated payment(s) to creators.

Read checkpoints

Read checkpoint evidence is unavailable for this report. Historical, private and unsupported native runs are not reconstructed.

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.

View JSON ↗Download

Recorded purchase outcomes

Did the exact article versions bought for this answer appear in its citations? This view scores retained BUY decisions against payment observations recorded in the same dispatch trace.

Recorded settlement bookkeeping only; Circle and chain settlement have not been independently rechecked here.

This is a partial retained trace sample, not a full payment ledger. An absent matching payment does not prove that no payment occurred; excluded and unconfirmed costs remain unknown.

Recorded network: eip155:5042002
Dispatch recorded at: 2026-09-15T18:44:52.202Z

Frozen testnet archive, captured 2026-10-03T00:26:18.665Z. This is historical testnet evidence, separate from current mainnet activity.

Archive source commit: f9dca8d04f4657abbf0153175feec65728ba6a99
Archive database SHA-256: c5d9c0d2bf01099de526d7510321eabd1b0e3519f2792d40b61e49062d766272

Participant cohort: unknown. No outside-customer usage is inferred.

0 scored exact-version purchases from 0 recorded BUY decisions; 0 BUY decisions unscored. 1 of 1 trace payment observations excluded.

Each unique source + item + content version with positive matching recorded settled access counts once. Duplicate BUYs, missing identities, zero/unconfirmed access and incompatible payment observations cannot create a scored purchase. CACHE and SKIP decisions are outside this sample.

Exact-version citation hit rate: Unmeasured
Recorded access cost of uncited purchases: Unmeasured

Predicted value and observed citations

Bins compare the recorded predicted value with citation occurrence in this one dispatch. Small samples do not validate a probability model.

Value band	Predicted mean (0–1)	Citation rate
0–0.2	Unmeasured	Unmeasured
0.2–0.4	Unmeasured	Unmeasured
0.4–0.6	Unmeasured	Unmeasured
0.6–0.8	Unmeasured	Unmeasured
0.8–1	Unmeasured	Unmeasured

Missed value, cost per supported claim, budget alternatives and counterfactual outcomes are unmeasured. No extra reading or learning was performed.

View outcome JSON Download outcomes

A new follow-up runs on Arc mainnet with today’s sources and budget. Only the historical question supplies context.

Ask a follow-upNew dispatch · creators paid again

Carries this dispatch’s question as context — never its answer. The next dispatch is read from sources bought for it.

From the archive

Related dispatches

Dispatch · Arc testnet historySep 30, 2026

I am reading about x402 batched-settlement latency on Arc testnet. What is the main point, and what does Arc Settlement Benchmarks say about it?

1 source cited0.0150 test USDC recorded creator rewards

Dispatch · Arc testnet historySep 30, 2026

What does Web Payments Review establish about conflicting published estimates of x402 settlement time, and what remains uncertain?

2 sources cited0.0220 test USDC recorded creator rewards

Dispatch · Arc testnet historySep 30, 2026

Which specific claim does Arc Settlement Benchmarks make about Arc finality for small payment confirmation, and what supports that claim?

1 source cited0.0150 test USDC recorded creator rewards

Dispatch · Arc testnet historySep 30, 2026

After reading Arc Settlement Benchmarks on x402 batched-settlement latency on Arc testnet, what follow-up question would help test the claim?

1 source cited0.0150 test USDC recorded creator rewards

Browse the full archive ▸