Archived dispatch

How long do x402 payments take to finalize?

Lowconfidence2 sub-claims remain below the evidence threshold, 1 disagreement adjudicated

9/7/2026, 9:47:08 AM · llm:mimo:mimo-v2.5

The dispatch, itemised.

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

Breaking down: "How long do x402 payments take to finalize?"

Decompose

Identified 4 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 4/4 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 (4/4); paid reading may proceed within the budget.

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

Highest-reputation source (39/100) with direct benchmark data on x402 settlement latency on Arc. Cached, so free to reuse; perfect fit for the question's sub-claims about finalization time and network conditions. — selected for the claim-aware evidence portfolio (targets claims 1, 2, 3, 4; 0 fetch USDC, 1 attention slot).

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

Second-highest reputation (28/100) with an article titled exactly 'How long do x402 payments take to finalize?'. Cached, so free; directly addresses the question and likely provides complementary timing data. — selected for the claim-aware evidence portfolio (targets claims 1, 3, 4; 0 fetch USDC, 1 attention slot).

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

Reputation 28/100, cached, and covers USDC instant onchain settlement—a core x402 stablecoin rail. Useful for sub-claims about low-latency settlement and blockchain congestion. — selected for the claim-aware evidence portfolio (targets claims 2, 3, 4; 0 fetch USDC, 1 attention slot).

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

Gardening topic—no relevance to x402 payment finalization. Skip despite being cached.

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

Retro gaming hardware—irrelevant to crypto payments. Skip.

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

Idempotency keys are relevant to payment safety but not directly to finalization time. Low reputation on this subject, and not cached. Skip in favor of more direct sources.

DecideSKIP
Stripe Blog — Helping businesses optimize network costs with the Visa Digital Commerce Authentication Program (DCAP)$0.002 · EV 40%

Stripe Blog has reputation 26/100 but this specific article is about Visa DCAP, not x402 finalization. Cached, but likely low direct value. May provide tangential payment optimization info. — 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 10%

Ethereum Foundation Blog has 0/100 reputation on this subject. Article about AI agents in protocol code—not about x402 finalization. Skip.

DecideSKIP
Cointelegraph.com News — Solana cuts blockchain slot time to 350 milliseconds$0.002 · EV 70%

Cointelegraph has reputation 36/100 and this article covers Solana's slot time reduction to 350ms—directly relevant to low-latency settlement and blockchain congestion sub-claims. Cached. — 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 60%

Onchain Micropayments Digest has reputation 9/100, but the article on nanopayment batching is somewhat relevant to settlement efficiency. Cached, so free; may add nuance. — 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 70%

Agent Economy Weekly has reputation 13/100 but this article directly describes x402 as an agent payment rail. Cached; provides context on the protocol's design for low-latency settlement. — 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
Latent.Space — Ontologies Are So Back: Why AI Agents Are Reviving the Semantic Web$0.004 · EV 10%

Latent.Space article on ontologies in AI agents—not about x402 finalization. Cached but irrelevant. Skip.

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

Simon Willison's article on Anthropic models—AI model usage, not crypto payments. Not cached; skip.

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

Hugging Face blog on voice agents—AI/TTS, not x402 payments. Not cached; skip.

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

Vitalik's post on low-risk DeFi—tangential to Ethereum settlement but not x402-specific. Not cached; skip in favor of more direct sources.

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

Coinbase Blog has 0/100 reputation on this subject. Article on reconciliation with Overseer—systems engineering, not x402 finalization. Cached but irrelevant.

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

Decrypt has reputation 34/100, but this article is about Russia's crypto law—regulatory news, not x402 timing. Cached; low direct value but may provide market context. — the free-preview coverage check could not connect this source to any sub-claim, so no toll is authorized.

DecideSKIP
CoinDesk: Bitcoin, Ethereum, Crypto News and Price Data — MUFG to test real-time blockchain settlement for Japanese government bond trades$0.002 · EV 60%

CoinDesk has reputation 16/100. Article on MUFG blockchain settlement for bonds—relevant to on-chain settlement finality and real-world use cases. Cached. — 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
Inner Axiom — The Codex — The Journey of the Soul$0.002 · EV 0%

Esoteric/spiritual content—completely irrelevant to crypto payments. Not cached; skip.

DecideSKIP
Conzit Labs — Architect-Designed Hudson Valley Farmhouse Lists at $3.14M$0.002 · EV 0%

Real estate article—irrelevant. Not cached; skip.

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 Stablecoin Ledger — Why USDC settles instantly onchain (free) — S3

Re-evaluate

Sub-claim "The finalization time of x402 payments depends on network co…": 80% covered by S1, S2 — S1 shows finalization is sub-second on Arc's BFT network, while S2 describes ~15 seconds on Ethereum L1 due to block times. This demonstrates network-dependent variation, though explicit 'depends on network conditions' statement is implied rather than explicit.

Re-evaluate

Sub-claim "X402 payments are designed for low-latency settlement.": 70% covered by S1 — S1 directly shows sub-second finality on Arc, supporting low-latency design. S3 mentions instant settlement for stablecoins but not specifically x402. Lack of explicit design-intent statement reduces coverage.

Re-evaluate

Sub-claim "Typical finalization times range from a few seconds to sever…": 60% covered by S1, S2 — S1 shows ~0.18 seconds, S2 shows ~15 seconds, covering part of the range. However, 'several minutes' not covered; no source mentions delays that long. Coverage moderate due to missing upper range.

