core-lightning/plugins/bkpr
niftynei 7b6956e4f9 bkpr: annotate an account with the block at which it's been resolved
Due to the way that onchain channel closes work, there is often a delay
between when the funding output is spent and the channel is considered
'closed'.

Once *every* downstream utxo of a channel has landed on chain, we
annotate the account with the resolving blockheight.

This gives us some insight into whether or not the chain fees etc of a
channel are going to update further and allows for a natural marker to
prune data (at a later date)
2022-07-28 12:08:18 +09:30
..
test bkpr: update tests for wallet/external onchain fees 2022-07-28 12:08:18 +09:30
account.c bkpr: if we're missing info about an account, add in journal entry 2022-07-28 12:08:18 +09:30
account.h bkpr: if we're missing info about an account, add in journal entry 2022-07-28 12:08:18 +09:30
account_entry.c bkpr: use tags not str for tag originations 2022-07-28 12:08:18 +09:30
account_entry.h bkpr: use tags not str for tag originations 2022-07-28 12:08:18 +09:30
bookkeeper.c bkpr: annotate an account with the block at which it's been resolved 2022-07-28 12:08:18 +09:30
chain_event.h bkpr: parse the 'originating_account' field, save to event 2022-07-28 12:08:18 +09:30
channel_event.c bkpr: if we're missing info about an account, add in journal entry 2022-07-28 12:08:18 +09:30
channel_event.h bkpr: if we're missing info about an account, add in journal entry 2022-07-28 12:08:18 +09:30
db.c bkpr: parse the 'originating_account' field, save to event 2022-07-28 12:08:18 +09:30
db.h bkpr: first attempt at database code for accounting 2022-07-28 12:08:18 +09:30
Makefile bkpr: use tags not str for tag originations 2022-07-28 12:08:18 +09:30
onchain_fee.h bkpr: put the account name on the event 2022-07-28 12:08:18 +09:30
recorder.c bkpr: annotate an account with the block at which it's been resolved 2022-07-28 12:08:18 +09:30
recorder.h bkpr: annotate an account with the block at which it's been resolved 2022-07-28 12:08:18 +09:30