Compliance stays on the token. On every chain.
Most RWA stacks gate the wrapper at issuance. When the asset crosses into open DeFi, the gate falls off. Onchain Bridges enforces the same policy on every transfer, on EVM and non-EVM alike.
Most RWA stacks gate the wrapper at issuance. When the asset crosses into open DeFi, the gate falls off. Onchain Bridges enforces the same policy on every transfer, on EVM and non-EVM alike.
Compliance architecture
Compliance is enforced in the token own transfer path, on every chain. Three pieces do the work.
Tokens call the policy engine on every transfer. Every movement is routed through its policies; there is no path around it.
Only admitted addresses can hold or move the asset. The issuer or admin role adds and removes addresses on-chain.
Pausing the policy halts all transfers instantly. On chains with tight gas budgets we deploy a combined ComplianceCheck.
Four virtual-machine families
Five EVM chains use Chainlink ACE. Solana uses a Token-2022 transfer hook. Stellar and Stacks use native modules per chain. If the address is not allowed, the transfer reverts on-chain.
Chainlink ACE ComplianceCheck attached to every OB-issued token. Identity validator, allowlist policy, and max-balance concentration cap run on every transfer.
SPL Token-2022 transfer hooks. The hook consults an on-chain compliance registry mirrored from EVM allowlist state via a Chainlink CRE workflow.
Lock-and-mint with admission checked at the mint. Non-admitted mints revert on the Soroban side, not deferred to an off-chain check.
A Tier-2 asset registry gates each mint. Because Clarity is decidable, we can reason statically that no token movement bypasses the guard.
Portable identity
One KYC verification issues an on-chain credential valid across all five supported EVM chains. Non-EVM chains use native compliance modules per chain, so there is no single portable identity spanning EVM and non-EVM; the guarantee holds on each chain own terms.