Bitcoin Core opens "Cormorant" wallet each time I open Sparrow wallet. Why?

[billllib]

Hey there!

I am a Sparrow wallet beginner as well as a Bitcoin Core newbie and I don’t understand, why Bitcoin Core opens a "Cormorant" wallet each time I open Sparrow wallet. I don't want that.

I googled a lot and also searched this forum for keywords "cormorant", "Sparrow" etc. but no further clues.

My setup:
I have Bitcoincore (…and nothing but Bitcoincore…) running on one computer (Linux Ubuntu) and installed Sparrow on another computer on MacOS (10.15 Catalina). I created a new wallet in Sparrow and transferred a small test amount to it. TX successful, I can see the small amount in Sparrow. So far, so good.

But why do I see this amount and all the details about it ALSO on the Linux computer where BCC is running? I want to manage my transactions just on the Mac in Sparrow...

And each time I close the "cormorant" wallet and delete the "cormorant" wallet data within the ./bitcoin/wallets/cormorant folder, it reappears as soon as I open Sparrow on the Mac.

– Can I disable the "cormorant" wallet somehow? Or is it necessary?
– Are my BCC server settings wrong? I've done it the way the Sparrow page says: https://sparrowwallet.com/docs/connect-node.html

The settings:
- - - - -
server=1
txindex=1

[main]
rpcbind=[Here the IP of the LINUX computer with Bitcoincore]
rpcallowip=[Here the IP of the Mac computer with Sparrow]
- - - - -

Any help is much appreciated!

[1714484853]

1714484853

[1714484853]

1714484853

[1714484853]

1714484853

[nc50lc]

Sparrow needs that "cormorant" wallet to sync your sparrow wallets.
It does that instead of relying on database like Electrum server does.

It doesn't contain any private keys so you can't manage your funds from there, it only displays it.
You can see that it has ""private_keys_enabled": false," in the result if you go to console, select the wallet in the drop-down menu, then enter: getwalletinfo

[billllib]

Sparrow needs that "cormorant" wallet to sync your sparrow wallets.
It does that instead of relying on database like Electrum server does.

It doesn't contain any private keys so you can't manage your funds from there, it only displays it.
You can see that it has ""private_keys_enabled": false," in the result if you go to console, select the wallet in the drop-down menu, then enter: getwalletinfo

Thanks for the explanation. Okay, that reassures me, sort of. It's still a mystery to me why Sparrow "needs that wallet".

I don't know if the following use case corresponds to reality, but imagine this: You set up a network with a "server" computer running BCC and multiple "clients" for different people to log in and manage their transactions. I assume that the server administrator would be able to see the wallets of all connected clients, right? Why would he "need to see that"?

So that seems to be the main argument for "running your personal node" instead of connecting to a public node / public server, right?

[nc50lc]

So that seems to be the main argument for "running your personal node" instead of connecting to a public node / public server, right?

Right, the only for-public-use option is the "Public Server" tab.
The two server options "Bitcoin Core" and "Private Electrum" are meant for private use.

Thanks for the explanation. Okay, that reassures me, sort of. It's still a mystery to me why Sparrow "needs that wallet".

Those public Electrum servers that you can connect to have their own database built from the blockchain that the client Sparrow query to sync.

On the other hand, if you use Bitcoin Core as server, Sparrow needs to use the cormorant wallet that it created with your Sparrow wallets' descriptors to scan the blockchain for transactions.
Then it uses RPC to query the needed data from that wallet or node, some require a loaded wallet to work.

[billllib]

So that seems to be the main argument for "running your personal node" instead of connecting to a public node / public server, right?

Right, the only for-public-use option is the "Public Server" tab.
The two server options "Bitcoin Core" and "Private Electrum" are meant for private use.

Thanks for the explanation. Okay, that reassures me, sort of. It's still a mystery to me why Sparrow "needs that wallet".

Those public Electrum servers that you can connect to have their own database built from the blockchain that the client Sparrow query to sync.

On the other hand, if you use Bitcoin Core as server, Sparrow needs to use the cormorant wallet that it created with your Sparrow wallets' descriptors to scan the blockchain for transactions.
Then it uses RPC to query the needed data from that wallet or node, some require a loaded wallet to work.

Thanks again.

So this "cormorant" wallet mirrors my real wallet (in Sparrow on the other computer) and shows the current balance, recent transactions, etc. But it is not able to e.g. sign transactions. 

- Is this what is known as a "watching" wallet?
- So it has to have the xpub, right?
- In order to stay safe, do I need to change my security settings?

[nc50lc]

- Is this what is known as a "watching" wallet?
- So it has to have the xpub, right?
- In order to stay safe, do I need to change my security settings?

- Yes, you can confirm that by checking if private keys are enabled in getwalletinfo command as I've mentioned earlier.

- Yes, it's a descriptor wallet with public descriptors only. You can see each descriptors via listdescriptors command.

