Open minioff opened 2 years ago
What kind of wallet is that? Doesn't seem to be a hotwallet but want to be sure?! So this is a specific hww ? And is it restored or created anew? And do you use the windows app or a windows pip installation?
What kind of wallet is that? Doesn't seem to be a hotwallet but want to be sure?! So this is a specific hww ? And is it restored or created anew?
its 2-of-3 multisig, 3x electrum compatible Zpub
keys.
The addresses that are generated are correct and the same as on electrum, so that checks out.
And do you use the windows app or a windows pip installation?
Its a windows app/exe.
ls
in./bitcoin
shows:drwx------ 2 btc2 btc2 4096 Jun 19 15:27 'specterc4032b6b796f6588\test' -rw------- 1 btc2 btc2 16384 Jun 19 13:48 wallet.dat
The path looks suspicious (mix of linux and windows paths?).
There is definitely sth. wrong here. This \test shouldn't be there after specterc4032b6b796f6588. I suppose sth. got mixed up due to Windows.
IMHO this is the result of all installations where specter is running on windows and core is running on linux. The result is probably that the wallet is fully functioning but it is listed as a failed wallet. It's astonishing why we didn't got that bug-report earlier. It's one of those "How could that ever worked" moments.
The PROPER fix won't be easy either. Itprobably doesn't hurt only fixing the error-messages. Turning the backslash into a slash (and therefore really use a subdirectory) will need a migration of all the wallets which has been created like that. But before that, we need more tests: How does it behave exactly in that setup?
As a side note, an interesting fact I came across today: If you delete / (have a wrong path to?) a Bitcoin Core wallet it still remains as loaded wallet and also works fine with Specter. Only when you restart bitcoind will you have trouble. Perhaps one of the reasons for the "How could that ever worked".
Specter Desktop is not showing transactions. In the log I can see a potential problem:
Using Specter v1.10.2. Specter server runs locally on a Windows machine. Bitcoind v22 (latest) is on remote Linux server.
ls
in./bitcoin
shows:The path looks suspicious (mix of linux and windows paths?).