Skip to main content

Managing a Multisig Address

A multisig (multi-signature) address requires M signatures from a set of N defined public keys before funds can be spent. This is useful for shared treasuries, escrow, team funds, or any situation where a single key should not be able to move funds unilaterally.

This guide covers setting up a multisig address and the full workflow for spending from it.

Prerequisites​

  • A running, synced node-daemon
  • wallet-cli connected to the node (one instance per participant, or a coordinator collecting signatures)
  • The public keys of all participants

Concepts​

M-of-N multisig: A multisig address defined by N public keys where at least M of them must sign a transaction for it to be valid. For example, a 2-of-3 address requires any 2 of the 3 keyholders to sign.

PartiallySignedTransaction (PST): A transaction that has been composed but not yet fully signed. It is passed between participants as a hex string so each can add their signature. Once M signatures are collected the transaction can be broadcast.

Standalone address: Multisig addresses are tracked as standalone addresses in the wallet, they are watched for incoming funds but not derived from the wallet's seed phrase. Each participant must add the same multisig address to their own wallet.


Part 1: Setting Up the Multisig Address​

Step 1: Collect public keys from all participants​

Each participant must reveal the public key for the address they will use to sign. In each participant's wallet:

address reveal-public-key --format hex <address>

This returns the raw hex public key for that address. Collect these from all N participants out of band (e.g. shared securely over a messaging channel).

Step 2: Create the multisig address​

In any wallet (typically the coordinator's), register the multisig address:

address standalone add-multisig <MIN_REQUIRED_SIGNATURES> <pubkey1> <pubkey2> ... <pubkeyN>

Example, a 2-of-3 multisig with an optional label:

address standalone add-multisig --label "Treasury" 2 <pubkey1> <pubkey2> <pubkey3>

The command returns the multisig address. Share this address with all participants.

Step 3: Each participant adds the same address​

Every participant who may need to sign transactions must also add the multisig address to their wallet:

address standalone add-multisig --no-rescan true 2 <pubkey1> <pubkey2> <pubkey3>

Using --no-rescan true skips a full blockchain rescan if the address has no existing history yet. Omit it (or use false) if the address may have already received funds.

Step 4: Verify the address is tracked​

address standalone list

To inspect the full details (participants, required signatures):

address standalone details <multisig_address>

Part 2: Receiving Funds​

Send funds to the multisig address like any other address, the sender just uses send or token send with the multisig address as the destination.

To check the multisig address balance and available UTXOs:

address standalone utxos

Part 3: Spending from the Multisig Address​

Spending requires M participants to each sign a PartiallySignedTransaction. The typical flow is: compose → sign (round-robin) → broadcast.

Step 1: Compose the transaction​

The coordinator composes a transaction spending from the multisig UTXO:

transaction compose --utxos <utxo> transfer(<destination_address>,<amount>)

The UTXO identifier comes from address standalone utxos output, in the format tx(<txid>,<index>) or block(<block_id>,<index>).

This returns a hex-encoded PartiallySignedTransaction with no signatures yet.

Step 2: First participant signs​

Pass the hex to the first signer's wallet:

transaction sign <hex>

The wallet adds its signature and returns a new hex string with one signature applied. If this wallet holds enough keys to fully sign the transaction (e.g. it controls 2 of 2 keys in a 2-of-2), it is complete after this step.

Step 3: Additional participants sign (if needed)​

Pass the updated hex to the next signer:

transaction sign <hex_from_previous_signer>

Repeat until M signatures have been collected. Each signer outputs an updated hex, always pass the latest hex to the next participant.

Step 4: Broadcast the fully signed transaction​

Once M signatures are present, broadcast from any wallet connected to the node:

node submit-transaction <fully_signed_hex>

Worked Example: 2-of-3 Treasury​

Setup (done once):

# Each participant reveals their public key
address reveal-public-key --format hex <my_address>
# → <pubkeyA>, <pubkeyB>, <pubkeyC> collected from each participant

# Coordinator registers the multisig
address standalone add-multisig --label "Treasury 2-of-3" 2 <pubkeyA> <pubkeyB> <pubkeyC>
# → returns: <multisig_address>

# Participants B and C also add it
address standalone add-multisig --no-rescan true 2 <pubkeyA> <pubkeyB> <pubkeyC>

Spending (each time funds need to move):

# Coordinator lists UTXOs and composes a transaction
address standalone utxos
transaction compose --utxos tx(<txid>,0) transfer(<destination_address>,500)
# → <pst_hex_v0> (0 signatures)

# Participant A signs
transaction sign <pst_hex_v0>
# → <pst_hex_v1> (1 signature)

# Participant B signs
transaction sign <pst_hex_v1>
# → <pst_hex_v2> (2 signatures: threshold reached)

# Coordinator broadcasts
node submit-transaction <pst_hex_v2>

Managing the Address​

Rename or remove the label​

# Rename
address standalone rename-label --label "New Label" <multisig_address>

# Remove label
address standalone rename-label <multisig_address>

Quick Reference​

TaskCommand
Get your public keyaddress reveal-public-key --format hex <address>
Create multisig addressaddress standalone add-multisig <M> <pubkey1> ... <pubkeyN>
List standalone addressesaddress standalone list
Inspect multisig detailsaddress standalone details <address>
View multisig UTXOsaddress standalone utxos
Compose spend transactiontransaction compose --utxos <utxo> transfer(<address>,<amount>)
Sign transactiontransaction sign <hex>
Broadcast transactionnode submit-transaction <hex>
Rename labeladdress standalone rename-label --label <label> <address>