x402 READING OF 11 NOVEMBER 2026: THE DATA IT RESTS ON MachineEconomy.ai This folder holds the data behind the reading of x402scan's payer and payee lists taken on 11 November 2026, and behind the seven concentrations it recorded (records 4 to 10). The reading is described, with its records, at https://machineeconomy.ai/methodology/x402-readings and in https://machineeconomy.ai/api/v1/diagnostics (data.x402.readings). Records 1 to 3 have no files here: they were recorded by our methodology ruling of 18 October 2026, before readings existed, by count and last payment. THE READING T is 2026-11-11 10:55:48 UTC, the timestamp of x402scan's sender-level 30-day view at the refresh that was read. The reading's window is the 30 days to T: after 2026-10-12 10:55:48 UTC, up to and including T. In that window, a single-use payer of a payee is a paying address that pays no other payee, and a sole-payer recipient of a payer is a recipient that no other payer pays. The reading records every payee with at least 1,000 single-use payers and every payer with at least 1,000 sole-payer recipients, with that number and the last payment between them. A record is a count. It says nothing about who runs the addresses or why, and it changes no value. All data was read from x402scan's public API on 11 November 2026, one request at a time. Times are UTC. Amounts are in USDC, to 6 decimals. THE FILES payers.csv Every paying address in x402scan's sender-level 30-day list at T: 29,078 rows, as the list returned them, sorted by payments, most first. Read 11:28:04-11:29:57 UTC, in 59 pages of 500, between two reads of the sender-level view that returned the same figures. The rows add up to the view: 29,078 addresses, 4,733,300 payments and 1,745,891.400657 USDC. Columns: sender the paying address tx_count its payments in the window total_amount_usdc their total unique_sellers the addresses it paid, counted on each chain and added up chains the chains it paid on facilitator_ids the facilitators that settled its payments, separated by | latest_block_timestamp its latest payment in the window, as the list had it payees.csv Every receiving address in x402scan's 30-day list of receiving addresses: 13,718 rows, as the list returned them, sorted by paying addresses, most first. Read 11:30:07-11:31:01 UTC, in 28 pages of 500, between two reads of the receiving-side view that returned the same figures, timestamped 10:55:48. The rows add up to the view: 13,718 addresses, 4,733,413 payments and 1,745,891.756513 USDC. Columns: recipient (the receiving address), then tx_count, total_amount_usdc, unique_buyers (the addresses that paid it, counted on each chain and added up), chains, facilitator_ids and latest_block_timestamp, as in payers.csv. record-NN--
.csv One file for each record, numbered as the records are (04 to 10). Each lists the addresses the record counts, one row each, copied unchanged from the list they appear in, in that list's order: a payee's record (04 to 07) lists its single-use payers, with their rows from payers.csv; every one has unique_sellers 1; a payer's record (08 to 10) lists its sole-payer recipients, with their rows from payees.csv; every one has unique_buyers 1. A record's count is the number of rows in its file. Its last payment is the latest latest_block_timestamp in its file, to the second, except where a later-payments file exists (below). How the addresses were found: 04 (payee 0x7284d41b5b852f2bd4c99bdf95043d84452d299c): its 1,568,322 payments were too many to read page by page. Instead, every paying address with unique_sellers 1 in payers.csv was read for its payments in the window: in batches of up to 100 addresses or, for an address with more than 500 payments, its newest payment only (12:36-13:54 UTC). 84 of the heaviest had been read earlier from their lists of recipients (11:46-11:54 UTC). The 9,077 whose only recipient in the window was this payee are its single-use payers. 05 to 07: every payment to the payee in the window was read (11:35-11:40 UTC). Its single-use payers are those of its payers with unique_sellers 1 in payers.csv. 08 to 10: every payment by the payer in the window was read (11:41-12:02 UTC). Its sole-payer recipients are those of its recipients with unique_buyers 1 in payees.csv. The payments read for 05 to 10 match the address's row in payees.csv or payers.csv. For 05 the read holds one payment more, made at 2026-10-12 10:57:25 UTC: inside the window, before the list's own 30 days began. Where a read came back short, it was read again with another page size and the two merged. A payer that pays on more than one chain could have unique_sellers above 1 while paying only one payee. No address in payers.csv pays on more than one chain, so every single-use payer here has unique_sellers 1. record-04-payee-0x7284d41b5b852f2bd4c99bdf95043d84452d299c-later-payments.csv Two payments that record 04's rows in payers.csv do not show. Each was made inside the window by one of the record's single-use payers to the payee, but was added to x402scan's data after the payer list was built, so that payer's row ends earlier. Record 04's last payment, 2026-11-11 10:55:41 UTC, is the second of them; its rows in payers.csv end at 10:54:24. The two payments are copied unchanged from a read of the newest payments by all payers, back to 10:42:00 UTC (11:27:30-11:27:40 UTC, 6 pages of 500). They are the only payments in that read, up to T, by one of record 04's single-use payers to the payee and later than that payer's row. Columns: block_timestamp when the payment was made sender the paying address recipient the receiving address amount_usdc the amount tx_hash the transaction log_index the payment's place in the transaction facilitator the facilitator that settled it chain the chain A record's last payment is the latest of its rows' latest_block_timestamp and its later payments, to the second.