Skip to main content
Your Party ID key is the co-signer key for DvP settlement — analogous to a multisig key, but with DAML choice-level granularity. Protect it with the same controls you apply to any key that authorizes asset movements.

Your Signing Authority

  • Co-signature on quote acceptance — no assets move without your approval
  • Settlement approval — you are one of four required signatories on the atomic DvP
  • Veto power — you can reject order proposals or refuse to co-sign quotes
Unlike EVM multisig where any N-of-M signers are interchangeable, your Canton Party ID is a named role. The settlement protocol requires specifically your signature — it cannot be substituted by another custodian or any other party.

Canton Privacy vs Public Chain Transparency

If you’re used to EVM or Bitcoin, where every transaction is publicly visible, Canton’s privacy model is fundamentally different:
This means you cannot independently verify other participants’ balances or transaction history by scanning a public ledger. Trust in counterparty solvency comes from the atomic DvP guarantee (both legs or neither), not from on-chain transparency.

Where the comparison stops: metadata

The privacy above is payload privacy. What a settlement contains — amounts, currencies, the FX rate, the order terms — reaches only entitled parties, and that holds. What it does not cover is the settlement’s own confirmation metadata. To collect the four required confirmations, the network’s mediator handles the set of parties participating in each transaction, along with its timing. Operators of that infrastructure can therefore see that a given institution settled with a given counterparty, through given custodians, at a given moment — without seeing a single amount or rate. On the public DevNet, a third-party network explorer serves that metadata without authentication, which makes the relationship graph readable by an outside observer today. The practical consequence is the one an EVM comparison table tends to obscure: Musubi hides what you traded, not that you traded. If the existence of a counterparty relationship is itself sensitive to you, raise it during onboarding. Establishing who holds this metadata on production networks — and whether any of them republish it — is an open pre-launch item, tracked and not yet closed.

Authentication

In production, JWT issuance integrates with your organization’s identity provider.

Data Isolation

Your backend and database run in your infrastructure: No other participant can access your backend or database. All cross-party communication flows through the settlement network protocol.

What You See

What You Control