QUICKSTART/ 04 · SEND ASSETS

Send assets

Once a profile is active, you can send a transfer with a single command.

1-of-1 single-signer

bash

cws transaction send alice::1220aaaa 1.25 amulet::<registrar> \
  --description "agent test"

The party id is derived from the active profile's keystore — no party argument needed. The cws-api submits the transaction directly upon signing.

Multisig

Route through the queue. Threshold signers approve; the submit auto-fires once the threshold is met.

bash

# Propose a transfer (prepare + queue + your signature)
cws multisig queue send treasury::1220abcd alice::1220aaaa 1.25 amulet::<registrar>

# Approve a queued transaction (as another signer)
cws multisig transaction approve <transactionId>

# Inspect what's pending across every multisig you participate in
cws multisig pending

# Re-submit a fully-signed transaction (if auto-submit failed)
cws multisig transaction submit <transactionId>

Inspect

bash

# Holdings for a party
cws holdings list treasury::1220abcd

# Instruments available on the network
cws instruments list

# Multisig details
cws multisig show treasury::1220abcd

# Transaction history filtered by status
cws multisig transaction history --multisig treasury::1220abcd --status confirmed

Each mutation triggers the keystore unlock + prepare/verify/sign flow. The CLI prints the transaction id and the prepared-submission hash before signing — review them before approving on mainnet.

Issue assetsMint, burn, and onboard providers via DA Utility.