Category
Compliance & Analytics on Arc · 3
Transaction monitoring, sanctions and wallet screening, blockchain intelligence and risk data — the vendors a regulated business needs before it can move money on a new chain. Role is Serves. Circle names several directly in Arc's own compliance-vendor documentation; others appear only in their own announcements, and the entry says which.
Worth being precise about scope: a permissioned validator set is not a compliance control, and a vendor listing is not an attestation that any particular obligation is met. Travel Rule thresholds and scope vary by jurisdiction, and the applicable regime is the reader's to determine with qualified advice. Entries record the relationship, the source and the date it was confirmed — nothing more.
| # | Project | What it builds on Arc | Role | Status | Links | Checked |
|---|---|---|---|---|---|---|
| 01 | Listed by Circle for Arc; transaction monitoring so banks can screen Arc USDC payments. | Serves | Announced | 2026-09-02 | ||
| 02 | Listed by Circle for Arc; wallet risk scoring for regulated firms touching Arc. | Serves | Announced | 2026-09-02 | ||
| 03 | Listed by Circle for Arc; blockchain intelligence for firms monitoring Arc activity. | Serves | Announced | 2026-09-02 |
Questions
Does coverage mean full attribution?
Not always. Some vendors ingest Arc transactions without full entity attribution. The entry sentence describes what the product actually does today.
How is status decided?
Status reflects what we observed on the date shown, not what a project announced. Every entry carries a dated source you can open and check yourself. Live can become Inactive if activity stops.
Does paying change where a project appears?
No. Paid entries are labelled Listing, sit in the same ranked order as everything else, and use rel="sponsored". Payment never affects status, flags, evidence or the Editor's Index.