Archived dispatch

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

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

· llm:mimo:mimo-v2.5

§ IIThe reading1 cited
Lowconfidence— Contains synthetic demo material; its measurements cannot support factual conclusions.deep researchpreview plan 2/2 claimsportfolio 2/3 · evidence 50%

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 from "Measuring x402 settlement latency on Arc" reveals that Arc's BFT consensus delivers sub-second finality, meaning a Gateway-batched payment confirms in well under a quarter second and is not block-time-bound like an Ethereum L1 transaction. Specifically, x402 batched settlements finalize in roughly 180 milliseconds (median 178ms, p95 240ms).

However, another source conflicts, stating 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.

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

  2. Requested topic (unverified): “What is x402 settlement latency in the context of Arc?”

    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 1 excerpt
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.
What is x402 settlement latency in the context of Arc?Illustrative demo excerpt
Inspect 1 excerpt
Across thousands of submitBatch calls on Arc testnet, x402 batched settlements finalize in roughly 180 milliseconds (measured median 178ms, p95 240ms).

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 · 2 cached · 17 skipped
llm:mimo:mimo-v2.5Arc Testnet · historical
Decision log · 48 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 2 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 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.

Pre-check

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

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

The article title and preview directly match the research question about 'Measuring x402 settlement latency on Arc' and finality, making it a precise, high-value source. It is cached, so reuse is free. This source has a strong historical reputation (56% citation rate on this subject) and the preview explicitly mentions benchmark methodology and finality, providing direct evidence for both subClaims 0 and 1. — selected for the claim-aware evidence portfolio (targets claims 1, 2; 0 fetch USDC, 1 attention slot).

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

The preview 'How long do x402 payments take to finalize?' directly addresses settlement latency (subClaim 1) and finality (subClaim 0). It is cached and provides a complementary, general overview of x402 timing, which can help contextualize the Arc-specific benchmark. At only $0.002, it's a cheap, relevant source. — selected for the claim-aware evidence portfolio (targets claims 1, 2; 0 fetch USDC, 1 attention slot).

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

The preview discusses USDC settling 'in seconds with finality on most L2s,' which touches on finality (subClaim 0) but is not specific to x402 or Arc settlement. It's about USDC in general. Given the presence of more targeted sources, this adds minimal unique value for the specific question and would be redundant.

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

The preview explains x402 as a payment rail but provides no information about settlement latency, Arc, or finality. It is descriptive of the protocol's purpose, not its performance metrics. Therefore, it does not support either subClaim.

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

This is a 2022 Coinbase blog post responding to a WSJ article about trading. The preview has no relevance to x402 settlement latency, Arc, or finality. It is an unrelated, off-topic source.

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

As first-party Keryx engineering notes, this source is highly authoritative on the internal mechanics of x402 and paid research jobs. The preview on 'buyer recovery' is not directly about latency, but the full text (3071 bytes) likely contains technical details on how x402 transactions are processed and settled, which could provide context for finality (subClaim 0) and latency (subClaim 1). Being cached, it's worth a free read for potential background. — 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
Cointelegraph.com News — Crypto payments barely register among euro area merchants, ECB finds$0.002 · EV 10%

The preview is about ECB findings on crypto payment adoption in the euro area. It is completely unrelated to the technical question of x402 settlement latency and finality on Arc.

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

The article is about AI agents and ontologies. While interesting for agent topics, the preview contains no information relevant to payment settlement latency, Arc, or finality. It does not support the subClaims.

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

Idempotency keys are a general distributed systems concept that could be tangentially related to ensuring correct finality (preventing double-spends), but the preview does not discuss latency, x402, or Arc. The connection is too indirect and abstract for the specific question asked, especially when more directly relevant sources are available.

DecideSKIP
CoinDesk: Bitcoin, Ethereum, Crypto News and Price Data — Bitcoin and Ether bears get decimated amid 'squeeze-led' rally and Musk's X wants to pay creators in stablecoins: Crypto week in 5 stories$0.002 · EV 20%

This is a general crypto news summary. The preview mentions stablecoins and 'squeeze-led' rallies but does not address x402 settlement latency or finality on Arc. It is not a technical source for this question.

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

The article is about Russian crypto regulation (trading legal, payments banned). It is entirely irrelevant to the technical measurement of x402 settlement latency.

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

