Can you give a concrete example of Arc finality for small payment confirmation using published source material?
9/30/2026, 11:03:05 AM · llm:deepseek:deepseek-v4-flash + heuristic (fallback from llm:mimo:mimo-v2.5) on 1 step
Arc finality is described as sub-second finality delivered by Arc's BFT consensus, meaning a Gateway-batched payment confirms in well under a quarter second and is not block-time-bound the way an Ethereum L1 transaction is . For confirming a small payment, the concrete published example is x402 batched settlements on Arc testnet: across thousands of submitBatch calls, these finalize in roughly 180 milliseconds (measured median 178ms, p95 240ms) .
One point of disagreement should be noted: a separate source states 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. The Arc-specific benchmark is more specific and internally consistent with Arc's described BFT consensus, so the sub-second figure is the trusted account for Arc finality.
Note that the CoinDesk abstract does not address Arc finality or payment confirmation timing, so it provides no evidence for either research question.
Evidence ledger — quotes verified before rewards
What is Arc finality?
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.” [S2] Measuring x402 settlement latency on Arc
How does Arc finality apply to confirming small payments, according to published sources?
90%“Across thousands of submitBatch calls on Arc testnet, x402 batched settlements finalize in roughly 180 milliseconds (measured median 178ms, p95 240ms).” [S2] Measuring x402 settlement latency on Arc
Cited sources and planned rewards
- 2Measuring x402 settlement latency on ArcArc Settlement Benchmarks100%$0.015 planned
Decision log · 57 steps
Breaking down: "Can you give a concrete example of Arc finality for small payment confirmation using published source material?"
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 covers 1/2 sub-claims (50%). The agent may buy only claim-targeted sources and will label the answer provisional if paid evidence stays thin.
Strong topical match on using, payments, according, addresses sub-claim 2; worth the 0.002 USDC toll. — selected for the claim-aware evidence portfolio (targets claim 2; $0.002000 fetch USDC, 1 attention slot).
Already cached and still relevant (matches finality, payments); reuse for free instead of paying again. — free-preview expected value 0.12 is below the 0.12 spend floor, so no toll is authorized.
Weak match (only payment); not worth 0.004 USDC.
Already cached and still relevant (matches payments, sources); reuse for free instead of paying again. — free-preview expected value 0.12 is below the 0.12 spend floor, so no toll is authorized.
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 payments); not worth 0.002 USDC.
Already cached and still relevant (matches source, apply); reuse for free instead of paying again. — the free-preview coverage check could not connect this source to any sub-claim, so no toll is authorized.
Weak match (only using); not worth 0.003 USDC.
Weak match (only give); not worth 0.003 USDC.
Weak match (no key terms); not worth 0.004 USDC.
Already cached and still relevant (matches published, payments); reuse for free instead of paying again. — free-preview expected value 0.12 is below the 0.12 spend floor, so no toll is authorized.
Weak match (only payments); not worth 0.002 USDC.
Weak match (only according); not worth 0.002 USDC.
Weak match (only payment, payments); not worth 0.002 USDC.
Already cached and still relevant (matches arc, finality); reuse for free instead of paying again. — free-preview expected value 0.12 is below the 0.12 spend floor, so no toll is authorized.
Already cached and still relevant (matches payment, payments); reuse for free instead of paying again. — the free-preview coverage check could not connect this source to any sub-claim, so no toll is authorized.
Weak match (only payment); not worth 0.002 USDC.
Agent spend wallet ready: 0x29028Fe1122E17Fe7863A22701e863FE4DaE1aFB (balance sufficient)
Paying $0.002 toll to read CoinDesk: Bitcoin, Ethereum, Crypto News and Price Data — AI agents will soon buy their own computing power and data using stablecoins, according to BlackRock…
Paid $0.002 to CoinDesk: Bitcoin, Ethereum, Crypto News and Price Data — AI agents will soon buy their own computing power and data using stablecoins, according to BlackRock (settled 43ce4f4d-3…) — S1
Sub-claim "What is Arc finality?": 0% covered
Sub-claim "How does Arc finality apply to confirming small payments, ac…": 0% covered
The only supplied source (S1) is a CoinDesk abstract about BlackRock's view on AI agents using stablecoins for payments and computing capacity. It does not mention Arc, Arc finality, or small payment confirmation. Therefore neither sub-claim is answered by the published source material provided. The assessment does not establish a complete supported answer for every requested part.
Sub-claim "What is Arc finality?": 0% covered — The only gathered passage (S1) is a CoinDesk abstract about BlackRock viewing stablecoin payments as a nearer-term opportunity; it does not define Arc finality or mention Arc at all.
Sub-claim "How does Arc finality apply to confirming small payments, ac…": 0% covered — No gathered passage addresses Arc finality or small-payment confirmation. S1 discusses stablecoin payments generally but provides no concrete Arc finality example or confirmation procedure.
Both sub-claims are entirely uncovered (0.0). The affordable skipped sources most directly on point are the Arc Settlement Benchmarks item ($0.003), which explicitly covers x402 batched-settlement finality on Arc, and the Web Payments Review item ($0.002), which covers end-to-end x402 settlement timing. Together they cost $0.005, within the remaining $0.013 budget, and are the only skipped sources whose previews mention Arc finality or payment finalization. Other skipped sources concern unrelated topics (gardening, retro hardware, disputes, UPI, etc.) and should not be purchased.
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 f13539ee-a…) — S2
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 486313bb-0…) — S3
Final check — "What is Arc finality?": 100% assessed by S2
Final check — "How does Arc finality apply to confirming small payments, ac…": 100% assessed by S2
Final coverage assessment — S2 directly defines Arc finality as sub-second BFT consensus finality and gives a concrete x402 batched settlement example with measured latency, which answers both the definition and the small-payment confirmation application. S1 is only topical context about stablecoin payments and does not mention Arc finality. S3 gives a conflicting Ethereum-like settlement view but does not describe Arc finality or its small-payment confirmation behavior.
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 Settlement time for x402 payments on Arc — S2 x402 batched settlements on Arc testnet finalize in roughly 180 milliseconds (median 178ms, p95 240ms), with sub-second BFT finality and no block-time dependency vs S3 x402 payments take about 15 seconds to settle, similar to Ethereum L1 block time, because each payment waits to be mined into a block → reported preference: S2 (S2 is Arc-specific, reports measured benchmark data (median and p95) from thousands of submitBatch calls, and is internally consistent with its description of Arc's BFT consensus delivering sub-second finality, whereas S3 is a general reading that assumes block-mining behavior and does not reference Arc's consensus mechanism.)
Verified — S2 supports claim 1 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…”
Verified — S2 supports claim 2 at 90%: “Across thousands of submitBatch calls on Arc testnet, x402 batched settlements finalize in roughly 180 milliseconds (measured median 178ms, …”
Below reward gate — S3 supports claim 2 at 10%: “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…”
Rejected 0 invalid evidence span(s) and 2 unsupported citation marker(s); rejected markers cannot receive citation rewards.
Drafted answer citing 1 source(s)
Confidence: Moderate — source preferences are explained, but conflicting evidence limits confidence.
Arc Settlement Benchmarks contributed 100% → reward $0.015
Settled $0.015 citation reward → Arc Settlement Benchmarks (f7b867de-c…)
Done. Spent $0.022 across 4 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
1 exact cited article version 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.