Skip to main content
You already custody stablecoins: key management, whitelisting, multisig, on-chain settlement. Musubi keeps all of that. What it adds is an active role in a multi-party FX settlement workflow — your cryptographic co-signature is one of four required for every atomic DvP.

​
What’s net-new for your stack

Three integration points. Everything else in your custody stack stays where it is. See Integration Guide for the architecture and onboarding.
For how Canton’s custody and transfer model differs from EVM/UTXO at the protocol level, see Ethereum vs Musubi. The Canton Holding model (sole-signatory, no allowance pattern) is covered in Settlement & Safekeeping.

​
Two Distinct Roles

You’re not just holding and releasing assets — you’re an active participant in an FX workflow.
  • See order proposals from your institutional clients and accept / reject them
  • Review competing market maker quotes — unusual for a custodian, but you’re the authorization gate for best execution
  • Co-sign the best quote alongside the institution (dual authorization)
  • Your co-signature is one of four required for the atomic DvP settlement

​
Guide Structure

Authorization Workflow

How multi-party DvP co-signing works, quote review, and how this differs from standard multisig.

Settlement & Safekeeping

Atomic DvP mechanics, Canton Holding model vs ERC-20, asset movements, reconciliation.

Security

Signing authority, Canton privacy vs public chain transparency, data isolation.

Integration

Deploy + Console + Audit Exports, with a programmatic access path for custodians who need it.

API Reference

Endpoints, accept quote examples, SSE events, order lifecycle.