diff options
author | Wladimir J. van der Laan <laanwj@protonmail.com> | 2019-08-29 16:41:29 +0200 |
---|---|---|
committer | Wladimir J. van der Laan <laanwj@protonmail.com> | 2019-08-29 16:41:46 +0200 |
commit | d8fc9979130a268cf55b12c223b20fd7d4b9f67f (patch) | |
tree | 66096a0b0d2430920184444b9fd2d83418efa024 /src/qt/guiutil.cpp | |
parent | 75142ece6b6624bcc1c480d170b92ed07359fd4c (diff) | |
parent | d48c1e837ae1bd08e0f18ad1b57ff72675c3d6ad (diff) | |
download | bitcoin-d8fc9979130a268cf55b12c223b20fd7d4b9f67f.tar.xz |
Merge #16695: rpc: Add window final block height to getchaintxstats
d48c1e837ae1bd08e0f18ad1b57ff72675c3d6ad Add window final block height to getchaintxstats (Jonathan "Duke" Leto)
Pull request description:
This patch is motivated by the desire to make the output of `getchaintxstats` more useful and optimized for applications to consume and render the data.
Firstly, this data is already available to the RPC, no additional work is done. Currently additional RPC calls will be needed to look up the height of the final block in the window or the block height that began the window.
By adding the block height of the final block in the window, the JSON is "self-contained" and applications can calculate the exact block height range of the window with no additional RPC requests.
For example, a web application which wants to render historical information for `getchaintxstats` RPC on various window sizes might call the RPC with various window lengths, once per day, and store the JSON results somewhere. Because the final block height of each dataset is included, it's no extra work to determine the exact block window range of each JSON response.
ACKs for top commit:
promag:
ACK d48c1e837ae1bd08e0f18ad1b57ff72675c3d6ad.
Tree-SHA512: fd4952c125f81a4ad18f7c78498c6b3e265b93cb574832166ac25596321ce84957f971f3f78f37d7e42638dc65f2a5d4d760f289873c9c2f2a82eb00a0f87c3f
Diffstat (limited to 'src/qt/guiutil.cpp')
0 files changed, 0 insertions, 0 deletions