How does conflicting published estimates of x402 settlement time work in practice, and which published material supports the explanation?
10/1/2026, 12:30:41 PM · llm:deepseek:deepseek-v4-flash
> ⚠ Low confidence — the final assessment does not establish a complete supported answer for every requested part within budget. Treat this as provisional.
The published estimates conflict: one source reports that x402 batched settlements on Arc finalize in roughly 180 milliseconds, with a measured median of 178ms and p95 of 240ms, and explains this by Arc's BFT consensus delivering sub-second finality so a Gateway-batched payment confirms well under a quarter second and is not block-time-bound like an Ethereum L1 transaction . Another source, by contrast, estimates that an x402 payment takes about 15 seconds to settle, similar to an Ethereum L1 block time, because each payment is treated as its own transaction waiting to be mined into a block, which would leave agent-to-agent micropayments sluggish until block times shrink . In practice, according to the published material, x402 settlement works through batched settlement: many micro-authorizations are signed off-chain and settled together in batches rather than paying gas per transaction. This batching mechanism is consistent with the Arc benchmark explanation that Gateway-batched payments confirm quickly under BFT consensus . The conflict is explained by differing assumptions about whether x402 payments are settled individually as on-chain transactions (the 15-second view) or batched and settled together (the sub-second view) . The sources do not provide a direct reconciliation or a single authoritative measurement that resolves the discrepancy; the Arc benchmark is the more specific and internally consistent measurement, while the 15-second estimate is described as a reading based on an Ethereum L1 analogy . Regarding which published material supports the explanation: the Arc Settlement Benchmarks abstract provides the batched-settlement latency measurement and BFT finality explanation , and the Onchain Micropayments Digest abstract describes the off-chain authorization and batch settlement mechanism. The Stablecoin Ledger source discusses USDC settling onchain in seconds and instant final settlement for machine-to-machine commerce, but it does not specifically address x402 settlement time or the conflicting estimates.
Evidence ledger — supporting quotes
What are the conflicting published estimates of x402 settlement time, and what does each estimate claim?
60%“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
“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 transaction waiting to be mined into a block.” [S2] How long do x402 payments take to finalize?
How does x402 settlement time work in practice, according to published material?
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
Which published material supports the explanation of how x402 settlement time works in practice?
80%“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
What explains the conflict among the published estimates of x402 settlement time?
70%“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 transaction waiting to be mined into a block.” [S2] How long do x402 payments take to finalize?
Cited sources and references
- 1Measuring x402 settlement latency on ArcArc Settlement Benchmarks60%$0.009 planned
- 2How long do x402 payments take to finalize?Web Payments Review40%$0.006 planned
Decision log · 66 steps
Breaking down: "How does conflicting published estimates of x402 settlement time work in practice, and which published material supports the explanation?"
Identified 4 research target(s) to investigate; these are not established facts
Deep mode: up to 4 paid/cached/public reads plus one bounded gap-expansion pass when needed.
Discovered 21 verified creator source(s) and 4 free public reference(s)
Recalled 60 past runs on this subject — how these sources performed when they were available.
ERC-8004 reputation loaded — composite scores on this subject.
Claim-aware portfolio selected 3/3 positive proposal(s): 3 cached + 0 fresh, predicting 4/4 claim(s) above the evidence floor with $0.000000/$0.015000 fetch USDC reserved.
Free-preview pre-check maps an actionable source to every sub-claim (4/4); paid reading may proceed within the budget.
Arc Settlement Benchmarks is the top performer on this subject (56% citation rate, avg weight 0.78, reputation 43/100) and its preview directly promises benchmark methodology and results for x402 batched-settlement finality on Arc — exactly the kind of measured latency figure that would appear among conflicting published estimates and explain how settlement actually works. Already cached, so reuse is free. — selected for the claim-aware evidence portfolio (targets claims 1, 2, 3, 4; 0 fetch USDC, 1 attention slot).
Web Payments Review's article is literally titled 'How long do x402 payments take to finalize?' and previews an overview of end-to-end settlement timing for x402 — directly on the conflicting-estimates question. Lower reputation (14/100) and only 33% citation rate, but it is cached and free to reuse. — selected for the claim-aware evidence portfolio (targets claims 1, 2, 3, 4; 0 fetch USDC, 1 attention slot).
Stablecoin Ledger (reputation 31/100, 40% citation rate) previews that USDC transfers settle in seconds with finality on most L2s — a concrete settlement-time claim that bears on the conflicting-estimates question and the underlying mechanics. Cached, so no cost. — selected for the claim-aware evidence portfolio (targets claims 1, 2, 4; 0 fetch USDC, 1 attention slot).
Agent Economy Weekly (reputation 23/100, 33% citation rate) previews how x402 turns HTTP 402 into an agent payment rail, useful background on the payment flow that settlement timing depends on. Cached and free; weaker fit than the dedicated timing sources. — cached bytes are free, but this read does not clear the attention gate (EV 0.40, minimum 0.45, with a required claim target).
Keryx Engineering is first-party with the highest avg reward ($0.0165) and 32% citation rate, but its preview concerns buyer recovery and payment journaling, not x402 settlement timing. Full text may still touch x402 mechanics; cached so reuse costs nothing. — cached bytes are free, but this read does not clear the attention gate (EV 0.35, minimum 0.45, with a required claim target).
Onchain Micropayments Digest previews batched settlement and the nanopayment floor — related to settlement primitives but says nothing about x402 timing estimates or why published figures conflict. Thin abstract (294 bytes) and only 1 prior citation; not worth prioritizing.
Latent.Space's preview is about ontologies and the semantic web for AI agents, not x402 settlement timing. Its single prior citation on this subject is weak evidence of relevance to the timing conflict.
Coinbase's Overseer post covers real-time reconciliation of distributed state, not x402 settlement latency or published timing estimates. Tangential at best.
Stripe Blog post is about travel/leisure fraud attempts, unrelated to x402 settlement timing. Stripe Blog has never been cited on this subject.
Ethereum Foundation post is about AI agents triaging protocol code, not x402 payment settlement timing. No prior citations on this subject.
Cointelegraph piece covers ECB merchant crypto acceptance rates, not x402 settlement latency. Cointelegraph has been read 7 times on this subject and never cited.
Decrypt article is about FCA/HTX regulatory settlement talks — 'settlement' in a legal sense, irrelevant to x402 payment finality. Never cited on this subject.
CoinDesk tokenization-for-advisors piece is metadata-only with no preview text and no bearing on x402 settlement timing. CoinDesk has never been cited on this subject.
Simon Willison post is metadata-only about Anthropic model adoption, unrelated to x402 settlement timing.
Hugging Face post is metadata-only about NVIDIA speaker diarization, entirely unrelated to x402 settlement.
Vitalik's low-risk DeFi post is metadata-only and about DeFi risk, not x402 settlement timing estimates.
Esoteric astrology article about the Pleiades; no connection to x402 or payment settlement.
Geopolitical casualty-reporting piece; no connection to x402 settlement timing.
Foundational AI-agents writing with no x402 or payment-settlement content; free but irrelevant to the timing conflict. - free public feed reference; no purchase or creator reward.
Cloudflare OS agent platform announcement; no x402 settlement timing content. - free public feed reference; no purchase or creator reward.
2023 LLM-agent survey; predates x402 and does not address payment settlement timing. - free public feed reference; no purchase or creator reward.
NASA engineering-excellence essay; no relevance to x402 settlement timing. - free public feed reference; no purchase or creator reward.
Agent spend wallet ready: 0x29028Fe1122E17Fe7863A22701e863FE4DaE1aFB (balance sufficient)
Reused cached Arc Settlement Benchmarks — Measuring x402 settlement latency on Arc (free) — S1
Reused cached Web Payments Review — How long do x402 payments take to finalize? (free) — S2
Reused cached Stablecoin Ledger — Why USDC settles instantly onchain (free) — S3
Sub-claim "What are the conflicting published estimates of x402 settlem…": 100% covered by S1, S2 — S1 gives a sub-second estimate (~180ms median, p95 240ms, sub-second finality) and S2 gives a ~15 second estimate similar to Ethereum L1 block time. Both conflicting estimates and their claims are explicitly stated.
Sub-claim "How does x402 settlement time work in practice, according to…": 60% covered by S1, S2 — S1 explains the practical mechanism on Arc: batched settlements via submitBatch calls, BFT consensus delivering sub-second finality, not block-time-bound. S2 offers a competing mechanism (each payment its own transaction waiting to be mined). However, the material does not reconcile which mechanism actually governs x402 in practice, so the practical answer is partial.
Sub-claim "Which published material supports the explanation of how x40…": 70% covered by S1, S2 — S1 (Arc Settlement Benchmarks) and S2 (Web Payments Review) are explicitly identified as the supporting published material for the two explanations. S3 is only tangential. The specific material is named, though it is limited to two abstracts.
Sub-claim "What explains the conflict among the published estimates of …": 30% covered by S1, S2 — The passages imply the conflict stems from different settlement architectures (Arc Gateway-batched BFT finality vs. Ethereum L1 per-transaction mining), but no source explicitly states or analyzes the cause of the discrepancy. Only topical context is provided.
The conflict-explanation claim is below 0.5 and the practical mechanism is only partially covered. The Onchain Micropayments Digest item on batched settlement ($0.005) directly addresses the batching mechanism that likely explains the latency discrepancy, and the Agent Economy Weekly x402 rail item ($0.004) covers the x402 standard's payment flow. Both fit the remaining $0.015 budget ($0.009 total). Other skipped sources are off-topic (fraud, ECB, tokenization, astronomy, etc.) and would not fill the gap.
Filling gap — buying Onchain Micropayments Digest — Nanopayments and the $0.000001 floor ($0.005)…
Paid $0.005 to Onchain Micropayments Digest — Nanopayments and the $0.000001 floor (settled 70f2d119-0…) — S4
Attention budget reached 4 source(s); stopping gap expansion.
Final check — "What are the conflicting published estimates of x402 settlem…": 100% assessed by S1, S2
Final check — "How does x402 settlement time work in practice, according to…": 100% assessed by S1, S2
Final check — "Which published material supports the explanation of how x40…": 100% assessed by S1, S2
Final check — "What explains the conflict among the published estimates of …": 80% assessed by S1, S2
Final coverage assessment — The supplied passages provide two conflicting published estimates of x402 settlement time: S1 claims roughly 180 ms via Arc batched settlement, while S2 claims about 15 seconds via Ethereum L1-style mining. S1 also gives a practical explanation for why x402 settlement can be sub-second: Arc BFT consensus and Gateway-batched payments are not block-time-bound. S2 gives the opposing practical explanation: each payment is its own transaction waiting to be mined. Thus the conflict is explained by differing assumptions about settlement architecture (batched Arc/Gateway settlement vs. per-payment L1 mining). However, no source directly frames the conflict as a conflict or explicitly reconciles the two estimates. S3 and S4 provide general context about USDC/onchain settlement and batched nanopayments but do not give x402-specific settlement times or directly explain the x402 conflict. The assessment does not establish a complete supported answer for every requested part.
Synthesizing a grounded answer from 4 source(s)…
Relevance review returned; only checked excerpts can retain support, and review cannot raise it.
⚖️ Sources disagreed on x402 settlement time — S1 x402 batched settlements finalize in roughly 180 milliseconds (median 178ms, p95 240ms) because Arc's BFT consensus delivers sub-second finality and Gateway-batched payments are not block-time-bound. vs S2 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. → reported preference: S1 (S1 provides a specific measurement (median 178ms, p95 240ms) from thousands of submitBatch calls on Arc testnet and an internally consistent mechanism (BFT consensus, Gateway batching). S2 is described as a reading based on an Ethereum L1 analogy and does not provide measurement data.)
Verified — S1 supports claim 1 at 60%: “Across thousands of submitBatch calls on Arc testnet, x402 batched settlements finalize in roughly 180 milliseconds (measured median 178ms, …”
Verified — S2 supports claim 1 at 60%: “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…”
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 — it is not block-tim…”
Below support/reward gate — S4 supports claim 2 at 20%: “Nanopayments push the minimum economical payment to about $0.000001 by signing off-chain authorizations and settling them in batches.”
Verified — S1 supports claim 3 at 80%: “Across thousands of submitBatch calls on Arc testnet, x402 batched settlements finalize in roughly 180 milliseconds (measured median 178ms, …”
Below support/reward gate — S4 supports claim 3 at 20%: “Instead of paying gas per transaction, many micro-authorizations settle together.”
Verified — S2 supports claim 4 at 70%: “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…”
Below support/reward gate — S4 supports claim 4 at 10%: “Nanopayments push the minimum economical payment to about $0.000001 by signing off-chain authorizations and settling them in batches.”
Rejected 0 invalid evidence span(s) and 2 unsupported citation marker(s); rejected markers cannot receive citation rewards.
Drafted answer citing 2 source(s)
Confidence: Low — the final assessment does not establish a complete supported answer for every requested part.
Arc Settlement Benchmarks contributed 60% - reward $0.009
Web Payments Review contributed 40% - reward $0.006
Settled $0.009 citation reward → Arc Settlement Benchmarks (9ccee486-8…)
Settled $0.006 citation reward → Web Payments Review (755c13ad-2…)
Done. Spent $0.02 across 3 confirmed/simulated payment(s) to creators.
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.
Carries this dispatch’s question as context — never its answer. The next dispatch is read from sources bought for it.