records · risk dataset · GET /api/v1/stats

Arc risk pulse

One signed row per UTC day, computed from what the CompliR tailer observed and what clients asked us to screen. Open data for analysts: JSON per day, a flat CSV, and an attester signature over every row.

API: /api/v1/stats · /api/v1/stats/<date>.json · /api/v1/stats/latest.csv

0.0% of observed USDC volume touched a flagged wallet today.

Addresses graded16/ 33 screensH 1 · M 1 · L 14

Observed wallets15510 graded · 145 candidates on map

USDC observed194,466.07USDC25 transfers in the map window

Flagged share0.0%0 USDC · 0 transfers · 1 flagged wallets

Tier changes10 up · 0 down · map 0 / watch 1

Tailer ticks2/ daylast 21:53 UTC · block 25,818,533

Fig. 01 · 30-day strip2026-09-14 → 2026-10-13 · UTC days · 2 rows

addresses graded per daypartial day (still recomputed)flagged share of observed USDC volume

Fig. 02 · Tier mix and reason codes2026-10-13 · partial

LOW: 14 · 87.5%
MEDIUM: 1 · 6.3%
HIGH: 1 · 6.3%

Reason code	Count	Share of screens
NO_HISTORY	16	48.5%
SANCTIONS_DIRECT	12	36.4%
USDC_BLACKLISTED	12	36.4%
PRIOR_HIGH_TIER	10	30.3%
FRESH_WALLET	9	27.3%
COMMUNITY_TIP_VERIFIED	8	24.2%
NETWORK_HELD_ELSEWHERE	8	24.2%
CLEAN	7	21.2%
LOOKALIKE_OF_KNOWN_PAYEE	2	6.1%

Screens by client class: outside 4 · internal 23 · unknown 6 · 8 client ids · 0 outside payers. Bridged inbound (CCTP): 0 USDC in 0 transfers, 0.0% to flagged wallets.

Fig. 03 · Caveatsread before citing

Sample = what the CompliR tailer observed in its block windows and what clients asked us to screen; it is not all of Arc.
Volume is the USDC moved on Transfer edges the tailer persisted that day (graded nodes and their counterparties); flagged = HIGH tier or a blocklist reason code at the time of computation.
Tailer ticks count distinct tick timestamps that wrote rows; quiet ticks (no USDC activity in the window) are not counted.
Computed before the UTC day ended; the row is recomputed and re-signed until it is final.
Flagged = HIGH tier or a blocklist reason code (sanctions, USDC blacklist, protocol blocklist) at the time the row was computed; a later regrade changes later rows, not this one.
Own wallets and internal client ids are excluded from the outside-payer counts; screenings they triggered are counted as internal.

Download

Day JSON Day CSV 30-day JSON All days CSV

CSV: one row per day, 47 flat columns, newest first. Schema in docs (docs/DATASET.md).

Signature

Row: 2026-10-13 (partial, will be recomputed)
Hash (keccak256 of canonical JSON): 0x7ddc387ed496de5ffad2301e995b50287b8f455b3d6715a84c0f4a939d5a8a9c
Signer (attester): 0xc742ada2872a042dd36d2e706907b4036968960c
Signature (EIP-191): 0x966e157188ef5f4957199d08a2d7fd3e5c8fda1435bbe842e2b6d0ef2792cbe062a520d0279c892581dac0f26b2793b6f0450ddd11ac2fbe9dfb4913106ad8ea1b
Computed: 2026-10-13T22:15:48.000Z

How to verify

Fetch the day, hash the stats object exactly as we do (sorted keys, no whitespace), and check the signature against the attester address.

import { keccak256, stringToHex, verifyMessage } from "viem";
const r = await (await fetch("/api/v1/stats/2026-10-13.json")).json();
const canon = (v) => Array.isArray(v) ? "[" + v.map(canon).join(",") + "]"
  : v && typeof v === "object" ? "{" + Object.keys(v).sort().map(k => JSON.stringify(k) + ":" + canon(v[k])).join(",") + "}"
  : JSON.stringify(v);
const hash = keccak256(stringToHex(canon(r.stats)));   // === r.hash
await verifyMessage({ address: r.signer, message: hash, signature: r.signature }); // true