Beta Scope
ACE Beta is an early-access release for testing and integration on supported mainnet and testnet networks. The limitations listed below are all areas of active development. Each will be addressed as ACE progresses toward general availability.
Supported networks
ACE Beta is available on selected mainnet and testnet networks. Additional networks may be added before general availability (GA).
No custom extractors or mappers
ACE Beta provides a library of pre-built, audited policies (allowlists, volume limits, role-based access control, pause controls, and more). You can also register your own custom policies. The following customizations are not available through the platform during Beta:
- Custom extractors: Writing extractors for function signatures beyond the pre-built ERC-20 and ERC-3643 set.
- Custom mappers: Deploying mapper contracts that transform or combine extracted parameters before they reach a policy.
Because custom extractors are not available, the platform supports ERC-20 and ERC-3643 function signatures only. These are the only contract types that get the full managed experience — policy configuration, reporting, and monitoring — through the Platform UI and Coordinator API. If you are building a different type of contract (vault, DEX, lending protocol), making it ACE-compatible could require custom extractors. Support for additional contract types and custom extractors is on the roadmap.
Users can deploy custom extractors or mappers onchain directly, but these fall under the self-deployed contracts limitation below — they will not be visible or manageable through the platform.
Self-deployed contracts are not visible in the platform
Contracts deployed outside the ACE Platform — for example, via Foundry scripts or direct factory calls — will not appear in the UI or API responses.
The ACE Platform only tracks and manages contracts it deploys. Self-deployed PolicyEngines, policies, registries, and extractors function onchain but will not appear in the UI, API responses, or reporting dashboards.
To use the full managed experience (UI dashboards, Reporting API queries, policy management), deploy contracts through the Platform UI or Coordinator API.
Credential data validation is a curated catalog
In addition to attestation-based checks (verifying whether a credential exists), the ACE Platform supports credential data validation — inspecting the contents of a credential's credentialData field for more granular checks. You link a data schema to a credential type, issue credentials that carry data, and attach a Data Validator to a policy's credential source to enforce rules on that data.
Data Validators are a curated catalog maintained by Chainlink, not something organizations deploy themselves. This is by design: curating the available validators and their data schemas ensures no personally identifiable information (PII) are used. The first available validator supports jurisdiction control using ISO 3166-1 alpha-2 country codes; Chainlink may add further validators over time. Bringing your own Data Validator is not offered — this is a permanent design choice, not a Beta limitation.
For the conceptual explanation of attestation-only vs. Credential Data Validator checks, see Cross-Chain Identity — Credential data and privacy.
Signing model is chosen at onboarding
ACE supports two signing models: delegated signing (Chainlink signs and executes transactions on your behalf) and self-signing (you sign operations yourself using the CRE Connect SDK). Your organization chooses its signing model during onboarding.
In both models, you retain full ownership of your contracts through the CRE Connect Wallet. See Signing & Ownership Model for details on how each model works.
Managed offchain risk policies are limited during Beta
ACE Beta provides a managed policy that screens transaction participants with TRM Wallet Screening and delivers approved permits onchain through a managed CRE workflow.
See Off-Chain Policy Execution for a conceptual overview of managed and custom offchain policies.