jasonbcox deadalnix Fabien
- Group Reviewers
Restricted Owners Package (Owns No Changed Paths) Restricted Project
- rSTAGING129395a132a3: Document method for reviewers to verify chainTxData
rABC129395a132a3: Document method for reviewers to verify chainTxData
The new return value from the getchaintxstats RPC may deserve an entry in the release notes.
This also raises a few questions:
- Do we want to update these params every release or only on major ones like bitcoin core do ?
- The current tx rate param does not reflect the actual tx rate, but according to getchaintxstats it doesn't seem to match the other actual params either (./src/bitcoin-cli getchaintxstats 4320 000000000000000001d2ce557406b017a928be25ee98906397d339c3f68eec5d returns tx rate of 0.23). Is this intentional ? (And is it the correct window ?)
I think you must backport PR12309 first, this will add some context to this sentence: https://github.com/bitcoin/bitcoin/pull/12309
Only porting this line is breaking the help output indent (you can see this through ./src/bitcoin-cli help getchaintxstats).
Use pushKV instead:
@Fabien I actually reworded the line as it was in this PR to better reflect our update process. As far as I'm aware, we don't update transaction rate or count in chainparams.cpp which makes PR12309's first line irrelevant. I didn't include the second line change in 12309 for similar reasons.
@jasonbcox This line should be indented to be in line with line 29? Should the next line (31) be indented past that or the same?
I'm not sure if this should be part of our release process.
The more I look into this, the less valuable it looks to me. The only use of chainTxData is for guessing verification progress in the wallet. @deadalnix do you see value in bloating our release process to add updating chainTxData? I don't.