Canonical: https://builtonarc.app/guides/compliance-and-travel-rule-providers-on-arc

# Compliance and Travel Rule providers on Arc — what's confirmed and what isn't

Updated 2026-09-02. Travel Rule, sanctions screening, and KYT on Circle's Arc chain — Chainalysis, Elliptic and TRM Labs named in Circle's own docs, as of 2 Sep 2026.

> A permissioned validator set — the roughly 100 institutions running Arc's consensus — governs who can validate transactions. It doesn't screen who is sending them, monitor for sanctioned addresses, or exchange the counterparty information the Travel Rule requires; those are separate, application-layer functions. Circle's own Arc developer documentation names three compliance vendors directly — Chainalysis, Elliptic, and TRM Labs — as of 2 Sep 2026; Elliptic additionally has a dated, testnet-scoped announcement beyond that listing. No dedicated Travel Rule messaging vendor is named. Arc mainnet doesn't launch until 16 September 2026.

## What a permissioned validator set does and doesn't do

Arc's consensus layer, Malachite — a Tendermint-based BFT engine — runs across a permissioned validator set: the entities allowed to validate are known and approved, unlike a fully permissionless chain. That's a meaningful governance and network-security property, controlled by roughly 100 institutions including 11 named founding validators from Circle's 5 August 2026 press release — BlackRock, DTCC, Galaxy, Global Payments, ICE, Mastercard, MoneyGram, SBI Group, Standard Chartered, Sumitomo Corporation, and Visa.

What that permissioning doesn't do: validate a wallet's identity, screen transactions against sanctions lists, flag laundering patterns, or transmit Travel Rule counterparty data. Those sit at the application layer — built by wallets, exchanges, custodians, and compliance vendors, not something a validator set performs by design. "Institutional, permissioned validator set" is not a substitute for a business's own KYT, sanctions-screening, and Travel Rule program.

## The Travel Rule, without a number this guide can't verify

The Travel Rule — a Bank Secrecy Act requirement extended to virtual-asset transfers by FATF's 2019 guidance — requires regulated providers (VASPs) to collect and transmit originator and beneficiary information above a jurisdiction-specific threshold. That threshold isn't one number: reporting compiled from jurisdictional trackers describes the US FinCEN threshold at $3,000, the UK's FCA applying £1,000 domestically and effectively £0 cross-border, and the EU's Transfer of Funds Regulation (TFR) applying with no minimum. This guide won't state a single global number, because there isn't one — a business operating across jurisdictions needs to map the specific threshold in each market it serves.

## Sanctions screening and KYT

