Three patterns. Three VMs. One model.
Every regulated asset Boli ships collapses to one of three Daml patterns, settles on Canton, and projects onto EVM and Solana through burn-and-mint — one asset reachable on every chain under a single global reserve cap, not a canonical copy with disconnected wrappers. Compliance is code the licensed parties configure and own.
Holdings transfer atomically against cash via Splice Token Standard V1 AllocationV1. Compliance modules gate every transfer with canTransfer preflight. Used by asset managers, fund managers, banks, environmental markets.
The state register stays authoritative. Boli mirrors entries on-chain so they can compose with finance and identity primitives. Used by sovereigns, land registries, transport authorities.
W3C verifiable credentials issued under eIDAS-2 patterns. Bound to TDIP DIDs. Used by identity issuers, KYC providers, environmental MRV bodies.
One asset, one cap, every chain.
Canton settles. Atomic delivery-vs-payment with sub-transaction privacy and instant finality — the institutional settlement rail.
EVM and Solana carry distribution and liquidity. The asset projects out via burn-and-mint (ERC-7802) so it composes with stablecoins, custody, DeFi, and wallets — never a lock-and-wrap copy.
One global cap holds across all of them: Σ circulating across every chain ≤ one attested reserve, re-checked on-chain at the mint, not trusted from anyone's books.
Compliance is the licensed party's code.
Each asset comes with a pack — a set of compliance modules (jurisdiction, holder limits, lockups, sanctions, accreditation) the issuer or transfer agent configures. The pack runs at the chain level on every transfer; failures surface as preflight rejections with reasons.
Boli ships the pack catalog and the engine. The licensed party decides the policy.