Archived dispatch

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

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

9/17/2026, 7:28:44 AM · llm:mimo:mimo-v2.5 + llm:deepseek:deepseek-v4-flash on 3 steps

§ IIThe reading1 cited
Lowconfidence— Contains synthetic demo material; its measurements cannot support factual conclusions.deep researchpreview plan 1/1 claimsportfolio 1/2 · 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.

The article "Measuring x402 settlement latency on Arc" reveals that x402 batched settlements on Arc finalize in roughly 180 milliseconds, with a measured median of 178ms and a 95th percentile of 240ms . Additionally, Arc's BFT consensus delivers sub-second finality, allowing Gateway-batched payments to confirm in well under a quarter second, and this finality is not block-time-bound like an Ethereum L1 transaction .

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.

  1. 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

Spent$0.02
To creators100%
Decisions0 bought · 1 cached · 20 skipped
llm:mimo:mimo-v2.5 + llm:deepseek:deepseek-v4-flash on 3 stepsArc Testnet · historical
Decision log · 44 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/2 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%

Directly on-topic: lab-measured x402 batched-settlement finality/latency on Arc testnet, exactly the question asked. Already cached, so reuse free. Past performance 45% citation rate but high relevance; the abstract confirms methodology and results exist. — 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 50%

Addresses x402 end-to-end settlement timing/finality, a secondary angle on the same question. Cached and cheap, but lower reputation (4/100) and only an overview, so useful as corroboration rather than primary evidence. — 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 40%

Covers USDC onchain settlement finality in seconds on L2s, relevant background for how finality works on Arc-like rails. Cached, but abstract is generic and not Arc/x402-specific. — 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
Agent Economy Weekly — x402 turns HTTP 402 into an agent payment rail$0.004 · EV 35%

Explains the x402 payment rail mechanics (HTTP 402 inline agent payment), useful context for interpreting settlement latency, though it does not itself measure Arc finality. Cached. — cached bytes are free, but this read does not clear the attention gate (EV 0.35, 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 relate to x402/Gateway batching on Arc, tangential support for latency discussion. Cached, no extra 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 10%

Idempotency keys for retries is about double-spend safety, not settlement latency or finality on Arc. Not worth reading for this question.

DecideSKIP
Garden & Soil Monthly — Building a no-dig raised bed$0.002 · EV 2%

Gardening content, wholly unrelated to x402 settlement latency or finality.

DecideSKIP
Retro Game Hardware — Recapping a 1990s console$0.002 · EV 2%

Retro console recapping, irrelevant to the settlement/finality question despite past citation stats.

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

Stripe fraud data at AI startups is about fraud rates, not x402 settlement latency or Arc finality. Not cached and not on-topic.

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; no bearing on x402 settlement latency or Arc finality.

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

ECB survey on crypto merchant acceptance; adoption stat, not settlement latency or finality.

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

Ontologies/semantic web for agents; no connection to x402 settlement timing or Arc finality.

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

Metadata-only AI opinion piece, no preview content and off-topic for settlement latency.

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

LLM benchmark methodology, metadata-only and unrelated to x402/Arc finality.

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

Vitalik on low-risk DeFi; metadata-only and not about x402 settlement latency or Arc finality.

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

Coinbase response to WSJ about proprietary trading; no relevance to settlement latency or finality.

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

Russia crypto law news; unrelated to x402 settlement latency or Arc finality.

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/euro onchain gap analysis; about stablecoin composition, not settlement latency or finality.

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

Esoteric soul cosmology; entirely unrelated.

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

CBS News censorship allegations; entirely unrelated.

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

First-party Keryx engineering note on buyer recovery/citation rewards; about the research job mechanics, not x402 settlement latency or Arc finality.

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: it reports x402 batched settlements on Arc testnet finalize in roughly 180ms (median 178ms, p95 240ms), states Arc's BFT consensus delivers sub-second finality, and notes a Gateway-batched payment confirms 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 measurement.

Re-evaluate

Coverage is already full (1.0) from S1, which explicitly states the finality findings (sub-second BFT finality, ~180ms median, not block-time-bound). No additional purchases are warranted; remaining budget should be preserved.

Sufficiency

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

Sufficiency

Final coverage assessment — The source passage from marker S1 explicitly states the findings of the article 'Measuring x402 settlement latency on Arc' regarding finality, providing specific latency measurements and characteristics of Arc's consensus, fully addressing the sub-claim.

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 80%: “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 (0438038a-d…)

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.

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-17T00:28:44.022Z
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

No scored purchases; the hit rate is unmeasured.

Recorded access cost of uncited purchases
Unmeasured

Counts only scored purchases. Descriptive access cost, not causal regret or proof that the purchase was useless.

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 bandPurchasesPredicted mean (0–1)Citation rate
0–0.20UnmeasuredUnmeasured
0.2–0.40UnmeasuredUnmeasured
0.4–0.60UnmeasuredUnmeasured
0.6–0.80UnmeasuredUnmeasured
0.8–10UnmeasuredUnmeasured

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

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