It may be useful to be able to export this timestamp information so that it can be analyzed in order to develop the final tie-breaking algo.
- Mentioned In
- rSTAGINGebff5f83feac: Add logging for block header receive time
rSTAGING144714e17f1c: Add nTimeReceived to CBlockIndex for tracking recevied time of blocks
rABCebff5f83feac: Add logging for block header receive time
D1441: Add logging for block header receive time
rABC144714e17f1c: Add nTimeReceived to CBlockIndex for tracking recevied time of blocks
T196: Storage block arrival time
D1288: Add nTimeReceived to CBlockIndex for tracking recevied time of blocks
D1196: Discourage selfish mining by favoring blocks with more accurate timestamps
T214: Replace LogPrintf with LogPrint
- Mentioned Here
- T214: Replace LogPrintf with LogPrint
When discussing T214, I realized I may need to add a new logging category to track the timestamps for racing blocks. schancel suggested the following:
schancel [1:40 PM]
@jasonbcox If you are going to do that I would actually like to do something a little more subtle.
@jasonbcox That'd be to keep the category which maps to a syslog level as well. But to introduce structured log which allows adding key-values to the entries.
Doing this would allow us to pretty easily do all kinds of log analysis.
EDIT: Created new tickets for these tasks, as they're kinda orthogonal to implementing header timestamp tracking (although they do make it nicer!):
Adding syslog levels: https://reviews.bitcoinabc.org/T221
Adding key-value support: https://reviews.bitcoinabc.org/T222