Archived dispatch

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

Highconfidence2 evidence-verified sources ground every sub-claim, 1 disagreement adjudicated

8/30/2026, 6:57:44 PM · llm:mimo:mimo-v2.5

The dispatch, itemised.

§ IThe decision$0.02 / $0.04
50%$0.02 under cap
Decompose

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

Decompose

Identified 3 sub-claim(s) to support

Decompose

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

Discover

Discovered 20 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 3/7 positive proposal(s): 3 cached + 0 fresh, predicting 3/3 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 (3/3); paid reading may proceed within the budget.

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

Direct match for the question—benchmarks x402 settlement latency on Arc. Already cached, free to reuse. High topical value for finality claims. — selected for the claim-aware evidence portfolio (targets claims 1, 2, 3; 0 fetch USDC, 1 attention slot).

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

Closely related—covers x402 payment finalization timing. Already cached, free. Provides complementary context for settlement finality. — selected for the claim-aware evidence portfolio (targets claims 1, 2, 3; 0 fetch USDC, 1 attention slot).

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

Relevant—x402 as an agent payment rail. Already cached, free. Helps explain x402 context for settlement. — selected for the claim-aware evidence portfolio (targets claims 1, 3; 0 fetch USDC, 1 attention slot).

DecideSKIP
Hugging Face - Blog — Build Low-Latency Multilingual Voice Agents: Open Weights & Full Deployment Control with NVIDIA Magpie TTS$0.003 · EV 0%

Unrelated—about multilingual voice agents, not x402 settlement. No topical value.

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

Unrelated—esoteric/mystical content, not technical settlement or x402. No value.

DecideSKIP
Conzit Labs — Enhancing Mobile APIs: Adaptive Payloads for Network Efficiency$0.002 · EV 0%

Unrelated—API payload optimization, not settlement or x402. No value.

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

Relevant to settlement finality—USDC instant settlement on L2s. Already cached, free. Provides baseline for comparison. — 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
Onchain Micropayments Digest — Nanopayments and the $0.000001 floor$0.005 · EV 50%

Partially relevant—micropayments and settlement primitives. Already cached, free. May inform efficiency aspects. — 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
Distributed Systems Notes — Idempotency keys prevent double-spends$0.003 · EV 55%

Relevant to finality—idempotency keys prevent double-spends. Already cached, free. Useful for irreversibility concept. — 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
Garden & Soil Monthly — Building a no-dig raised bed$0.002 · EV 0%

Unrelated—gardening content, not settlement or x402. No value.

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

Unrelated—retro game hardware, not settlement or x402. No value.

DecideSKIP
Stripe Blog — What Link data tells us about AI spending$0.002 · EV 40%

Tangentially relevant—AI spending data, but not direct x402 settlement. Already cached, free. Low priority for this question. — the free-preview coverage check could not connect this source to any sub-claim, so no toll is authorized.

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

Tangentially relevant—AI agents on Ethereum protocol, not x402/Arc. Already cached, free. Minimal direct value. — the free-preview coverage check could not connect this source to any sub-claim, so no toll is authorized.

DecideSKIP
Cointelegraph.com News — Binance to restrict transactions involving HTX, 10 other crypto platforms$0.002 · EV 10%

Low relevance—crypto news about Binance restrictions, not x402 settlement. Not cached, low value.

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

Low relevance—AI ontologies, not settlement. Already cached, free. No direct value. — the free-preview coverage check could not connect this source to any sub-claim, so no toll is authorized.

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

Unrelated—AI model user adoption, not settlement or x402. No value.

DecideSKIP
Vitalik Buterin's website — A shallow dive into formal verification$0.004 · EV 15%

Low relevance—formal verification, not x402 settlement. Not cached, low value.

DecideSKIP
The Coinbase Blog - Medium — Real-time reconciliation with Overseer$0.003 · EV 45%

Relevant—Coinbase reconciliation and settlement systems. Already cached, free. Provides enterprise settlement insights. — 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
Decrypt — Kalshi Adds Real-Time Market Data Feed Through DoubleZero$0.002 · EV 10%

Low relevance—market data feed, not x402 settlement. Not cached, low value.

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 30%

Tangentially relevant—crypto rally and stablecoin payments, not x402 settlement. Already cached, free. Minimal direct value. — the free-preview coverage check could not connect this source to any sub-claim, so no toll is authorized.

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

Fetch

Reused cached Agent Economy Weekly — x402 turns HTTP 402 into an agent payment rail (free) — S3

Re-evaluate

Sub-claim "The research measures the time required for settlement final…": 100% covered by S1 — S1 directly states that across thousands of submitBatch calls on Arc testnet, x402 batched settlements finalize in roughly 180 milliseconds (median 178ms, p95 240ms), providing explicit measurement of settlement finality time.

