Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Node actions in messages

message list reports each node message’s protocol action verbatim (kebab-case). The full list is in the protocol book; these are the ones this book refers to, with how the CLI presents them.

actionSent whennext_stepPayload kind
new-orderAn order was created for you; for range orders, the child order announced to your next key—order
pay-bond-invoiceA bonded node wants your bondpay_bond_invoicepayment_request
pay-invoiceYou are the seller: lock the satspay_hold_invoicepayment_request
add-invoiceYou are the buyer: the node needs your invoiceadd_invoiceorder
add-bond-invoiceA counterparty bond was slashed; send a payout invoiceadd_bond_invoicebond_payout_request
waiting-seller-to-payYour invoice is in; the seller has to pay—none
hold-invoice-payment-acceptedThe seller locked the sats; the trade is active—(varies)
fiat-sent-okThe buyer’s fiat-sent was accepted—peer
hold-invoice-payment-settled, releasedThe seller’s release went through—(varies)
canceledThe order was canceled—none
cooperative-cancel-initiated-by-youYou started a cooperative cancel—(varies)
cooperative-cancel-acceptedThe cooperative cancel completed—(varies)
invoice-updatedA replacement buyer invoice was stored—(varies)
rate-receivedYour rating was recorded—other (rating_user)
cant-doThe node refused something—cant_do

Only the four next_step values ask you to act. Everything else is information; use order info for the authoritative status.

The same action names appear in replies to the write commands, where the CLI maps them to result values (see order fiat-sent and order add-invoice).