Documentation Home

Release Notes

October 7, 2026: Active Monitoring

ACE adds a continuous mode of compliance: Active Monitoring. It screens the addresses you choose with TRM on a schedule, applies a rule you define when an address's risk changes, and acts onchain on tokens you already run, without changing their contracts. Policy Manager and Identity Manager stay preventive: they block a transaction while it executes. See Preventive and Continuous Compliance.

What's new

  • Monitored tokens: Register a token and its associated contracts from their ABI, with the enforcement functions Active Monitoring may call. One configuration covers every network of the token. See Manage Monitored Tokens.
  • Monitoring rules: Map each TRM risk level to a response: Silently log, Flag for review, or Enforce one or more onchain actions, with an optional token balance condition. See Configure Monitoring Rules.
  • Watchlist and screening: Add addresses from a CSV file or an identity registry, store your TRM API key, and choose the screening interval. See Manage the Watchlist and Configure the TRM API Key and Screening Schedule.
  • Decisions log: Review every decision with the TRM result, the matched rule, and the operation status, and resolve or enforce flagged decisions. See Review Decisions and Track Operations.
  • Coordinator API: The new Active Monitoring endpoints cover these operations, except resolving and enforcing flagged decisions, which are available in the Platform UI only. See Active Monitoring API.

For the current limits, see Beta Scope.

September 14, 2026: Custom contracts

This release makes any ACE-compatible contract a first-class citizen in the platform, not just ERC-20 and ERC-3643 tokens.

What's new

  • Custom contract types: Declare contract types with your own function ABIs via the new /contract-types Coordinator API endpoints. Custom types appear alongside the built-in contract types (ERC-20, ERC-3643, and CCIP-AdvancedPoolHooks) and can be attached to policy engines and targets with contract_type_ids. See Custom Contract Types & Extractors.
  • Custom extractors: Write and deploy your own extractor contract (implementing IExtractor from the chainlink-ace repository) and register it via POST /extractors with its supported function signatures and per-chain deployment addresses. Pre-built extractors cover ERC-20, ERC-3643, and CCIP-AdvancedPoolHooks signatures; custom extractors extend coverage to any other function signature.
  • Contract types on engines and targets: POST/PUT /policy-engines and POST/PUT /targets accept contract_type_ids, and engine, target, and extractor responses now include their associated contract types (contract_types, assigned_contract_types).
  • ERC-3643 extractor coverage fix: ERC3643MintBurnExtractor now covers burn(address,uint256) only; mint(address,uint256) is covered by ComplianceTokenMintBurnExtractor. If you protect mint on an ERC-3643 token, attach ComplianceTokenMintBurnExtractor.

July 17, 2026: ACE Beta+

ACE Beta+ builds on ACE Beta with new compliance capabilities. This release is still a Beta — see Beta Scope for the current scope and limitations.

What's new

  • Custom policies — You can now write, deploy, and register your own policy contract and use it like a pre-built library policy. Custom policy implementations are scoped to your organization. See Custom Policies.
  • Grouped identity validation — The new GroupedIdentityValidatorPolicy applies different credential requirements to different accounts. It routes each account to a group — by credential attestation or by credential data (for example, jurisdiction) — then validates the account against that group's requirements. Use it to enforce, for example, one rule set for individuals and another for businesses, or different rules per jurisdiction, within a single policy.
  • External registries — Organizations can now share registries with each other. A registry owner grants another organization read access, and the grantee can use the shared registry's identities and credentials as a credential source in its own policies — without re-issuing credentials. Access is read-only for the recipient and revocable at any time. See External Registries.
  • Credential data validation — Credentials are no longer limited to attestation-only. You can now link a data schema to a credential type, issue credentials that carry structured data, and attach a Data Validator to a policy's credential source to enforce rules on that data. The first use case is jurisdiction control using a pre-built AllowDenyList Data Validator with ISO 3166-1 alpha-2 country codes. See Credential data and privacy.
  • Self-signing model — Organizations can now choose between delegated signing (Chainlink signs on your behalf) and self-signing (you sign operations yourself) at onboarding. With self-signing, ACE creates unsigned draft operations that you poll, sign (EIP-712), and submit using the CRE Connect SDK. Both models use the same CRE Connect Wallet and all platform capabilities work identically. See Signing & Ownership Model.
  • Managed offchain risk policies (MVP) — Screen transaction participants with TRM Wallet Screening before allowing a protected onchain action. Configure global and category-specific risk thresholds, request evaluations through the new Evaluation API, and receive single-use permits delivered onchain by a managed CRE workflow. Grant evaluation access to other organizations so they can request permits against your target contracts. This feature is an MVP; contact your Chainlink representative for help with setup. See Offchain Policies, Managing Offchain Policies (MVP), Requesting Offchain Permits, and Granting Evaluation Access.

May 26, 2026: Mainnet support

What's new

  • Mainnet deployments — ACE Beta now supports mainnet on Ethereum, Arbitrum, Avalanche, Base, and Polygon, in addition to existing testnets. Mainnet access is not enabled for all organizations by default — contact your Chainlink contact to request it. See Supported Networks for chain IDs and chain selectors.

Other improvements

  • Policy Engine creation is now available in the Platform UI under Compliance > Policy Manager (previously API-only). See Managing Policy Engines.

April 15, 2026: ACE Beta (Private Release)

Chainlink ACE Beta is now available to a first set of selected participants as a private release. This initial release provides early access to the ACE platform.

What's included

ACE Beta ships with three core components:

  • Policy Manager — Create policy engines, register target contracts, configure policy instances from the pre-built library, and enforce compliance rules on-chain.
  • Identity Manager — Set up identity registries, register on-chain identities, define credential types, and issue verifiable credentials for use in identity-based policies.
  • Reporting Manager — Query on-chain policy configurations, identity states, and transaction history via a read-only API to support compliance verification and auditing workflows.

All three components support multi-chain deployments across all supported testnets and are accessible via the Chainlink Platform UI and the Coordinator and Reporting APIs, once Chainlink provisions your organization with ACE Beta access.

Scope and limitations

This is a testnet-only release. For full details on what is supported, known constraints, and planned additions, see Beta Scope.

Get the latest Chainlink content straight to your inbox.