Before You Start
These command groups require an active and unlocked node:Units on this page.
wallet amounts are satoshis, and asset and payment amounts are raw integer units, where the asset’s precision decides the conversion — check it with kaleido asset metadata <asset-id>. Display amounts such as --from-amount 0.001 appear only on market and swap commands.BTC Wallet
Common wallet commands
Examples
Colored UTXOs
RGB assignments live on specific Bitcoin outputs, so the node needs spare UTXOs before it can issue, receive, or send an asset:Backup and restore
backup and restore both accept --password, -p. Restore overwrites the current node data, so use it deliberately.
RGB Assets
Core asset commands
Issue new assets
Theissue subgroup supports the three supported schemas:
niafor fixed-supply fungible assetscfafor collectible fungible assetsudafor unique digital assets
--precision for the number of decimal places, and --supply is expressed in the smallest raw unit. cfa and uda also accept --description.
Asset invoice and send examples
asset send options:
--fee-rate--min-confirmations--donation--transport-endpoint--witness-amount-satand--witness-blinding--skip-sync
Batch sends
asset send-batch takes a path to a JSON file describing the recipients, not inline flags:
Keeping transfers moving
refresh to advance pending transfers and sync to resynchronise the RGB wallet. Only when a transfer is genuinely dead should you release its allocations with kaleido asset fail-transfers, which accepts --batch-idx to target one batch, --no-asset-only to limit it to transfers with no asset, and --skip-sync.
Lightning And RGB+LN Payments
Payment commands
Examples
--amount-msat. For RGB+LN payments, supply --asset-id and --asset-amount.
Working Style
- Use
--jsonwhen you need machine-readable responses. - Use
--skip-synconly when stale wallet or transfer state is acceptable. - Create extra UTXOs before heavy RGB activity to avoid running out of usable colored outputs.