Re-evaluate

Sub-claim "Actual finalization duration is influenced by blockchain con…": 50% covered by S2 — S2 implies congestion影响 via block time delays, but doesn't explicitly mention congestion. S1 shows low latency on a non-congested network. Partial coverage.

Re-evaluate

Coverage across claims is adequate (0.5-0.8), and skipped sources are unrelated to x402 payment timing. No affordable sources directly address gaps like 'several minutes' or explicit network-condition dependence. Buying more would not improve coverage materially.

Sufficiency

Final check — "The finalization time of x402 payments depends on network co…": 60% assessed by S1, S2

Sufficiency

Final check — "X402 payments are designed for low-latency settlement.": 80% assessed by S1, S2

Sufficiency

Final check — "Typical finalization times range from a few seconds to sever…": 70% assessed by S1, S2

Sufficiency

Final check — "Actual finalization duration is influenced by blockchain con…": 50% assessed by S1, S2

Sufficiency

Final coverage assessment — The question asks about the finalization time of x402 payments, and the gathered sources provide information about settlement latency on Arc, the nature of x402 as potentially low-latency, and typical timing ranges from different perspectives. The sources collectively address the sub-claims: S1 indicates sub-second finality on Arc, S2 suggests ~15 seconds for Ethereum L1, and S3 discusses instant settlement for USDC. While sources differ on exact timing, they cover the concepts of network dependence, low-latency design, typical ranges, and congestion influence.

Synthesize

Synthesizing a grounded answer from 3 source(s)…

Adjudicate

⚖️ Sources disagreed on Typical finalization time for x402 payments — S1 Sub-second finality (median 178ms) on Arc testnet. vs S2 About 15 seconds, similar to Ethereum L1 block time. → trusted S1 (S1 provides specific, measured benchmark data from a dedicated testnet (Arc), while S2 offers a general estimate based on Ethereum L1 characteristics. S1's data is more specific and recent for the x402 implementation it describes.)

Evidence

Verified — S1 supports claim 2 at 90%: “Arc's BFT consensus delivers sub-second finality, so a Gateway-batched payment confirms in well under a quarter second”

Evidence

Verified — S1 supports claim 3 at 85%: “x402 batched settlements finalize in roughly 180 milliseconds (measured median 178ms, p95 240ms).”

Evidence

Verified — S2 supports claim 3 at 75%: “an x402 payment takes about 15 seconds to settle, similar to an Ethereum L1 block time”

Evidence

Verified — S3 supports claim 3 at 80%: “USDC is a fully-reserved dollar stablecoin that settles peer-to-peer onchain in seconds.”

Synthesize

Drafted answer citing 3 source(s)

Verdict

Confidence: Low — 2 sub-claims remain below the evidence threshold, 1 disagreement adjudicated.

Attribute

Arc Settlement Benchmarks contributed 50% → reward $0.01

Attribute

Web Payments Review contributed 30% → reward $0.006

Attribute

Stablecoin Ledger contributed 20% → reward $0.004

Settle

Settled $0.01 citation reward → Arc Settlement Benchmarks (2308bce9-8…)

Settle

Settled $0.006 citation reward → Web Payments Review (1dce7fc5-5…)

Settle

Settled $0.004 citation reward → Stablecoin Ledger (0a8d3e7b-a…)

Done

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

§ IIIThe settlementweighted · USDC on Arc
50%
30%
20%
1

Arc Settlement Benchmarks

batched

50%$0.01
2

Web Payments Review

batched

30%$0.006
3

Stablecoin Ledger

batched

20%$0.004
§ IIThe reading3 cited
Lowconfidence2 sub-claims remain below the evidence threshold, 1 disagreement adjudicateddeep researchpreview plan 4/4 claimsportfolio 3/7 · evidence 100%

> ⚠ Low confidence — 2 sub-claims remain below the evidence threshold, 1 disagreement adjudicated within budget. Treat this as provisional.

The finalization time for x402 payments can vary significantly depending on the underlying network and implementation. On the Arc testnet, batched settlements finalize in roughly 180 milliseconds, demonstrating sub-second finality . However, other reviews suggest that if implemented on Ethereum L1, settlement may take about 15 seconds, similar to the block time . The concept of instant onchain settlement is highlighted for stablecoins like USDC, which settle peer-to-peer in seconds .

Evidence ledger — quotes verified before rewards

  1. The finalization time of x402 payments depends on network conditions.

    0%

    No reward-qualifying evidence

  2. X402 payments are designed for low-latency settlement.

    80%
    Arc's BFT consensus delivers sub-second finality, so a Gateway-batched payment confirms in well under a quarter second [S1] Measuring x402 settlement latency on Arc
  3. Typical finalization times range from a few seconds to several minutes.

    70%
    x402 batched settlements finalize in roughly 180 milliseconds (measured median 178ms, p95 240ms). [S1] Measuring x402 settlement latency on Arc
    an x402 payment takes about 15 seconds to settle, similar to an Ethereum L1 block time [S2] How long do x402 payments take to finalize?
    USDC is a fully-reserved dollar stablecoin that settles peer-to-peer onchain in seconds. [S3] Why USDC settles instantly onchain
  4. Actual finalization duration is influenced by blockchain congestion.

    0%

    No reward-qualifying evidence

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

3 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