Bitcoin Forum
May 27, 2024, 05:10:27 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: "iswatchonly": false, misleading?  (Read 85 times)
Decadenze (OP)
Newbie
*
Offline Offline

Activity: 2
Merit: 1


View Profile
December 02, 2022, 12:30:29 PM
Merited by ABCbits (1)
 #1

Hi.

On my journey down the bitcoin rabbit hole i stumbled across something i consider confusing, or misleading.

Some info:
Bitcoin Core 22.0 linux ARM version running on a raspberry pi with debian.

I bought a coldcard wallet, created a descriptor wallet in bitcoin core with the arguments disable_private_keys=true descriptors=true, and imported the descriptor key's into the wallet with the argument "watchonly": true.

When i do a getadressinfo query for the addresses, it shows as ""iswatchonly": false,".

From bitcoininformation.org on watchonly:
"Definition
An address or pubkey script stored in the wallet without the corresponding private key, allowing the wallet to watch for outputs but not spend them."

Isn't that a little bit misleading or confusing? It sure confused me. Per definition, as far as i can figure out at least, "iswatchonly: false" means that bitcoin core has the corresponding private key. Which it does not. I did a getdescriptorinfo to double check that the descriptors i imported does not contain the private key, and the output clearly shows "hasprivatekeys: false".

Is this a bug, or is this intended? Or is there something i don't understand here?
nc50lc
Legendary
*
Offline Offline

Activity: 2422
Merit: 5649


Self-proclaimed Genius


View Profile
December 02, 2022, 01:28:21 PM
Merited by ABCbits (1)
 #2

Is this a bug, or is this intended? Or is there something i don't understand here?
I had a similar (answered) question in this thread where we discussed a similar setup: https://bitcointalk.org/index.php?topic=5414023.msg61052365#msg61052365
You can also read my reply next to it for additional info.

█▀▀▀











█▄▄▄
▀▀▀▀▀▀▀▀▀▀▀
e
▄▄▄▄▄▄▄▄▄▄▄
█████████████
████████████▄███
██▐███████▄█████▀
█████████▄████▀
███▐████▄███▀
████▐██████▀
█████▀█████
███████████▄
████████████▄
██▄█████▀█████▄
▄█████████▀█████▀
███████████▀██▀
████▀█████████
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
c.h.
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
▀▀▀█











▄▄▄█
▄██████▄▄▄
█████████████▄▄
███████████████
███████████████
███████████████
███████████████
███░░█████████
███▌▐█████████
█████████████
███████████▀
██████████▀
████████▀
▀██▀▀
Decadenze (OP)
Newbie
*
Offline Offline

Activity: 2
Merit: 1


View Profile
December 02, 2022, 02:40:11 PM
 #3

Is this a bug, or is this intended? Or is there something i don't understand here?
I had a similar (answered) question in this thread where we discussed a similar setup: https://bitcointalk.org/index.php?topic=5414023.msg61052365#msg61052365
You can also read my reply next to it for additional info.

Ok. So it is intended to be this way then I guess. Nevertheless, quite confusing.
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!