Canonical: https://builtonarc.app/guides/arc-security-and-monitoring-providers # Security and monitoring providers for Arc, confirmed so far Updated 2026-09-02. Chainalysis, Elliptic and TRM Labs document Arc compliance support. Runtime monitoring is thinner and unconfirmed; custody has moved to Wallets & Custody. > Circle's developer documentation names three compliance vendors for Arc as of 2 September 2026: Chainalysis, Elliptic, and TRM Labs — transaction monitoring, address screening, and AML/sanctions tooling. That is a narrower category than runtime security monitoring (contract-level anomaly detection and incident response) or custody-grade key management, where the confirmed record on Arc is thinner. Fireblocks is a named integration partner in Circle's founding-validator announcement; Forta, OpenZeppelin Defender, and Hexagate have no confirmed Arc-specific integration Built on Arc could source. ## Two different things both called "security" here "Security and monitoring" for a chain covers at least two distinct jobs a team sources separately: compliance monitoring (screening addresses and transactions against sanctions lists and known-illicit activity, usually a regulatory or partner requirement) and runtime security monitoring (watching a protocol's own contracts for anomalous activity — draining, price-oracle manipulation, unusual admin-key usage — in order to react before or during an exploit). Custody and key management (how a team actually holds and signs with the keys controlling its contracts and treasury) is a third, related layer. Arc's documented ecosystem, as of 2 Sep 2026, is unevenly built out across the three. ## Compliance monitoring: the confirmed layer Circle's compliance-vendors reference names three providers directly, each with a stated Arc-relevant capability: **Chainalysis** — a blockchain data platform for transaction monitoring, address screening, and investigation tooling, aimed at AML, sanctions, and fraud detection. > **Builds on Arc:** Provides transaction monitoring and address screening for Arc. · **Role:** Serves · **Category:** Compliance & Analytics · [Project page](/project/chainalysis) **Elliptic** — blockchain analytics and transaction-monitoring APIs for identifying illicit activity and assessing AML/sanctions risk; separately dated its own Arc coverage to the 28 Oct 2025 public testnet launch, making it testnet-scoped as of that announcement. > **Builds on Arc:** Provides blockchain analytics and AML/sanctions screening for Arc, testnet-scoped since 28 Oct 2025. · **Role:** Serves · **Category:** Compliance & Analytics · [Project page](/project/elliptic) **TRM Labs** — risk intelligence, wallet screening, and real-time monitoring for fraud and money-laundering detection; also named directly in Circle's description of Arc's agentic-economy compliance screening, alongside Elliptic, as providing integrated checks for agent-to-agent payment flows. > **Builds on Arc:** Provides wallet-screening and fraud-risk intelligence for Arc, including agent-payment flows. · **Role:** Serves · **Category:** Compliance & Analytics None of the three carries a mainnet-specific claim in the material Built on Arc reviewed — consistent with the rest of Arc's developer stack being documented against testnet pre-launch. ## Runtime monitoring: the unconfirmed layer Forta (decentralized detection network for on-chain threats), OpenZeppelin Defender (a widely used operations and monitoring platform for smart contracts), and Hexagate (real-time on-chain risk monitoring) are three of the more commonly deployed runtime-monitoring tools across EVM chains generally. Built on Arc searched for Arc-specific integration documentation, blog posts, or announcements from each and found none as of 2 Sep 2026. That is an absence from the public record, not a claim that any of the three has ruled out Arc support — general-purpose EVM monitoring tools frequently work across new EVM chains without a dedicated announcement, but "frequently works elsewhere" is not the same as "confirmed on Arc," and this guide does not blur the two. ## Key management and custody Custody and key management is a separate category under Built on Arc's taxonomy — see [Wallets & Custody](/category/wallets-custody) for the full comparison, including Ledger, MetaMask, and other institutional custody names from Circle's founding-validator release. **Fireblocks** is the one name from that release with a direct security/monitoring-adjacent relevance here. > **Builds on Arc:** Named as a custody/institutional integration partner in Circle's Arc founding-validator release. · **Role:** Serves · **Category:** Wallets & Custody → Custodians · [Project page](/project/fireblocks) ## What "no confirmed integration" should and shouldn't tell a builder A team choosing runtime monitoring or custody infrastructure for an Arc deployment should not read the gaps above as "these tools don't work on Arc" — most are built on standard EVM RPC and event-log interfaces that Arc supports natively, and a general-purpose EVM monitoring setup may function without any Arc-specific integration work at all. What the gap means concretely is that none of these vendors has published Arc-specific configuration, tested edge cases (like Arc's non-standard native-token transfer events, documented in its EVM-differences reference), or support commitments — so a team relying on one should verify compatibility itself rather than assume vendor-tested parity with, say, Ethereum mainnet or another established EVM chain. Sources: - [Arc compliance vendors reference](https://docs.arc.io/arc/tools/compliance-vendors.md) - [Arc agentic economy overview](https://docs.arc.io/build/agentic-economy.md) - [Arc EVM differences reference](https://docs.arc.io/arc/references/evm-differences.md) - [Circle: founding validator cohort press release, 5 Aug 2026](https://www.circle.com/pressroom/circle-announces-founding-validator-cohort-and-major-integrations-for-arc-ahead-of-september-16-mainnet-launch) - [Circle: Arc Public Testnet launch, 28 Oct 2025](https://www.circle.com/pressroom/circle-launches-arc-public-testnet) *Built on Arc is an independent directory. Arc is a Circle product; we are not affiliated with, endorsed by, or operated by Circle.* ## Questions **Is Elliptic's Arc coverage still testnet-only as of 2 Sep 2026?** Yes, based on the dated announcement Built on Arc could source, which tied Elliptic's Arc coverage to the 28 Oct 2025 public testnet launch; no subsequent mainnet-specific statement was found. **Does Chainalysis have a confirmed Arc relationship?** Yes — Chainalysis is named directly in Circle's own compliance-vendors documentation as of 2 Sep 2026, which supersedes earlier reporting that found no confirmed relationship; this guide reflects the current, sourced state. **What does TRM Labs' role in the "agentic economy" section mean?** Circle's own documentation on Arc's agent-payment infrastructure (ERC-8004 identity, ERC-8183 job settlement) names Elliptic and TRM Labs together as providing "integrated compliance screening" for that flow — the clearest signal Built on Arc found that compliance monitoring is being built into agent-to-agent payments specifically, not just human-initiated transactions. **Should I use a general EVM monitoring tool on Arc even without a vendor's explicit Arc support statement?** That's a case-by-case technical decision outside what this guide can make for you; the honest answer is that compatibility is plausible given Arc's EVM base but unverified by the vendor, so test it rather than assume it. **Is there a Circle-published list of runtime security monitoring vendors, separate from compliance vendors?** Not as of 2 Sep 2026 — Circle's docs.arc.io tools section covers node providers, data indexers, oracles, account abstraction, and compliance vendors specifically; it does not have a distinct runtime-security-monitoring category.