Choose format - Githubissues

noncesense-research-lab / archival_network

Investigating the frequency of alternative blocks, reorganizations, potential double-spend attacks, selfish mining, and more.

MIT License

14 stars 7 forks source link

Choose format #2

Closed Mitchellpkt closed 6 years ago

Mitchellpkt commented 6 years ago

Right now data is organized in messy grep'd out log dumps. Need a clean format to use for this project. It seems like each entry receiving a given block should contain:

Block height
Block nonce
Timestamp (optional, since redundant with block height, but finer-grained)
Block version A identifier
Block version B identifier
(Block version C identifier?)
Did this cause a reorganization (0/1)

Suggestions for format? Other ideas for data to include? Thanks!

Mitchellpkt commented 6 years ago

Miner recorded time (MRT), whatever they put in the "timestamp" field of the block
Node receipt time (NRT), the timestamp when our node received each copy of the block

If the node receives 5 copies of a block (duplicates from multiple nodes, not because of a fork) then there will be 5 NRT timestamps that we can analyze for latency, etc.

Mitchellpkt commented 6 years ago

MM-DD-YYYY format will mess us up hard as soon as January rolls around. It should never be used anywhere in any project.

When not using unix time, then YYYY-MM-DD-HH-MM-SS or bust.

Mitchellpkt commented 6 years ago

See https://github.com/Mitchellpkt/monero_archival_project/blob/master/misc/MAP_daemon_format.xlsx and https://github.com/Mitchellpkt/monero_archival_project/blob/master/misc/MAP_daemon_format.pdf

Mitchellpkt commented 6 years ago

Closing, now that format is documented. May re-open this issue or a new one if requirements change.