KYT and sanctions-screening tools analyze blockchain activity — specific addresses and transaction patterns — against sanctions lists (like OFAC's) and behavioral risk indicators. This is analytics infrastructure sitting on top of a chain's public transaction data; it requires a specific integration, typically a vendor relationship, to deploy for a given chain.

## What's actually confirmed for Arc, provider by provider

Circle's own Arc developer documentation publishes a dedicated compliance-vendors reference page (`docs.arc.io/arc/tools/compliance-vendors`) naming three providers directly: Chainalysis, Elliptic, and TRM Labs — a primary-sourced confirmation for all three. It does not state mainnet-versus-testnet scope for any of them.

**Elliptic** has the strongest confirmation of the three: beyond the documentation listing, Elliptic announced on 28 October 2025 that it's providing blockchain analytics to Circle's Arc *testnet*, "joining Arc's testnet" to extend its Circle collaboration — a real, dated, named relationship, explicitly testnet-scoped in Elliptic's own announcement. No separate confirmation extending it to mainnet was found as of 2 Sep 2026.

> **Builds on Arc:** Providing blockchain analytics to Arc testnet since October 2025, extending its Circle collaboration. · **Role:** Serves · **Category:** Compliance & Analytics · [Project page](/project/elliptic)

**Chainalysis** is named in Circle's compliance-vendors documentation as a vendor for "transaction monitoring, address screening, and investigation tools" aimed at AML, sanctions, and fraud detection — correcting earlier reporting on this page, which had found no independently verifiable Arc-specific relationship and treated Chainalysis as unconfirmed. No separate dated press release beyond the documentation listing was found as of 2 Sep 2026. See Built on Arc's <a href="/chainalysis-on-arc">Chainalysis on Arc</a> page for the full readout.

> **Builds on Arc:** Named in Circle's Arc docs for transaction monitoring, address screening, and investigation tooling. · **Role:** Serves · **Category:** Compliance & Analytics · [Project page](/project/chainalysis)

**TRM Labs** is named in Circle's compliance-vendors documentation for "risk intelligence, wallet screening, and monitoring" across Arc transactions, and separately alongside Elliptic in Circle's agentic-economy documentation as providing compliance screening for agent-to-agent payment flows (ERC-8004 identity, ERC-8183 job settlement).

> **Builds on Arc:** Named for wallet screening and risk intelligence, including agent-to-agent payment compliance on Arc. · **Role:** Serves · **Category:** Compliance & Analytics

**Notabene** — a widely used Travel Rule messaging platform — does not appear on Circle's compliance-vendors documentation, and no Arc-specific relationship was found as of 2 Sep 2026. That's the clearest remaining gap: none of Circle's three named vendors is a dedicated Travel Rule messaging platform the way Notabene is.

Circle's 5 August 2026 press release — the source for Arc's founding-validator and integration-partner list — separately names Rain, Thunes, Wirex, Fireblocks, Chainlink, Kraken, Ledger, and MetaMask, among others, but not Chainalysis, Elliptic, or TRM Labs; those three are confirmed instead through Circle's separate compliance-vendors documentation.

## What this means for compliance readiness ahead of mainnet

The honest state of this category as of 2 Sep 2026: three named analytics and monitoring vendors confirmed through Circle's own documentation, with Elliptic carrying an additional testnet-dated announcement, and no dedicated Travel Rule messaging platform named. A business needing Travel Rule and sanctions-screening capability at mainnet shouldn't assume the documented vendors have mainnet coverage solved already — Circle's listing doesn't state that — and should confirm mainnet-specific Arc coverage and Travel Rule messaging capability directly, budgeting for that as a gap rather than assuming it off the shelf. Built on Arc's <a href="/guides/arc-for-payment-service-providers">PSP guide</a> covers the adjacent build-versus-buy question.

Built on Arc is an independent directory. Arc is a Circle product; we are not affiliated with, endorsed by, or operated by Circle.



Sources:
- [Arc compliance vendors documentation](https://docs.arc.io/arc/tools/compliance-vendors.md)
- [Elliptic provides Circle's Arc testnet with blockchain analytics](https://www.elliptic.co/blog/elliptic-provides-circles-arc-testnet-with-blockchain-analytics)
- [Circle Announces Founding Validator Cohort and Major Integrations for Arc](https://www.circle.com/pressroom/circle-announces-founding-validator-cohort-and-major-integrations-for-arc-ahead-of-september-16-mainnet-launch)
- [Eco: Travel Rule for Stablecoins — 2026 Compliance Guide](https://eco.com/support/en/articles/15210554-travel-rule-for-stablecoins-2026-compliance-guide)

## Questions

**Does Arc's permissioned validator set mean Travel Rule compliance is built in?**

No. The validator set governs consensus; Travel Rule compliance is an application-layer function built separately by wallets, exchanges, and compliance vendors.

**What is the Travel Rule threshold on Arc?**

No single number, and it isn't Arc-specific — it's set per jurisdiction, ranging from no minimum (EU's TFR) to a specific amount elsewhere (FinCEN's $3,000 in the US). Map the applicable threshold per jurisdiction.

**Are Chainalysis, Elliptic, and TRM Labs confirmed on Arc?**

Yes, all three are named directly in Circle's own compliance-vendors documentation as of 2 Sep 2026 — a correction, for Chainalysis, to earlier reporting on this page that found no relationship. Elliptic additionally has a dated announcement (28 October 2025) scoping its involvement to testnet; no mainnet-versus-testnet scope is stated for any of the three in Circle's listing itself.

**Is Notabene confirmed on Arc?**

Not yet confirmed as of 2 Sep 2026 — it does not appear on Circle's compliance-vendors documentation, and no dated, Arc-specific announcement was found.

**Does a business need a Travel Rule vendor before mainnet?**

If it plans regulated volume across any jurisdiction's threshold, yes — no dedicated Travel Rule messaging vendor is named in Circle's Arc documentation, so that capability shouldn't be assumed off the shelf.