Oliver Gugger fa05add3b7 account+rpcserver: handle consecutive batch confirmations ... This commit allows the account manager to handle the situation where an account participates in multiple consecutive batches that might still be in the mempool. Once the first batch confirms, the database state of the account might differ from the batch key used in that earlier batch. We need to cancel old spend and conf watches and only watch the latest batch for confirmation. While an account is in this pending batch state, no user modification like deposits or withdrawals are allowed so it's safe to just jump to the latest batch and wait for confirmations on that one.		2020-08-17 13:53:04 +02:00
..
log.go	watcher: implement subsystem to watch accounts on-chain	2020-01-08 13:01:38 -08:00
mock_test.go	multi: update aperture, use lndclient, remove loop	2020-08-11 19:41:01 +02:00
watcher.go	account+rpcserver: handle consecutive batch confirmations	2020-08-17 13:53:04 +02:00
watcher_test.go	multi: use btcec.PublicKey instead of [33]byte	2020-01-24 13:45:48 -08:00