Can you give a concrete example of blockchains for tiny automated payments using published source material?
9/30/2026, 12:03:02 PM · llm:deepseek:deepseek-v4-flash
For tiny automated payments, the published sources point to Arc as the blockchain used, with x402 as the payment rail. Arc testnet measurements show x402 batched settlements finalizing in roughly 180 milliseconds, and Arc's BFT consensus delivers sub-second finality so a Gateway-batched payment confirms in well under a quarter second, unlike an Ethereum L1 transaction . The concrete documented example is x402 batched settlements on Arc testnet, where thousands of submitBatch calls were measured . Separately, x402 is described as reviving the HTTP 402 status as a real payment rail, allowing agents to pay per request without accounts or API keys. However, the sources disagree on settlement timing: one source states x402 payments take about 15 seconds to settle, similar to an Ethereum L1 block time, because each payment is its own transaction waiting to be mined . The Arc-specific measurement is more specific and internally consistent with its described BFT consensus, so it is treated as the trusted account for Arc-based x402 settlement.
Evidence ledger — quotes verified before rewards
Which blockchains are used for tiny automated payments?
70%“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
What concrete example of a blockchain for tiny automated payments is documented in published sources?
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
“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.” [S3] How long do x402 payments take to finalize?
Cited sources and planned rewards
- 1Measuring x402 settlement latency on ArcArc Settlement Benchmarks70%$0.0105 planned
- 3How long do x402 payments take to finalize?Web Payments Review30%$0.0045 planned
Decision log · 54 steps
Breaking down: "Can you give a concrete example of blockchains for tiny automated payments 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 3/6 positive proposal(s): 3 cached + 0 fresh, predicting 2/2 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 (2/2); paid reading may proceed within the budget.
Cached abstract benchmarking x402 batched settlement on Arc testnet — a concrete blockchain rail for tiny automated payments. Reputation 24/100, cited 39% of reads. Supports claims 0 and 1. — selected for the claim-aware evidence portfolio (targets claims 1, 2; 0 fetch USDC, 1 attention slot).
Cached abstract on x402 as an agent payment rail — directly relevant to concrete blockchain rails for tiny automated payments. Reputation 20/100, cited 30% of reads. Supports claims 0 and 1. — selected for the claim-aware evidence portfolio (targets claims 1, 2; 0 fetch USDC, 1 attention slot).
Cached abstract on x402 payment finalization timing — relevant to concrete blockchain rails for tiny automated payments. Reputation 25/100, cited 44% of reads. Supports claims 0 and 1. — selected for the claim-aware evidence portfolio (targets claims 1, 2; 0 fetch USDC, 1 attention slot).
Cached abstract on stablecoins as agent unit of account — relevant to which blockchains/rails support tiny automated payments (USDC/EURC onchain settlement), but only an abstract, so modest value. Supports claim 0. — the claim-aware portfolio chose a stronger, less redundant set inside the 4-source attention and $0.015000 fetch-budget caps, so this proposal stays unspent.
Cached abstract on sub-cent/nanopayments and gas-efficient settlement primitives — topical for tiny automated payments, though preview is about citation weighting. Supports claim 0. — the claim-aware portfolio chose a stronger, less redundant set inside the 4-source attention and $0.015000 fetch-budget caps, so this proposal stays unspent.
Idempotency keys for retries is generic distributed-systems material, not a concrete blockchain example for tiny payments. Low relevance.
Gardening content, entirely off-topic.
Retro console repair, entirely off-topic.
Stripe dispute-evidence analysis is about chargebacks, not blockchains for tiny automated payments. Off-topic.
Ethereum Foundation post on AI agents triaging protocol code — Ethereum is a blockchain but the preview is about security triage, not tiny automated payments. Weak fit.
Cached abstract on SoFi moving card settlement to a stablecoin blockchain rail — a concrete blockchain settlement example, though at $25B volume rather than tiny payments. Supports claim 1. — cached bytes are free, but this read does not clear the attention gate (EV 0.40, minimum 0.45, with a required claim target).
Full-text but about hiring an AI engineer for <$6/hr; no blockchain micropayment example. Latent.Space has 0 citations on this subject.
Metadata-only, no preview content, and Blender/coding agents is off-topic.
Metadata-only title about agent memory; no blockchain micropayment content.
Metadata-only preview; low-risk DeFi on Ethereum is tangentially about onchain settlement but no concrete tiny-payment example and no readable content.
2022 Coinbase Cloud developer-platform launch; not about blockchains for tiny automated payments.
Sony game ownership/NFTs — not about tiny automated payments.
Digital bond issuance on Euroclear's blockchain is a settlement example but institutional/large-value, not tiny automated payments.
Esoteric mythology content, entirely off-topic.
Fan-loyalty blockchain article; not about tiny automated payments.
First-party Keryx full-text on paid research job recovery; highest reputation (40/100) and full text, but preview concerns buyer recovery rather than a concrete blockchain for tiny payments. Supports claim 0 loosely. — the claim-aware portfolio chose a stronger, less redundant set inside the 4-source attention and $0.015000 fetch-budget caps, so this proposal stays unspent.
Agent spend wallet ready: 0x29028Fe1122E17Fe7863A22701e863FE4DaE1aFB (balance sufficient)
Reused cached Arc Settlement Benchmarks — Measuring x402 settlement latency on Arc (free) — S1
Reused cached Agent Economy Weekly — x402 turns HTTP 402 into an agent payment rail (free) — S2
Reused cached Web Payments Review — How long do x402 payments take to finalize? (free) — S3
Sub-claim "Which blockchains are used for tiny automated payments?": 70% covered by S1, S2 — S1 names Arc (Arc testnet) as a blockchain where x402 batched settlements finalize in ~180ms, and S2 documents x402 as a per-request agent payment rail. Together they identify Arc as a blockchain used for tiny automated payments. The answer is direct but limited to one named chain; no broader survey of chains is provided.
Sub-claim "What concrete example of a blockchain for tiny automated pay…": 80% covered by S1, S2 — S1 gives a concrete documented example: thousands of submitBatch calls on Arc testnet, x402 batched settlements finalizing in roughly 180ms median (178ms, p95 240ms), with Arc's BFT consensus delivering sub-second finality. S2 supplies the x402 per-request payment mechanism. This is a direct concrete example, though S3 offers a conflicting 15-second Ethereum L1-style settlement view that is not reconciled.
Coverage is adequate for both sub-claims: Arc is explicitly named as the blockchain, and a concrete documented example (x402 batched settlement on Arc testnet with ~180ms finality) is provided. No affordable skipped source clearly fills a remaining gap; the skipped items concern stablecoins, idempotency, disputes, or unrelated topics, not additional concrete blockchain examples for tiny automated payments. Remaining budget is small and buying more is not warranted.
Final check — "Which blockchains are used for tiny automated payments?": 80% assessed by S1
Final check — "What concrete example of a blockchain for tiny automated pay…": 80% assessed by S1
Final coverage assessment — S1 documents a concrete blockchain (Arc) used for tiny automated payments via x402 batched settlements, with measured finality (~180ms median). S2 provides topical context on x402 as an agent payment rail but does not name a specific blockchain. S3 discusses x402 settlement timing but names no blockchain and is a general timing view, not a concrete blockchain example. The requested concrete example is directly supported by S1; no requested part remains missing.
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 timing — S1 x402 batched settlements on Arc testnet finalize in roughly 180 milliseconds, with sub-second finality and not block-time-bound like Ethereum L1. vs S3 x402 payments take about 15 seconds to settle, similar to Ethereum L1 block time, because each payment is its own transaction waiting to be mined. → reported preference: S1 (S1 provides a specific measured benchmark on Arc testnet and is internally consistent with its described BFT consensus, whereas S3 is a general reading without Arc-specific measurement.)
Verified — S1 supports claim 1 at 70%: “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 — S1 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 — S2 supports claim 2 at 20%: “Agents can therefore pay per request with no accounts or API keys, discovering and purchasing data autonomously at runtime.”
Verified — S3 supports claim 2 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…”
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: Moderate — source preferences are explained, but conflicting evidence limits confidence.
Arc Settlement Benchmarks contributed 70% → reward $0.0105
Web Payments Review contributed 30% → reward $0.0045
Settled $0.0105 citation reward → Arc Settlement Benchmarks (0234857e-c…)
Settled $0.0045 citation reward → Web Payments Review (04389f5c-7…)
Done. Spent $0.015 across 2 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.