This is a Vitalik Buterin blog post about low-risk DeFi and Ethereum. While related to onchain settlement broadly, the preview does not mention x402, Arc, or settlement latency benchmarks. It is not a direct match for the specific question.

DecideSKIP
Simon Willison's Weblog — Anthropic’s best AI model struggles to attract users as cheaper tools thrive$0.003 · EV 10%

This is a metadata-only preview about an Anthropic AI model's user adoption. It has no connection to the topic of x402 settlement latency or finality.

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

This is a metadata-only preview about LLM benchmarks. It is unrelated to payment settlement latency, x402, or Arc.

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

This is an Ethereum Foundation post about AI agents running against protocol code. While related to Ethereum and AI, the preview does not discuss x402, settlement latency, or finality benchmarks. It is not relevant to the question.

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

The preview discusses nanopayment floors and batching, which is related to settlement efficiency but not specifically to measuring latency or finality on Arc for x402. It is a more general micropayments piece, and more targeted sources are available.

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

This is about retro game hardware repair. It has zero relevance to the research question.

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

This is about esoteric spirituality. It has zero relevance to the research question.

DecideSKIP
Conzit Labs — Revolutionizing Context Engineering for Claude 5 Models$0.002 · EV 0%

This is about context engineering for Claude models. It is unrelated to x402 settlement latency.

Fetch

Agent spend wallet ready: 0x29028Fe1122E17Fe7863A22701e863FE4DaE1aFB (balance sufficient)

Fetch

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

Fetch

Reused cached Web Payments Review — How long do x402 payments take to finalize? (free) — S2

Re-evaluate

Sub-claim "What does 'Measuring x402 settlement latency on Arc' reveal …": 100% covered by S1 — Source S1 directly reports that across thousands of submitBatch calls on Arc testnet, x402 batched settlements finalize in roughly 180 milliseconds (median 178ms, p95 240ms), and that 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. This fully answers the question about what the measurement reveals regarding finality.

Re-evaluate

Sub-claim "What is x402 settlement latency in the context of Arc?": 100% covered by S1 — Source S1 explicitly defines x402 settlement latency on Arc as the time for batched settlements to finalize, reporting median 178ms and p95 240ms on testnet, and contrasts it with Ethereum L1 block time. This directly answers the sub-claim.

Re-evaluate

Coverage for both claims is complete based on the supplied passages from S1. No additional sources are needed.

Sufficiency

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

Sufficiency

Final check — "What is x402 settlement latency in the context of Arc?": 100% assessed by S1

Sufficiency

Final coverage assessment — The first claim asks what the specific source 'Measuring x402 settlement latency on Arc' reveals about finality. The source S1 directly provides the answer: x402 batched settlements finalize in roughly 180ms (median 178ms, p95 240ms) due to Arc's BFT consensus delivering sub-second finality, and it explicitly states it is not block-time-bound. The second claim asks for the definition of x402 settlement latency in the context of Arc. The same source S1 defines this as the time for batched settlements to finalize, giving the specific latency numbers. However, a competing source S2 provides a different perspective (15 seconds, Ethereum L1-like), but the question asks specifically about what the 'Measuring x402...' source reveals. Therefore, for both claims, the supplied passages from S1 provide direct, explicit answers covering the requested scope.

Synthesize

Synthesizing a grounded answer from 2 source(s)…

Evidence

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

Adjudicate

⚖️ Sources disagreed on The settlement time for x402 payments on Arc. — S1 Sub-second finality (roughly 180ms). vs S2 About 15 seconds, similar to Ethereum L1 block time. → trusted S1 (The question specifically asks about what the article 'Measuring x402 settlement latency on Arc' reveals, and S1 is the direct source for that content. S2 appears to describe a general or different context (each payment as its own transaction).)

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

Evidence

Verified — S1 supports claim 2 at 90%: “Across thousands of submitBatch calls on Arc testnet, x402 batched settlements finalize in roughly 180 milliseconds (measured median 178ms, …”

Evidence

Below reward gate — S2 supports claim 2 at 0%: “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…”

Evidence

Rejected 0 invalid evidence span(s) and 1 unsupported citation marker(s); rejected markers cannot receive citation rewards.

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, 1 disagreement adjudicated.

Attribute

Arc Settlement Benchmarks contributed 100% → reward $0.02

Settle

Settled $0.02 citation reward → Arc Settlement Benchmarks (d3abcff0-0…)

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.

Manage question privacy

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-09T10:25:22.819Z
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