cln/plugins/bkpr
Rusty Russell e28443ed40 bkpr: pass bkpr struct into all functions in recorder.c.
We want to access it in stmt2chain_event, so plumb it through.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2025-08-19 13:37:50 +09:30
..
test bkpr: pass bkpr struct into all functions in recorder.c. 2025-08-19 13:37:50 +09:30
account.c ]bkpr: save accounts in the datastore instead of database. 2025-08-19 13:37:50 +09:30
account.h ]bkpr: save accounts in the datastore instead of database. 2025-08-19 13:37:50 +09:30
account_entry.c bkpr: strings in structures should be const. 2025-08-19 13:37:50 +09:30
account_entry.h bkpr: strings in structures should be const. 2025-08-19 13:37:50 +09:30
bookkeeper.c bkpr: pass bkpr struct into all functions in recorder.c. 2025-08-19 13:37:50 +09:30
bookkeeper.h bkpr: infrastructure to keep rebalance pairs in mem & datastore. 2025-08-19 13:37:50 +09:30
chain_event.c bkpr: use the in-memory event descriptions, not the database ones. 2025-08-19 13:37:50 +09:30
chain_event.h bookkeeper: use the in-memory rebalances. 2025-08-19 13:37:50 +09:30
channel_event.c bookkeeper: use the in-memory rebalances. 2025-08-19 13:37:50 +09:30
channel_event.h bookkeeper: use the in-memory rebalances. 2025-08-19 13:37:50 +09:30
channelsapy.c bkpr: pass bkpr struct into all functions in recorder.c. 2025-08-19 13:37:50 +09:30
channelsapy.h bkpr: cache accounts table in memory. 2025-08-19 13:37:50 +09:30
db.c bkpr: remove onchain_fees table. 2025-08-19 13:37:50 +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
descriptions.c bookkeeper: infrastructure to keep descriptions (annotations) in mem and datastore. 2025-08-19 13:37:50 +09:30
descriptions.h bookkeeper: infrastructure to keep descriptions (annotations) in mem and datastore. 2025-08-19 13:37:50 +09:30
incomestmt.c bkpr: pass bkpr struct into all functions in recorder.c. 2025-08-19 13:37:50 +09:30
incomestmt.h bkpr: cache accounts table in memory. 2025-08-19 13:37:50 +09:30
Makefile bkpr: infrastructure to keep rebalance pairs in mem & datastore. 2025-08-19 13:37:50 +09:30
onchain_fee.c bkpr: pass bkpr struct into all functions in recorder.c. 2025-08-19 13:37:50 +09:30
onchain_fee.h bkpr: save and restore onchain_fees from the datastore, not the db. 2025-08-19 13:37:50 +09:30
README.md chore: fix some minor issues 2025-08-15 11:05:51 +09:30
rebalances.c bkpr: infrastructure to keep rebalance pairs in mem & datastore. 2025-08-19 13:37:50 +09:30
rebalances.h bkpr: infrastructure to keep rebalance pairs in mem & datastore. 2025-08-19 13:37:50 +09:30
recorder.c bkpr: pass bkpr struct into all functions in recorder.c. 2025-08-19 13:37:50 +09:30
recorder.h bkpr: pass bkpr struct into all functions in recorder.c. 2025-08-19 13:37:50 +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