- No, if you haven't exported any private key from Sparrow, there'll be no security issue regarding the xpub contained in your cormorant wallet.
That's because even a single child private key can be used together with the (parent) xpub to derive its xprv pair
That could compromise all the other private keys of that wallet. If you did, consider creating another wallet.

[billllib]

- Yes, you can confirm that by checking if private keys are enabled in getwalletinfo command as I've mentioned earlier.
- Yes, it's a descriptor wallet with public descriptors only. You can see each descriptors via listdescriptors command.
- No, if you haven't exported any private key from Sparrow, there'll be no security issue regarding the xpub contained in your cormorant wallet.
That's because even a single child private key can be used together with the (parent) xpub to derive its xprv pair
That could compromise all the other private keys of that wallet. If you did, consider creating another wallet.

1. It says: private_key_enabled = false . Is that bad? I didn't consciously change it. How can I change it?

2. I get an output, but I really don't know what they mean. Timestamp, active, range. Hm?

I noticed something else today:
I made another small transaction from the Sparrow wallet. It was successful and the balance and the transaction itself are shown correctly in Sparrow.
But in the Cormorant wallet the balance is correctly updated, but the transaction is NOT listed at all (under "recent transactions"). How can that be?

[nc50lc]

1. It says: private_key_enabled = false . Is that bad? I didn't consciously change it. How can I change it?

No, "false" means that descriptors with private keys can't be imported there.
Refer to my first reply regarding that result.

2. I get an output, but I really don't know what they mean. Timestamp, active, range. Hm?

The "xpub" that you were asking is listed in each of the descriptors.
You can get more information about the other data in help listdescriptors command.

I noticed something else today:
I made another small transaction from the Sparrow wallet. It was successful and the balance and the transaction itself are shown correctly in Sparrow.
But in the Cormorant wallet the balance is correctly updated, but the transaction is NOT listed at all (under "recent transactions"). How can that be?

Have you sent that transaction to your own address?
Because if it is your change address, Bitcoin Core wont show it in the history but will still be included to your available coins.

[billllib]

No, "false" means that descriptors with private keys can't be imported there. Refer to my first reply regarding that result.

I'm sorry, I read that at the time, but only now have I understood it.

The "xpub" that you were asking is listed in each of the descriptors.
You can get more information about the other data in help listdescriptors command.

Okay, it looks like I need to learn more about the command line. (I have a long Mac history, but virtually no DOS/Linux experience, so my shell/terminal skills are very very very poor.)

Have you sent that transaction to your own address?
Because if it is your change address, Bitcoin Core wont show it in the history but will still be included to your available coins.

Yes, it was another address from the same wallet, so my own address.
I have now made another transaction to another wallet, and now the Cormorant wallet is showing this transaction!  

Slowly, I am getting a better understanding of how all these things (UTXO, inputs, change etc.) are connected and work.

@all contributors in this thread: Thank you so much for supporting me! Without helping hands like this, bitcoin adoption would be less likely. (...although it still is a long and bumpy road. Even for tech-minded people like me. It really must get easier in the future...).

[Cricktor]

Okay, it looks like I need to learn more about the command line. (I have a long Mac history, but virtually no DOS/Linux experience, so my shell/terminal skills are very very very poor.)

MacOS is an unixoid OS, too. While it tries to abstract a lot of the inner workings from an user and has a nifty UI, you can also have a powerful command line. Tossing the mouse around isn't everything that's possible, even in MacOS.

(...although it still is a long and bumpy road. Even for tech-minded people like me. It really must get easier in the future...).

I may sound like a broken record when I highly recommend to have a look at https://learnmeabitcoin.com: the beginner's pages are a fun to work through and the more technical sections explain a lot of Bitcoin's details in a nice and informative way. At least I like it very much, recommend it often and regularly go myself there to refresh my knowledge.

[billllib]

I highly recommend to have a look at https://learnmeabitcoin.com

Thanx!! Looks really good!

[ABCbits]

The "xpub" that you were asking is listed in each of the descriptors.
You can get more information about the other data in help listdescriptors command.

Okay, it looks like I need to learn more about the command line. (I have a long Mac history, but virtually no DOS/Linux experience, so my shell/terminal skills are very very very poor.)

You don't have to learn about using terminal, since you could just use built-in Bitcoin Core console (see image below). Although since you already own computer with Linux, you'll benefit from using terminal in long term.


Source: http://bitcoindaily.org/bitcoin-guides/how-to-recover-bitcoins-bitcoin-core-wont-sync-export-private-key/

(...although it still is a long and bumpy road. Even for tech-minded people like me. It really must get easier in the future...).

I may sound like a broken record when I highly recommend to have a look at https://learnmeabitcoin.com: the beginner's pages are a fun to work through and the more technical sections explain a lot of Bitcoin's details in a nice and informative way. At least I like it very much, recommend it often and regularly go myself there to refresh my knowledge.

And Sparrow wallet meant for power user. IMO average people should use more friendly wallet software such as Blue wallet.