The experiment:

I was doing an experiment and I have a question that I wasn't able to answer myself.

I will post some real data here (but not private keys etc).

I have a fully airgaped computer, where I installed Bitcoin Core and I created a wallet.

I got an address from there bc1qfrmthac4es7fpw5yhl7cu9kvedsgj7levwxv5g and sent some sats there.

I then stored the encrypted wallet.dat in another usb stick for backup.

I also got the descriptors of the wallet using the command listdescriptors:


Then, I decided, to import the descriptors on Sparrow wallet to see if I would be able to create a simple watch-only wallet.

Sparrow didn't let me import two descriptors on the same wallet, so I had to google it and someone suggested to import the descriptor like this:


Notice the <0;1> in the path, which I suspect is to get both receiving and change addresses.

To my surprise, it looked like it worked perfectly, but...

I decided to import the descriptors on my full node (bitcoin core) to create a watch-only wallet there too, so I did:


The "strange" result:

In Bitcoin Core, it looks like my addresses (when I click to generate a new address) are correct, but it generates the Receive addresses that Sparrow considers to be the Change addresses.

In simpler terms, it looks like:

Bitcoin Core -> Receive Address = Sparrow -> Change Address

My question:

Even though the answer may be the simplest one, like that I have confused the descriptors when importing them, or that Sparrow doesn't work well with the <0;1>, I would like to ask for a clear justification.