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

No USDC transfers observed on 2026-10-12 yet; 0 addresses graded.

Addresses graded0/ 0 screensH 0 · M 0 · L 0
Observed wallets010 graded · 145 candidates on map
USDC observed0USDC0 transfers in the map window
Flagged share0.0%0 USDC · 0 transfers · 0 flagged wallets
Tier changes00 up · 0 down · map 0 / watch 0
Tailer ticks0/ dayno tick recorded · block 25,818,533
Fig. 01 · 30-day strip2026-09-13 → 2026-10-12 · UTC days · 1 rows
graded / day10flagged share of observed USDC1%0%2026-10-12: 0 graded2026-10-12: 0% of 0 USDC touched a flagged wallet0%09-1309-2009-2710-0410-12
addresses graded per daypartial day (still recomputed)flagged share of observed USDC volume
Fig. 02 · Tier mix and reason codes2026-10-12 · final
LOW
0 · 0.0%
MEDIUM
0 · 0.0%
HIGH
0 · 0.0%
Reason codeCountShare of screens
No screenings on this day.

Screens by client class: outside 0 · internal 0 · 0 client ids · 0 outside payers. Bridged inbound (CCTP): not tracked on this deployment.

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.
  • No CCTP inbound table on this deployment; bridged figures are zero and marked unavailable.
  • 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.