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.Documentation Index
Fetch the complete documentation index at: https://musubinetwork.com/llms.txt
Use this file to discover all available pages before exploring further.
What’s net-new for your stack
Three integration points. Everything else in your compliance and custody stack stays where it is.| Seam | What you wire | Why |
|---|---|---|
| Canton participant + Musubi backend | Deploy the Musubi custodian backend in your infrastructure with a Canton Party ID | This is your identity on the settlement network; your signing key here becomes your co-signer on every DvP |
| Order proposal review + quote co-signature | Wire GET /api/v1/orders and the accept endpoints into your ops UI | You review competing market maker quotes and co-sign the chosen one — this is the authorization gate |
| Settlement event → accounting | Subscribe to the SSE stream for SETTLED events and hand transaction_hash to your accounting / compliance archive | One-way fan-out. Musubi emits, your systems consume |
What stays exactly as it is
KYC vendor, sanctions vendor, Travel Rule provider (CODE / VerifyVASP / Notabene / TRUST / Sygna), STR pipeline, compliance archive, whitelist tooling. None of these need Musubi-specific integration. Your custodian is the attester of record on the FXOrder — the underlying checks run where they always have.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
- Sender Custodian
- Receiver Custodian
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.
Compliance
What you attest to on the FXOrder, what stays in your existing stack, whitelist model.
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.