[bisq-network/bisq] Add rpc wallet protection endpoints (#4214)

Chris Beams notifications at github.com
Fri May 8 09:42:37 UTC 2020


@ghubstan, I just ran into the following scenario when testing everything locally:

1. spin up a daemon against a new data directory, e.g: `./bisq-daemon --appDataDir=/tmp/newbisqdatadir --apiPassword=xyz
1. run `./bisq-cli --password=xyz getbalance` until you get a valid response of `0.00000000`
1. set a wallet password with `./bisq-cli --password=xyz setwalletpassword foo`
1. notice that `./bisq-cli --password=xyz getbalance` errors out as expected
1. unlock the wallet with `./bisq-cli --password=xyz unlockwallet foo 60`
1. notice that `./bisq-cli --password=xyz getbalance` returns 0.00000000 once again
1. lock the wallet with `./bisq-cli --password=xyz lockwallet`
1. notice that `./bisq-cli --password=xyz getbalance` errors out as expected
1. unlock the wallet once again with `./bisq-cli --password=xyz unlockwallet foo 60`
1. notice that `./bisq-cli --password=xyz getbalance` does NOT return 0.00000000 as expected, but rather fails with a "balance is not yet available message"
1. notice that no matter how long you wait, the command above always fails with the same message.

It appears there is no way to recover from this state via the cli, and that the only way out is to spin up a fresh data directory. Stopping and starting the server makes no difference either.


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/bisq/pull/4214#issuecomment-625733825
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20200508/22b4d3f2/attachment.html>


More information about the bisq-github mailing list