Bug: Use default wallet for rpc commands when multiple wallets are loaded

[oren-z0]

Describe the bug
I'm using the bitcoin nodes also to develop and test some desktop wallets, which create new wallets in bitcoin-core.
This confuses the UI connection attempt.

I'm not sure if it's possible to set bitcoind so it will use a default wallet when it's not specified by the bitcoin-cli.
Specifically I would want all commands to run with -rpcwallet="".

To Reproduce
Steps to reproduce the behavior:

1. Create a new Bitcoin Core node
2. Start Sparrow wallet (with the -regtest flag) and connect to that Bitcoin Core with polaruser & polarpass credentials.
3. See error in the Polar UI

Expected behavior
Polar should just ignore other wallets.

Screenshots

Desktop (please complete the following information):

• OS: MacOS Sequoia 15.1.1
• Polar Version: 3.2.0
• Docker Version: Docker Desktop 4.37.1 Engine 27.4.0
• Docker Compose Version: v2.31.0-desktop.2

Additional context
Add any other context about the problem here.

[jamaljsr]

Hey @oren-z0 Thanks for the feedback. This is a scenario that I have not encountered myself. Appreciate the detailed explanation. This is should be fairly easy to resolve. I'll try to squeeze it in before the next release.

[TomLucasakaTGeek]

Hi @jamaljsr @oren-z0 , I have installed Polar on my Windows along with the Docker desktop setup, and I am able to reproduce this issue, can I work on it if it is still active.

[jamaljsr]

@TomLucasakaTGeek yhanks for offering to work on this. It is up for grabs. Feel free to put up a PR.

[TomLucasakaTGeek]

Most appreciated sir @jamaljsr .

[TomLucasakaTGeek]

Hi @jamaljsr , I have installed Sparrow Wallet on Windows, what should be my next steps.

I am mainly struggling with:-

• Start Sparrow wallet (with the -regtest flag)" and
• Connect to that Bitcoin Core with polaruser & polarpass credentials".

[TomLucasakaTGeek]

Tried following the step: "Connect to that Bitcoin Core with polaruser & polarpass credentials"

By entering the values into the Bitcoin Core Node Server from my Polar's backend1 node[ given above ].

Maybe cause regtest flag is still not setup, or something else.

[ Followed this documenatation: sparrow-connect-node, just so that we are on the same page ]

[jamaljsr]

I have never used sparrow myself, so I'm not sure what's going on. Did you check the backend1 node logs in Polar? Maybe there's some helpful info in there.

[TomLucasakaTGeek]

Sir @oren-z0 we need some help in here 😭

[oren-z0]

@TomLucasakaTGeek Sorry, this was 11 months ago and I'm currently on a trip. I will try to figure what was the bug about when I'll return home in a few days.

[TomLucasakaTGeek]

I have connected Polar node to Sparrow

Don't see any problem, should I create a new wallet to see the issue.

[Edit]

Creating new wallet - "Sparrow-Dummy-Wallet"

[TomLucasakaTGeek]

Caused problem when I try to enter the mnemonic words and create keystore in Sparrow under New or Imported Software Wallet.

[TomLucasakaTGeek]

Made the changes added all the new tests, cleared all the tests using "yarn test" and "yarn test:e2e".
Tried to commit and then something happened @jamaljsr