diff options
| author | MarcoFalke <falke.marco@gmail.com> | 2018-05-07 16:49:07 -0400 |
|---|---|---|
| committer | MarcoFalke <falke.marco@gmail.com> | 2018-05-07 16:49:10 -0400 |
| commit | 6b824c090f53d0a56833930fd38c41bcaec8ff4a (patch) | |
| tree | cd6fd314d15472168e424ce9f22c2e98e7128d69 /src/pubkey.h | |
| parent | bf9b03ddcc65c807503d0622c9e43f85cd15d367 (diff) | |
| parent | f30e9be4c194e33c25c20989b3e74dcf9dee7d9a (diff) | |
| download | bitcoin-6b824c090f53d0a56833930fd38c41bcaec8ff4a.tar.xz | |
Merge #13184: RPC Docs: gettxout*: clarify bestblock and unspent counts
f30e9be4c1 RPC Docs: gettxout*: clarify bestblock and unspent counts (David A. Harding)
Pull request description:
Expounds on two things I've seen confuse inexperienced users:
- transactions/outputs in `gettxoutsetinfo`: a user thought this was the total number of transactions or outputs ever seen on the chain, whereas it's only the number in the UTXO.
- bestblock in `gettxout`: a user thought this was the block that included the output, not realizing it was the tip of the current best block chain. I also copied this text to `gettxoutsetinfo` for congruency. I skimmed other uses of "bestblock" in the RPC docs and they seemed clear to me.
Tree-SHA512: c2161c497bef5fe15ee9f1e2a4413fa099b5baa36205ba1ba4b3822885b3ccd1badb9c118a0334f47ba6fa7fff5818ac359cfac6a1108c6847a876b1a251bb7c
Diffstat (limited to 'src/pubkey.h')
0 files changed, 0 insertions, 0 deletions