I took the text from bitcoin.org's description. @harding Is this originally from there?
edit: Changed the wording
I took the text from bitcoin.org's description. @harding Is this originally from there?
edit: Changed the wording
@instagibbs yes; that description was written by me based upon my reading of the code.
ACK
383 | @@ -384,6 +384,7 @@ UniValue getblock(const UniValue& params, bool fHelp) 384 | " \"nonce\" : n, (numeric) The nonce\n" 385 | " \"bits\" : \"1d00ffff\", (string) The bits\n" 386 | " \"difficulty\" : x.xxx, (numeric) The difficulty\n" 387 | + " \"chainwork\" : \"xxxx\", (string) The estimated number of block header hashes checked from the genesis block to this block, in hexadecimal\n"
I don't understand this sentence. I like (string) Expected number of hashes required to produce the current chain (in hex) better.
What don't you understand about it specifically? Would:
(string) Expected number of hashes required to produce the chain up to this block (in hex)
be better? As-is it's ambiguous to what "current chain" means. In getblockchaininfo it clearly means the valid chain with most work.
block header hashes
is not immediately clear what this means. Usually blocks with hashes that don't hit the diff are not considered valid, so they are not counted. Then "estimated" gives the hint that they are counted as well.
@instagibbs I like your suggestion as well.
Updated wording re: @MarcoFalke comments.
utACK 94bdd71f9b4768c9803ffd133aa7781b19bfa6f9
utACK