Browse Source
Prior to this commit, a lock of one wallet followed by an unlock of another, or an unlock of a new wallet, overriding the old one, if it occurred during a running taker-side coinjoin, would not reset the coinjoin_state to CJ_NOT_RUNNING, resulting in an inability of the newly loaded wallet to function correctly. After this commit, all subservices, including the quasi-service of taker-side coinjoin, are fully shut down whenever a wallet is locked, or a new wallet is unlocked. This may be suboptimal (see TODO) but is logical for now. The main effect is to ensure that a new wallet will always start in the correct coinjoin state (CJ_NOT_RUNNING). Also worth noting, a running Taker will have its abort parameter set to True on the wallet lock event, meaning that it will not proceed to the next step on the next asynchronous message coming from counterparties.master
1 changed files with 33 additions and 8 deletions
Loading…
Reference in new issue