LIGHTNING-NOTIFICATION-COIN_MOVEMENT(7)

okay so bestie, welcome to LIGHTNING-NOTIFICATION-COIN_MOVEMENT(7) 💅 — aka the coin_movement notification page. this is the manual-page main character energy for when lightningd records a finalized ledger movement, and we are gonna go through every single field, no skipping, periodt. ✨

🌸 NAME 🌸

coin_movement — notification for coin movements 🪙💖

🦋 DESCRIPTION 🦋

the coin_movement notification informs whenever lightningd records a finalized ledger movement. that's the whole vibe check: finalized ledger movement happens, notification says hi. 👋✨

🎀 NOTIFICATION PAYLOAD 🎀

• version (u32) — the coin movement schema version. the version of the vibe, basically 💫
• coin_type (string) — the BIP173 coin type name.
• node_id (pubkey) — the node id that emitted the notification.
• type (string) (one of "channel_mvt", "chain_mvt") — whether this is a channel or chain movement.
• created_index (u64) — 1-based index indicating order this move was created in. (added v25.09)
• account_id (string) — the account identifier for the movement.
• credit_msat (msat) — amount credited to the account.
• debit_msat (msat) — amount debited from the account.
• timestamp (u64) — the UNIX timestamp when the movement was recorded.
• primary_tag (string) (one of "deposit", "withdrawal", "penalty", "channel_open", "channel_close", "delayed_to_us", "htlc_tx", "htlc_timeout", "htlc_fulfill", "to_wallet", "anchor", "to_them", "penalized", "stolen", "ignored", "to_miner", "invoice", "routed", "pushed", "lease_fee", "channel_proposed", "penalty_adj", "journal_entry") — the primary movement tag. (added v25.09)
• tags (array of strings, optional) — deprecated legacy combined tag array, emitted only for deprecated output compatibility. deprecated in v25.09, removed after v26.09:
  • (string, optional) — a legacy movement tag.
• extra_tags (array of strings, optional) — additional movement tags. (added v25.09):
  • (string, optional) — an additional movement tag.
• payment_hash (hash, optional) — the payment hash associated with the movement, if any.
• part_id (u64, optional) — the part id for a multi-part channel payment.
• group_id (u64, optional) — the group id for a multi-part channel payment.
• fees_msat (msat, optional) — the fees associated with a channel movement.
• utxo (outpoint, optional) — the outpoint for a chain movement. (added v25.09)
• peer_id (pubkey, optional) — the peer associated with a chain movement, if any.
• originating_account (string, optional) — the originating account for an external chain movement, if any.
• txid (txid, optional) — deprecated legacy field for the spending transaction id. deprecated in v25.09, removed after v26.09
• spending_txid (txid, optional) — the spending transaction id for a chain movement, if any. (added v25.09)
• utxo_txid (txid, optional) — deprecated legacy field for the outpoint transaction id. deprecated in v25.09, removed after v26.09
• vout (u32, optional) — deprecated legacy field for the outpoint output index. deprecated in v25.09, removed after v26.09
• output_msat (msat, optional) — the output amount for a chain movement.
• output_count (u32, optional) — the number of outputs in the spending transaction, if known.
• blockheight (u32, optional) — the blockheight for a chain movement.

---

and that's the whole payload, bestie — every field accounted for, every deprecated legacy bit still called out, no cap. 🫶💖

footer flex: Core Lightning v26.06.9 · LIGHTNING-NOTIFICATION-COIN_MOVEMENT(7) — mwah 💋✨