search

decred / dcrdex

The Decred Decentralized Exchange (DEX), powered by atomic-swaps.
Other
184 stars 92 forks source link

mixing: Starting with locked wallet causes problems. #2856

Closed JoeGruffins closed 2 months ago

JoeGruffins commented 3 months ago

Clicking the mix slider for dcr when the wallet is locked errors with:

2024-07-04 05:12:17.666 [DBG] CORE[dcr][SPV]: Starting cspp peer-to-peer funds mixer
2024-07-04 05:12:17.680 [ERR] CORE[dcr][SPV]: Error mixing account: wallet.MixAccount: wallet locked:
    wallet.MixOutput(1212c06d1ee9af17d4e8a09bfafa98e216da23d5eedb0271107f59b0d4344643:0): account with unique passphrase is locked

Restarting bisonw it will error again because the wallet is locked.

The locked wallet also shows this error when trying to turn off mixing:

2024-07-04 05:21:38.643 [TRC] CORE[dcr]: Obtained estimate for 2-conf fee rate, 10
2024-07-04 05:21:38.647 [ERR] CORE[dcr][SPV]: signature error for index 0: wallet.SignTransaction: wallet locked: account with unique passphrase is locked
2024-07-04 05:21:38.647 [ERR] CORE[dcr][SPV]: signature error for index 1: wallet.SignTransaction: wallet locked: account with unique passphrase is locked
2024-07-04 05:21:38.647 [ERR] CORE[dcr][SPV]: signature error for index 2: wallet.SignTransaction: wallet locked: account with unique passphrase is locked
2024-07-04 05:21:38.647 [ERR] CORE[dcr][SPV]: signature error for index 3: wallet.SignTransaction: wallet locked: account with unique passphrase is locked
2024-07-04 05:21:38.647 [ERR] CORE[dcr][SPV]: signature error for index 4: wallet.SignTransaction: wallet locked: account with unique passphrase is locked
2024-07-04 05:21:38.647 [ERR] CORE[dcr][SPV]: signature error for index 5: wallet.SignTransaction: wallet locked: account with unique passphrase is locked
2024-07-04 05:21:38.647 [ERR] CORE[dcr][SPV]: signature error for index 6: wallet.SignTransaction: wallet locked: account with unique passphrase is locked
2024-07-04 05:21:38.647 [ERR] CORE[dcr][SPV]: signature error for index 7: wallet.SignTransaction: wallet locked: account with unique passphrase is locked
2024-07-04 05:21:38.647 [ERR] CORE[dcr][SPV]: signature error for index 8: wallet.SignTransaction: wallet locked: account with unique passphrase is locked
2024-07-04 05:21:38.647 [ERR] CORE[dcr][SPV]: signature error for index 9: wallet.SignTransaction: wallet locked: account with unique passphrase is locked
....
2024-07-04 05:21:38.648 [ERR] CORE[dcr][SPV]: signature error for index 108: wallet.SignTransaction: wallet locked: account with unique passphrase is locked
2024-07-04 05:21:38.648 [ERR] CORE[dcr][SPV]: signature error for index 109: wallet.SignTransaction: wallet locked: account with unique passphrase is locked
2024-07-04 05:21:38.648 [ERR] CORE[dcr][SPV]: signature error for index 110: wallet.SignTransaction: wallet locked: account with unique passphrase is locked
2024-07-04 05:21:38.648 [ERR] CORE[dcr][SPV]: signature error for index 111: wallet.SignTransaction: wallet locked: account with unique passphrase is locked
2024-07-04 05:21:38.648 [ERR] CORE[dcr][SPV]: signature error for index 112: wallet.SignTransaction: wallet locked: account with unique passphrase is locked

I've also seen this when not messing with mixing.

JoeGruffins commented 3 months ago

It's odd the log says it is starting the mixer every block. Did it start a mixer or is it mixing. On testnet so it isn't going very fast...:

2024-07-04 05:52:31.425 [TRC] CORE: Processing tip change for dcr
2024-07-04 05:52:31.425 [DBG] CORE[dcr][SPV]: Starting cspp peer-to-peer funds mixer
ukane-philemon commented 2 months ago

It's odd the log says it is starting the mixer every block. Did it start a mixer or is it mixing. On testnet so it isn't going very fast...:

2024-07-04 05:52:31.425 [TRC] CORE: Processing tip change for dcr
2024-07-04 05:52:31.425 [DBG] CORE[dcr][SPV]: Starting cspp peer-to-peer funds mixer

It starts a new mixing cycle. I guess that log message should say that yeah?

JoeGruffins commented 2 months ago

I've also seen this when not messing with mixing.

This was because a sendAll was triggered on connect.