Skip to main content
When your quote is accepted, Musubi executes an atomic Delivery-vs-Payment (DvP) swap. You deliver USDCx; you receive JPYSC0. Both legs settle in a single transaction — there is never a moment where you’ve delivered one side but not received the other.

How Settlement Works for You

1

Your Quote Wins

The institution selects your quote. Your quote status moves to ACCEPTED. Settlement preparation begins automatically.
2

You Co-Sign the Settlement

Musubi creates a settlement proposal. Four parties must approve before execution:
  1. Network operator (Musubi)
  2. Sender’s custodian (holds the JPYSC0)
  3. You (committing USDCx)
  4. Receiver’s custodian (receiving USDCx)
Your approval is collected automatically through the settlement protocol. No manual action is required if your system is connected.
3

Atomic DvP Executes

All four legs execute in a single transaction:
LegMovementYour Role
1JPYSC0: Sender’s custodian -> Musubi
2USDCx: You -> MusubiYou deliver
3USDCx: Musubi -> Receiver’s custodian
4JPYSC0: Musubi -> YouYou receive
All four succeed atomically, or all four roll back. Settlement takes ~4 seconds.
4

Settlement Confirmation

You receive a settlement record with a single transaction_hash covering all four legs. This is your definitive proof of execution.
How this differs from CEX/DEX settlement: On a CEX, settlement is internal ledger entries — you trust the exchange. On a DEX, settlement is atomic within one smart contract call — you trust the code. On Musubi, settlement is atomic across four independent parties via Canton DvP — no exchange custody risk, no smart contract risk. Your assets stay in your own custody until the atomic swap executes.

Your Settlement Record

After settlement, you can retrieve the details:
FieldDescriptionExample
intent_idOrder referenceUUID
source_currencyWhat the sender exchangedJPYSC0
target_amountSender’s amount"10000000"
target_currencyWhat you deliveredUSDCx
source_amount_actualFinal delivered amount"11200000"
fx_rateExecuted rate"112.0"
mm_delivered_target_amountUSDCx you delivered"11200000"
mm_delivered_target_amountJPYSC0 you received"10000000"
transaction_hashCryptographic settlement proofHex string
settled_atSettlement timestampISO 8601
P&L calculation: Your profit is the spread between your offered rate and your cost of acquiring USDCx. The settlement record gives you exact amounts for reconciliation.

Risk Profile

RiskStatusWhy
Counterparty riskEliminatedAtomic DvP — both legs or neither
Settlement riskEliminatedSingle transaction, no intermediate state
Herstatt riskEliminatedNo time gap between legs
Identity exposureNoneAnonymized RFQs, no sender/receiver identity even post-settlement
Pre-funding requirementNoneNo intraday liquidity commitment window
Failed settlementFull rollbackIf any leg fails, all four revert. Your USDCx stays in your account.
The only risk you carry is market risk during the validity window of your quote. If the market moves against you between quoting and settlement (~15 seconds total), your committed rate stands. Manage this by setting appropriate valid_until windows.

Liquidity Management

What You Need

Deposit USDCx with sufficient balance to cover your expected quoting activity. Your USDCx is committed only when a quote is accepted and settlement executes — pending quotes do not lock funds.

Monitoring

Track your performance via the dashboard:
MetricDescription
quotes_submittedTotal quotes you’ve submitted
quotes_acceptedQuotes that won
quotes_rejectedQuotes where another MM won
quotes_expiredQuotes that expired unselected
win_rateAccepted / submitted ratio
total_source_tradedTotal JPYSC0 received from won swaps
total_target_tradedTotal USDCx delivered in won swaps
active_quote_requestsCurrently quotable requests

Liquidity Strategy

  • Deposit sizing: Based on your expected daily volume and win rate
  • Rate management: Tighter spreads win more flow but reduce per-trade P&L
  • Validity tuning: Shorter valid_until reduces market risk; longer windows increase win probability
  • Volume monitoring: Track active_quote_requests to gauge current demand