Oliver Gugger 4332413fba chainntnfs: remove block info from conf detail copy ... Noticed this while updating to latest master in another project: If there are two notifications for the same output being registered and the first one does _NOT_ request the block to be included, then the second one also will not receive the block, even if it explicitly requests it. This is caused by the block being removed from the original confirmation set instead of a copy (as it is done in NotifyHeight and UpdateConfDetails).		2023-08-02 15:23:14 +02:00
..
bitcoind	bitcoindnotify: fix subtest closure in unit tests	2023-01-19 21:06:23 +08:00
btcd	multi: add golang 1.17 compatible build tags	2021-09-29 17:31:37 -07:00
neutrino	multi: add golang 1.17 compatible build tags	2021-09-29 17:31:37 -07:00
test_interface.go	chainntnfs: remove block info from conf detail copy	2023-08-02 15:23:14 +02:00