What does Web Payments Review establish about conflicting published estimates of x402 settlement time, and what remains uncertain?
9/30/2026, 9:10:54 AM · llm:deepseek:deepseek-v4-flash + heuristic (fallback from llm:mimo:mimo-v2.5) on 1 step
> ⚠ Low confidence — 2 sub-claims remain below the evidence threshold within budget. Treat this as provisional.
Web Payments Review does not itself establish a resolution of conflicting published estimates of x402 settlement time; it presents one estimate. According to Web Payments Review, 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 . On that view, agent-to-agent micropayments remain sluggish until block times shrink . This conflicts with Arc Settlement Benchmarks, which 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 the way an Ethereum L1 transaction is . The trusted position is the Arc benchmark because it is more specific (measured median and p95 across thousands of calls) and internally consistent with its stated consensus mechanism . What remains uncertain is whether Web Payments Review acknowledges, reconciles, or explains the conflicting estimates; the supplied Web Payments Review passage contains no statement about conflicting published estimates, so that part is unanswered. Cointelegraph.com News is unrelated to x402 settlement timing.
Evidence ledger — quotes verified before rewards
What does Web Payments Review establish about conflicting published estimates of x402 settlement time?
20%“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?
“Across thousands of submitBatch calls on Arc testnet, x402 batched settlements finalize in roughly 180 milliseconds (measured median 178ms, p95 240ms).” [S3] Measuring x402 settlement latency on Arc
What remains uncertain about x402 settlement time according to Web Payments Review?
0%No reward-qualifying evidence
Cited sources and planned rewards
- 2How long do x402 payments take to finalize?Web Payments Review45%$0.00675 planned
- 3Measuring x402 settlement latency on ArcArc Settlement Benchmarks55%$0.00825 planned
Decision log · 60 steps
Breaking down: "What does Web Payments Review establish about conflicting published estimates of x402 settlement time, and what remains uncertain?"
Identified 2 research target(s) to investigate; these are not established facts
Deep mode: up to 4 paid/cached reads plus one bounded gap-expansion pass when needed.
Discovered 21 verified source(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 1/1 positive proposal(s): 0 cached + 1 fresh, predicting 0/2 claim(s) above the evidence floor with $0.002000/$0.015000 fetch USDC reserved.
Free-preview pre-check maps an actionable source to every sub-claim (2/2); paid reading may proceed within the budget.
Strong topical match on payments, review, addresses sub-claim 1 & 2; worth the 0.002 USDC toll. — selected for the claim-aware evidence portfolio (targets claims 1, 2; $0.002000 fetch USDC, 1 attention slot).
Already cached and still relevant (matches payments, settlement); reuse for free instead of paying again. — cached bytes are free, but this read does not clear the attention gate (EV 0.15, minimum 0.45, with a required claim target).
Weak match (only x402); not worth 0.004 USDC.
Already cached and still relevant (matches payments, settlement); reuse for free instead of paying again. — cached bytes are free, but this read does not clear the attention gate (EV 0.15, minimum 0.45, with a required claim target).
Weak match (no key terms); not worth 0.003 USDC.
Weak match (no key terms); not worth 0.002 USDC.
Weak match (no key terms); not worth 0.002 USDC.
Weak match (only payments); not worth 0.002 USDC.
Weak match (no key terms); not worth 0.002 USDC.
Weak match (only web); not worth 0.004 USDC.
Weak match (no key terms); not worth 0.003 USDC.
Weak match (only time); not worth 0.003 USDC.
Weak match (only settlement); not worth 0.004 USDC.
Already cached and still relevant (matches payments, time, remains); reuse for free instead of paying again. — cached bytes are free, but this read does not clear the attention gate (EV 0.23, minimum 0.45, with a required claim target).
Already cached and still relevant (matches web, payments, remains); reuse for free instead of paying again. — cached bytes are free, but this read does not clear the attention gate (EV 0.23, minimum 0.45, with a required claim target).
Already cached and still relevant (matches web, settlement); reuse for free instead of paying again. — cached bytes are free, but this read does not clear the attention gate (EV 0.15, minimum 0.45, with a required claim target).
Weak match (only according); not worth 0.002 USDC.
Weak match (only remains); not worth 0.002 USDC.
Already cached and still relevant (matches x402, settlement); reuse for free instead of paying again. — cached bytes are free, but this read does not clear the attention gate (EV 0.15, minimum 0.45, with a required claim target).
Already cached and still relevant (matches web, payments, review, x402, settlement); reuse for free instead of paying again. — cached bytes are free, but this read does not clear the attention gate (EV 0.39, minimum 0.45, with a required claim target).
Weak match (only x402); not worth 0.002 USDC.
Agent spend wallet ready: 0x29028Fe1122E17Fe7863A22701e863FE4DaE1aFB (balance sufficient)
Paying $0.002 toll to read Cointelegraph.com News — CFTC submits crypto market regulation plan for White House review…
Paid $0.002 to Cointelegraph.com News — CFTC submits crypto market regulation plan for White House review (settled 6158989c-d…) — S1
Sub-claim "What does Web Payments Review establish about conflicting pu…": 0% covered
Sub-claim "What remains uncertain about x402 settlement time according …": 0% covered
The only gathered source (S1) is a Cointelegraph abstract about the CFTC submitting a crypto market regulation plan for White House review. It contains no mention of Web Payments Review, x402, settlement time, or conflicting published estimates. Therefore neither sub-claim is addressed by the supplied text. The assessment does not establish a complete supported answer for every requested part.
Sub-claim "What does Web Payments Review establish about conflicting pu…": 0% covered — The only gathered source (S1, Cointelegraph) concerns CFTC crypto market regulation and does not mention x402, settlement time, or Web Payments Review. The Web Payments Review source appears only as a skipped preview ('How long do x402 payments take to finalize?: An overview of end-to-end settlement timing for x402 and similar payment rails'), which is a title/preview, not an answer, and was not read.
Sub-claim "What remains uncertain about x402 settlement time according …": 0% covered — No gathered passage addresses x402 settlement time or any uncertainty about it. The skipped Web Payments Review preview gives only a topical description, not the requested content.
Both sub-claims are entirely uncovered (0.0). The Web Payments Review source (item:2f2c1d95, $0.002) is the named source in the question and directly targets x402 finalization timing, so it is the top priority. The Arc Settlement Benchmarks source (item:11203a0e, $0.003) provides x402 settlement latency benchmarks and could corroborate or supply the conflicting estimates. Total cost $0.005, within the $0.013 remaining budget. Other skipped sources are off-topic (gardening, retro hardware, fraud, etc.) and not worth buying.
Filling gap — buying Web Payments Review — How long do x402 payments take to finalize? ($0.002)…
Paid $0.002 to Web Payments Review — How long do x402 payments take to finalize? (settled ece8880e-6…) — S2
Filling gap — buying Arc Settlement Benchmarks — Measuring x402 settlement latency on Arc ($0.003)…
Paid $0.003 to Arc Settlement Benchmarks — Measuring x402 settlement latency on Arc (settled cc2dfa9c-1…) — S3
Final check — "What does Web Payments Review establish about conflicting pu…": 20% assessed by S2
Final check — "What remains uncertain about x402 settlement time according …": 0% assessed
Final coverage assessment — The supplied passages include a Web Payments Review abstract (S2) stating x402 settlement takes about 15 seconds, similar to Ethereum L1 block time, and an Arc Settlement Benchmarks abstract (S3) reporting roughly 180 ms batched settlement on Arc. However, the question asks specifically what Web Payments Review establishes about conflicting published estimates and what remains uncertain according to Web Payments Review. S2 provides only its own estimate and does not mention conflicting estimates, reconcile them, or identify uncertainty. S3 supplies a conflicting estimate but is not Web Payments Review and does not show that Web Payments Review addressed the conflict. Thus the requested Web Payments Review analysis of conflicting estimates and remaining uncertainty is not covered. The assessment does not establish a complete supported answer for every requested part.
Synthesizing a grounded answer from 3 source(s)…
Relevance review returned; only checked excerpts can retain support, and review cannot raise it.
⚖️ Sources disagreed on x402 settlement time — S2 About 15 seconds, similar to an Ethereum L1 block time, because each payment is its own transaction waiting to be mined into a block. vs S3 Roughly 180 milliseconds for batched settlements on Arc testnet, with sub-second finality and not block-time-bound like Ethereum L1. → reported preference: S3 (S3 is more specific, reporting measured median and p95 values across thousands of submitBatch calls, and is internally consistent with its stated BFT consensus mechanism; S2 is framed as an estimate ('In our reading') and does not address batched settlement.)
Verified — S2 supports claim 1 at 90%: “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 — S3 supports claim 1 at 90%: “Across thousands of submitBatch calls on Arc testnet, x402 batched settlements finalize in roughly 180 milliseconds (measured median 178ms, …”
Below reward gate — S2 supports claim 2 at 30%: “On that view, agent-to-agent micropayments remain sluggish until block times shrink.”
Below reward gate — S3 supports claim 2 at 30%: “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…”
Rejected 0 invalid evidence span(s) and 1 unsupported citation marker(s); rejected markers cannot receive citation rewards.
Drafted answer citing 2 source(s)
Confidence: Low — 2 sub-claims remain below the evidence threshold.
Web Payments Review contributed 45% → reward $0.00675
Arc Settlement Benchmarks contributed 55% → reward $0.00825
Settled $0.00675 citation reward → Web Payments Review (cf882877-8…)
Settled $0.00825 citation reward → Arc Settlement Benchmarks (776cd9a4-6…)
Done. Spent $0.022 across 5 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.