Boli is an operating layer on the Canton Network for regulated tokenized assets. It ships three Daml asset patterns — Tradeable, Registry-mirror, Credential — sufficient to represent every regulated asset class encountered in production: securities, funds, sukuk, real-estate share classes, environmental credits, sovereign registries, identity attestations, and central-bank instruments. A chain-level compliance-pack engine, multi-VM mirroring, the TDIP identity bridge, and agentic asset operations under DID-bound mandates round out the platform. The whitepaper sets out the architectural rationale, the three patterns, the regulatory boundary, and the specifications referenced by the Boli Standards Proposals (BSPs).
Published by Boli Association (Switzerland). Licensed CC BY 4.0. Maintained alongside the Boli Standards Proposals (BSPs) the whitepaper references.
Why Boli
Tokenization in 2026 is no longer a question of can it be done. It is a question of which legal entity, under which jurisdiction, carries which license. Boli ships the operating layer so that question can be answered cleanly: the tokenization runtime and rails are neutral; the licensed parties (issuers, transfer agents, registries, banks, sovereigns) own every regulated step.
Three patterns, every audience
Asset and fund managers, banks, sovereigns, citizens, environmental markets, corporates, identity issuers, central banks. Eight audiences. Their assets collapse to three Daml patterns — Tradeable, Registry-mirror, Credential — which Boli ships as base packages and extends through compliance packs.
Three chains, three jobs
Canton settles. EVM is the interoperability surface. Solana is the performance surface. The asset model is canonical on Canton; EVM and Solana representations are mirrors. There is no "chain picker" in the Boli operator UI because there is nothing to pick — the institutional rail is Canton, and the mirrors are present when distribution requires them.
Settlement: AllocationV1, not escrow
Boli does not run an escrow. Atomic delivery-vs-payment uses the Splice Token Standard V1 AllocationV1 primitive: AllocationRequest → AllocationFactory_Allocate → Allocation_ExecuteTransfer. Both legs settle in a single Daml transaction; failure of either leg unwinds the whole settlement.
Compliance is code the licensed party owns
Each asset comes with a pack — a set of compliance modules configured by the issuer or transfer agent. The pack runs at the chain level on every transfer. Boli ships the pack catalog (Reg D 506(c), Reg S, Sukuk Ijara, Land Registry Torrens, eIDAS-2 High, etc.) and the engine; the licensed party decides the policy.
Identity: TDIP, not federated
Identities are anchored by Tenzro DIDs (did:tenzro:human:{uuid}), minted from Boli's internal UUIDs — never from a federated profile field. MPC wallets across EVM, Solana, and Canton are auto- provisioned at sign-in. Boli persists the DID and the wallet addresses; Boli does not persist long-lived bearer tokens.
Agentic asset operations
Real institutional assets need to be continuously operated — reconciled, monitored, verified, reported, retired. Boli runs that operational layer on Tenzro's agentic runtime: autonomous workflow execution under DID-bound, on-chain mandates; verifiable in TEE; settled on Canton. Authority graphs and revocation trees — not API tokens — govern what an autonomous system can do.
Entities and governance
Boli is deployed on Tenzro's Canton validator node. The initial operating company is based in the UAE. The Boli Association (Switzerland) is a non-profit that supports research and ecosystem design around the platform and the standards (BSPs) it implements. The Boli Foundation will be established ahead of $BOLI and will govern the token and ecosystem treasury. Operating company and Foundation are legally and operationally separate.