Stack Exchange network consists of 183 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.
Thank you for the quick reply. I asked this question because we were debating what would be the minimum amount of UTXOs that can ever be. So I guess 102 utxos? twitter.com/zndtoshi/status/…
I wanted to ask here first before making a feature request. Wanted to make sure its not a stupid request. Regarding importing watch only wallet those are extra steps users could just refuse to do or too difficult to import from HW.
I used that rpc from my full node and verified a random transaction on the blockchain. The output of that command was the inputs of the tx and the outputs and number of confirmations and other info. So that is definitely from outside of the local wallet. Maybe I misunderstood your answer.
Ok. So the target is given by nBits (which is very granular and that's perfect). But if this is true, why do you need zeroes in front of the header hash? Wouldn't you just take the nBits target and verify the header hash is correct? Or are the hash header leading zeros exponentially increasing difficulty?
Ok I understand that nBits is actually the difficulty target, which is part of the header. I still don't understand what this has to do with the header hash leading zeroes: I assume a full node takes the header, double sha256s it and gets a header hash that it compares to the nBits to see if it's right. Correct? My question is how are those leading zeroes more granular for finding the right hash of the header? I think I'm missing something here..