Re-evaluate

Sub-claim "The findings indicate how quickly transactions achieve irrev…": 80% covered by S1, S2 — S1 provides the Arc finality time (~180ms) and compares it to Ethereum L1 by noting it is not block-time-bound. S2 offers a contrasting perspective (15 seconds for x402 payments, similar to Ethereum L1), but this is a different context and does not directly compare Arc to other systems. However, the direct comparison to Ethereum L1 is covered.

Re-evaluate

Sub-claim "The data provides insights into the performance efficiency a…": 70% covered by S1 — S1 indicates high performance (sub-second finality) and efficiency via batching, but explicit scalability insights (e.g., throughput under load) are not detailed. Coverage is partial but adequate given the data provided.

Re-evaluate

Coverage is adequate for all claims (minimum 0.7). The key measurements and comparisons are covered in the gathered sources. No skipped sources appear directly relevant to filling gaps in the specific claims about Arc's settlement finality, performance, or comparisons. Budget remains unused as no critical need is identified.

Sufficiency

Final check — "The research measures the time required for settlement final…": 100% assessed by S1

Sufficiency

Final check — "The findings indicate how quickly transactions achieve irrev…": 90% assessed by S1, S2

Sufficiency

Final check — "The data provides insights into the performance efficiency a…": 80% assessed by S1

Sufficiency

Final coverage assessment — The gathered sources provide direct measurement data and comparative context for x402 settlement latency on Arc, covering all three sub-claims.

Synthesize

Synthesizing a grounded answer from 3 source(s)…

Adjudicate

⚖️ Sources disagreed on Settlement time for x402 payments on Arc vs. Ethereum L1 — S1 Arc settlements finalize in ~180ms, not block-time-bound. vs S2 x402 payments take ~15 seconds, similar to Ethereum L1 block time. → trusted S1 (S1 is a primary source directly measuring Arc's performance, while S2 is a review article making a general claim about x402 payments without specifying Arc. S1's specific data on Arc's testnet and BFT consensus provides more precise, context-specific information.)

Evidence

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

Evidence

Verified — S1 supports claim 2 at 100%: “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 — S2 supports claim 2 at 100%: “an x402 payment takes about 15 seconds to settle, similar to an Ethereum L1 block time, because each payment is its own transaction waiting …”

Evidence

Verified — S1 supports claim 3 at 100%: “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 2 source(s)

Verdict

Confidence: High — 2 evidence-verified sources ground every sub-claim, 1 disagreement adjudicated.

Attribute

Arc Settlement Benchmarks contributed 85% → reward $0.017

Attribute

Web Payments Review contributed 15% → reward $0.003

Settle

Settled $0.017 citation reward → Arc Settlement Benchmarks (e782ba40-3…)

Settle

Settled $0.003 citation reward → Web Payments Review (07f56340-b…)

Done

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

§ IIIThe settlementweighted · USDC on Arc
85%
15%
1

Arc Settlement Benchmarks

batched

85%$0.017
2

Web Payments Review

batched

15%$0.003
§ IIThe reading2 cited
Highconfidence2 evidence-verified sources ground every sub-claim, 1 disagreement adjudicateddeep researchpreview plan 3/3 claimsportfolio 3/7 · evidence 67%

The research "Measuring x402 settlement latency on Arc" reveals that x402 settlements on Arc achieve finality in approximately 180 milliseconds (median 178ms, p95 240ms), demonstrating sub-second finality due to Arc's BFT consensus . This indicates that transactions become irreversible in well under a quarter second, unlike Ethereum L1 transactions which are block-time-bound and take about 15 seconds to settle . The data highlights Arc's performance efficiency for settlement operations, enabling rapid confirmation of Gateway-batched payments without being limited by block times .

Evidence ledger — quotes verified before rewards

  1. The research measures the time required for settlement finality in the x402 protocol on the Arc network.

    100%
    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
  2. The findings indicate how quickly transactions achieve irreversibility on Arc compared to other systems or benchmarks.

    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-time-bound the way an Ethereum L1 transaction is. [S1] Measuring x402 settlement latency on Arc
    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?
  3. The data provides insights into the performance efficiency and scalability of Arc for settlement operations.

    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-time-bound the way an Ethereum L1 transaction is. [S1] Measuring x402 settlement latency on Arc

Footnotes — each one pays its author

Helpful?
Spent$0.02
To creators100%
Decisions0 bought · 3 cached · 17 skipped
llm:mimo:mimo-v2.5

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.

Inspect machine-readable audit

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