ai
3 мин
25 октября 2026 г.
Источник: Dev.to AI Feed

Five Wallets Paid an x402 Seller. What Can We Say About Demand?

Alex
Alex
RSS AI Ingest
Five Wallets Paid an x402 Seller. What Can We Say About Demand?

AI disclosure — Fully Autonomous: AI agents prepared this analysis, its implementation and this article under the project owner’s direction. I maintain HISTOR and AIMarket in the alexar76 ecosystem. Deterministic code produced the counts an...

AI disclosure — Fully Autonomous: AI agents prepared this analysis, its implementation and this article under the project owner’s direction. I maintain HISTOR and AIMarket in the alexar76 ecosystem. Deterministic code produced the counts and transfer checks; no model inferred wallet identities. One research payment was ours, and it is identified below. After our x402 delivery survey, Martin Pisacreta reported that textokit’s only repeat payer appeared to send the published normativa-ar inputExample. He asked whether HISTOR could flag wallets whose activity resembled a sweep. We implemented a local audit and checked all five external payers. The useful result is an evidence table with explicit unknowns. The payment totals hold up The public seller ledger, retrieved on 25 October 2026 at 05:16:44 UTC, contained 80 settled sales: 56 marked as own-wallet sales by the publisher and 24 external sales from five wallets, totaling 0.055000 USDC. Publisher ownership flags are source claims, not independently authenticated identities. All 24 external entries matched successful Base transaction receipts containing an official USDC Transfer from the stated payer to the seller for the exact stated amount. That verifies settlement. It does not verify service delivery or why somebody paid. The ledger is live; these are snapshot figures. For context, we scanned outgoing USDC transfers from these five addresses over 11 October 2026, 05:23:11 UTC, through 25 October 2026, 05:23:11 UTC: blocks 52453422–53058222. All 605 consecutive log ranges completed successfully, returning 23,254 raw events. Two zero-value events were excluded from behavioral metrics. Collection finished at 05:27:36 UTC. The selected head was twelve blocks behind the initial node head, and its hash remained stable. What the five wallets show Addresses below link to their public explorer pages. “Recipients” means distinct USDC recipient addresses, which are not necessarily merchants or x402 services. The outgoing-transfer counts exclude the two zero-value events. Wallet textokit sales USDC Outgoing transfers / recipients Recipients paid once Transfers ≤0.01 USDC Audit label 0x097e…475a 1 0.001000 5 / 4 3 (75.0%) 1 (20.0%) known-probe 0x7722…5e4a 1 0.001000 1,262 / 1,010 909 (90.0%) 1,051 (83.3%) unknown 0xa1d1…1978 1 0.001000 1,896 / 1,632 1,416 (86.8%) 1,449 (76.4%) unknown 0xc9c7…1670 1 0.001000 1,979 / 730 442 (60.5%) 1,518 (76.7%) unknown 0xec2a…d034 20 0.051000 18,110 / 648 217 (33.5%) 16,320 (90.1%) probe-like 0x097e…475a was our research probe. Its single 0.001 USDC x402-ping purchase on 20 October matches our recorded survey transaction. The label applies to that purchase, not every future action by the address. 0xec2a…d034 made twenty purchases across seventeen services, including four normativa-ar purchases, between 20 and 24 October. Martin reports that it sends the published inputExample. We associated his statement with those four ledger rows by service and time. Their request payloads are not public, so exact per-transaction input matches were not independently verified. This supports a source-annotated probe-like indication; it does not establish a monitor’s identity. Without that annotation, the strict automatic label is unknown. The remaining three wallets show broad small-payment activity, with unknown intent. The first two reached 1,010 and 1,632 recipients. Our earlier “more than a thousand” description holds, but “nearly all” should be replaced by the exact fractions above. The third reached 730 recipients and repeated recipients more often. Their individual 0.001 USDC textokit purchases establish neither an organic workflow nor monitoring. The function exists; the labels remain cautious The local, unreleased histor payer-audit command accepts public receipts, optional bounded chain evidence and transaction-scoped source annotations. It exports JSON and Markdown containing input hashes, the observation window, payer metrics, policy, settlement references and coverage limits. It needs no wallet keys or production database. Its collector allows five read RPC methods and never sends transactions or paid service requests. The initial broad-pattern heuristic requires at least 50 transfers, 50 recipients, 90% singleton recipients and 90% transfers of at most 0.01 USDC. These uncalibrated cutoffs were set before inspecting the collected metrics and were not relaxed to force a label. Descriptive signals remain visible when the combined rule fails. The result is one known probe, one source-annotated probe-like case and three unknown cases. Unknown does not mean confirmed buyer. Probe-like does not mean fraud or worthless usage. Paid monitoring can itself be genuine use. All 0.055000 USDC remains in the payment totals, regardless of labels. These observations do not determine textokit’s organic customer count, profitability, service delivery or wallet ownership. RPC checks trust the selected Base node; they are not locally verified chain proofs. The practical improvement is narrower: settlement, behavior and sourced claims now have separate fields, so a receipt count need not silently become a customer count. Public settlement references The following 24 public transactions correspond to the verified external ledger entries, grouped by payer. Amounts are USDC. The live ledger and the explorer links are primary sources; the fourteen-day behavioral figures above refer to the fixed observation window. 0x097e3f339d0b023605e12a6b81e2d6cb7571475a 0x62c01526… — 0.001000 USDC 0x7722dfae6bbed2fd02dc07455c2f5bf14be25e4a 0x8d2ccd6a… — 0.001000 USDC 0xa1d1c0cf717402ff3651aa4873ccf96410b01978 0x58ddb2e7… — 0.001000 USDC 0xc9c7b38c0942914fc8ea12063bc92dcd3b581670 0x3ca4f279… — 0.001000 USDC 0xec2abd3eda89bed90124736e317e847d5fb6d034 0x8c0acafc… — 0.005000 USDC 0xef5f2a2c… — 0.002000 USDC 0xcc3231d1… — 0.005000 USDC 0xa7662362… — 0.005000 USDC 0xd197a66a… — 0.003000 USDC 0x68a7bb46… — 0.002000 USDC 0x4f712436… — 0.002000 USDC 0x9fe21127… — 0.002000 USDC 0x23207988… — 0.001000 USDC 0x0e65e22c… — 0.001000 USDC 0x56eafab5… — 0.001000 USDC 0x55049b03… — 0.001000 USDC 0x6322b987… — 0.005000 USDC 0x415ec0e3… — 0.001000 USDC 0x4feb47e1… — 0.001000 USDC 0x9bb91375… — 0.001000 USDC 0x3bc01e29… — 0.001000 USDC 0x068b1930… — 0.002000 USDC 0x4700749e… — 0.005000 USDC 0xf93149b9… — 0.005000 USDC

Хотите внедрить ИИ в ваш бренд?

Спроектируем и развернем автономных агентов и современный цифровой стек под ваши задачи.

Рассчитать проект