cln/plugins/bkpr
Rusty Russell 16819f345d lightningd: make notifications from plugins just like native ones.
Rather than forcing them to wrap their parameters in a "payload"
sub-object, copy in params directly.  We include the "origin" field
one level up, if they care.

The next patch restores compatibility for the one place we currently use
them, which is the pay plugin.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Changelog-Deprecated: pyln-client: plugin custom notifications origins and payload (use parameters directly)
2025-08-18 10:01:07 +09:30
..
test lightningd: have onchaind inform us when to make a channel penalty_adj. 2025-08-14 19:49:09 +09:30
account.c common: put "external" and "wallet" strings, and test functions into common/coin_mvt.h 2025-08-14 19:49:09 +09:30
account.h common: put "external" and "wallet" strings, and test functions into common/coin_mvt.h 2025-08-14 19:49:09 +09:30
account_entry.c bkpr: track channel rebalances, display in listincome 2022-08-09 11:57:18 +09:30
account_entry.h bkpr: track channel rebalances, display in listincome 2022-08-09 11:57:18 +09:30
bookkeeper.c lightningd: make notifications from plugins just like native ones. 2025-08-18 10:01:07 +09:30
chain_event.c bkpr: remove different currency support. 2025-08-14 19:49:09 +09:30
chain_event.h bkpr: remove different currency support. 2025-08-14 19:49:09 +09:30
channel_event.c bkpr: remove different currency support. 2025-08-14 19:49:09 +09:30
channel_event.h bkpr: remove different currency support. 2025-08-14 19:49:09 +09:30
channelsapy.c common: put "external" and "wallet" strings, and test functions into common/coin_mvt.h 2025-08-14 19:49:09 +09:30
channelsapy.h bkpr: command to calculate some APYs/stats on channel routing fees 2022-07-28 12:08:18 +09:30
db.c common: remove "ignored" tag. 2025-08-14 19:49:09 +09:30
db.h bkpr: now that we're not doing empty acct logging, we dont need this bool 2024-01-29 10:05:03 +10:30
incomestmt.c bkpr: remove different currency support. 2025-08-14 19:49:09 +09:30
incomestmt.h bkpr: remove different currency support. 2025-08-14 19:49:09 +09:30
Makefile wallet: add channel_type field to db. 2023-04-10 17:26:47 +09:30
onchain_fee.c bkpr: remove different currency support. 2025-08-14 19:49:09 +09:30
onchain_fee.h bkpr: remove different currency support. 2025-08-14 19:49:09 +09:30
README.md chore: fix some minor issues 2025-08-15 11:05:51 +09:30
recorder.c lightningd: have onchaind inform us when to make a channel penalty_adj. 2025-08-14 19:49:09 +09:30
recorder.h bkpr: remove different currency support. 2025-08-14 19:49:09 +09:30

The bookkeeper keeps track of coins moving through your Lightning node.

See the doc/PLUGINS.md#coin_movement section on the message that CLN emits for us to process.

// FIXME: add more detailed documenation for how bookkeeper works.

3rd Party Coin Movements

Bookeeper ingests 3rd party plugin notifications about on-chain movements that it should watch.

This allows for us to account for non-internal on-chain wallets in the single place, making bookkeeper your single source of truth for bitcoin for an organization or node-operator.

As a plugin writer, if you want to emit onchain events that the bookkeeper should track, you should emit an event with the following format:

{
	"utxo_deposit": {
		"account": "nifty's secret stash",
		"transfer_from: null,
		"outpoint": xxxx:x,
		"amount_msat": "10000sat",
		"coin_type": "bc",
		"timestamp": xxxx,
		"blockheight": xxx,
	}
}
{
	"utxo_spend": {
		"account": "nifty's secret stash",
		"outpoint": xxxx:x,
		"spending_txid": xxxx,
		"amount_msat": "10000sat",
		"coin_type": "bc",
		"timestamp": xxxx,
		"blockheight": xxx,
	}
}

Withdrawing money (sending to a external account)

Sending money to an external account is a bit unintuitive in the UTXO model that we're using to track coin moves; technically a send to an external account is a "deposit" to 3rd party's UTXO.

To account for these, bookkeeper expects to receive a utxo_deposit event for the creation of an output to a 3rd party. It's assumed that you'll issue these at transaction creation time, and that they won't be final until we receive notice of spend of the inputs in the tx that created them.

To notify that money is being sent to a 3rd party output, here's the event we'd expect.

The two keys here are the following:

  • The account is external. This is a special account in bookkeeper and used for tracking external deposits (aka sends)
  • The transfer_from field is set to the name of the account that is sending out the money.
{
	"utxo_deposit": {
		"account": "external",
		"transfer_from": "nifty's secret stash",
		"outpoint": xxxx:x,
		"amount_msat": "10000sat",
		"coin_type": "bc",
		"timestamp": xxxx,
		"blockheight": xxx,
	}
}

List of todos

List of things to check/work on, as a todo list.

  • Transfers btw a 3rd party wallet and the internal CLN wallet? These should be registered as internal transfers and not show up in listincome