Minted Protocol · Confidential
Technical Documentation · v4.0

mUSD
Technical Architecture

Canton-Native Institutional Cash and Securities Minting Protocol.

Network
Canton · DAML
Date
April 2026
Version
v4.0

01Protocol Overview

mUSD is a Canton-native stable settlement token built on Digital Asset's DAML smart contract language and the Canton Network's Global Synchronizer. The protocol is designed exclusively for institutional use — securities-backed minting, treasury settlement, and deployment into Canton-native yield vehicles through a structurally separate Institutional Yield Vault.

The architecture is Canton-exclusive by design. There is no external-domain transfer dependency, no public-chain DeFi dependency in the core product, and no blended retail and institutional reserve pools. Every component — collateral validation, minting, yield routing, and payout — operates within Canton's privacy-preserving, formally-verified DAML environment.

02DAML and Canton Foundation

Why DAML

DAML (Digital Asset Modelling Language) is an open-source, purpose-built smart contract language for regulated financial workflows. Unlike EVM-compatible contracts, DAML enforces explicit party authorization at the contract level — no transaction can execute without all required signatories present. This eliminates the single-key-drain attack surface that has caused billions in EVM losses.

Canton Network Infrastructure

Canton is the Global Synchronizer infrastructure connecting sovereign ledgers operated by institutions including Goldman Sachs, BNY, BNP Paribas, DTCC, Euroclear, and HSBC. It processes over $350 billion in repo daily and $6T+ in tokenized asset volume monthly. Minted operates as a Featured Application on Canton, earning Canton Coin rewards based on transaction activity — creating a native revenue stream that scales with network usage.

03Securities Minting Architecture

Securities Minting is the primary institutional entry point. Institutions holding approved Canton-native tokenized securities mint mUSD against that collateral without liquidating their position. The workflow is entirely bilateral and off-chain on the yield side — no open DeFi strategy, no smart contract risk on the yield leg.

Figure 1 — Minting Flow
STEP 1 Pledge securities Institution → Minted STEP 2 Validate & haircut DAML contract STEP 3 mUSD minted 60–85% LTV STEP 4 Ring-fence / route Custody / Vault STEP 5 Liquidity held by inst.

Minting Flow

StepActionParty
1Institution pledges eligible Canton-native securitiesInstitution → Minted
2Minted validates collateral eligibility and applies haircutMinted (DAML contract)
3mUSD minted to institution at approved advance rate (60–85% LTV)Canton Global Synchronizer
4Collateral ring-fenced or routed to Institutional Yield VaultCustody / Asset Control Partner
5Institution holds mUSD as liquid settlement instrumentInstitution

Eligible Collateral (Initial)

AssetExampleAdvance Rate
Tokenized US TreasuriesUSYC on Canton (Hashnote / DRW)80–85%
Tokenized money market fundsFranklin Benji / FOBXX on Canton80–85%
Tokenized sovereign bondsUSDM1 and comparable instruments70–80%
Canton-native structured debtT-RIZE digital bond programme60–75%
Other approved RWAsGovernance-approved on a case-by-case basisCase-by-case

04Token Design

mUSD — Base Settlement Token

mUSD is a non-yield-bearing Canton-native stable settlement token. It is the neutral cash leg — designed to be stable, liquid, and institutionally legible. mUSD does not carry yield exposure. It is the instrument that connects collateral, settlement workflows, and yield access.

Implemented as a CIP-56 compliant DAML contract on the Canton Global Synchronizer. Sub-transaction privacy ensures counterparties see only their own positions.

smUSD Vaults — Institutional Yield Vault

Yield is accessed exclusively through a structurally separate smUSD Vault architecture. Institutions opt in explicitly. The vault receives economic exposure to approved Canton-native yield vehicles — tokenized private credit, structured digital bonds, trade finance instruments — while the base mUSD product remains clean, redemption-oriented, and peg-stable.

LayerInstrumentYield-BearingEconomic Role
Settlement layermUSDNoNeutral cash leg — treasury, settlement, collateral
Yield access layersmUSD VaultYesControlled exposure to Canton-native yield vehicles

05Security and Audit Status

ControlImplementation
Multi-party authorizationNo mint executes without all required DAML signatories
Sub-transaction privacyContract state invisible to non-parties — no front-running
Atomic settlementDAML atomic commit — no partial execution possible
Collateralization enforcement120% enforced on-chain before any mint
Replay protectionPer-instruction participant and contract ID binding
Rate limitingNet mint/burn capped on 24-hour rolling window
Emergency controlsMulti-sig admin with 48-hour timelock
Key managementHSM-backed custody with verified enclave signing
Audit statusTwo public Softstack audits cover the Canton mUSD and Vaults scopes — institutional-grade smart contract review at seed stage.
Test coverage244 test cases, 14/14 Canton audit checks, 27-phase 5N sandbox validation
Sandbox validation27-phase sandbox validation via 5North — all phases passed

06Compliance Infrastructure

Minted is structured around a defined institutional compliance stack prior to launch. Regulated-counterparty roles are mapped in the legal architecture materials across issuer pathway, custody, BD/ATS/TA, validator, AML, and sanctions-screening functions.

Compliance ElementStatus
Broker-Dealer oversightTexture LOI · signed
Transfer Agent registrationTexture LOI · signed
ATS oversightTexture LOI · signed
U.S. issuer pathwayAnchorage pathway identified
Issuer of RecordDefinitive status to verify in diligence
KYC / KYB / Sanctions screeningRequired for all institutional participants
Legal counsel (General Counsel)Wallace Glausi — Securities law, Reg D, BD/TA/ATS
MINTED PROTOCOL · MintedAssociates Corp · Delaware C-Corporation · April 2026 · CONFIDENTIAL — Not for distribution