Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Timestamp Observatory #1924

Open
zookozcash opened this issue Dec 5, 2016 · 2 comments

Comments

5 participants
@zookozcash
Copy link

commented Dec 5, 2016

Importing this from https://github.com/Electric-Coin-Company/infrastructure/issues/45

Write a tool that monitors the blocks from the network observatory and reports, for each block seen:

  • the timestamp
  • its position in the blockchains
  • the peer it was received from
  • the beneficiary address of the coinbase transaction
  • in the case that it is the new tip, what the resulting difficulty factor is
@zookozcash

This comment has been minimized.

Copy link
Author

commented Jan 11, 2017

@bitcartel: This is the ticket that I think https://github.com/bitcartel/findtimewarpers might be a partial solution to. To be a full solution, I'd like to see a publicly visible, live-updated display of the results. (Ideally, https://zcha.in would host it. ☺)

@nathan-at-least

This comment has been minimized.

Copy link
Contributor

commented Jan 17, 2017

Note, I've added #2022 which would make the local timestamp of first sight of block headers persistent information from the zcashd rpc interface.

In fact, glancing back at Zooko's bullet points of required information, I believe I'd prefer to store and present all of that information via the blocks database and RPC interface (unless any particular case is troublesome).

If there are more expedient ways to gather this information for an observatory, then these kinds of diagnostic improvements to zcashd should not block setting up the observatory.

@ebfull ebfull modified the milestones: 1.0.5, 1.0.6 Jan 19, 2017

@bitcartel bitcartel modified the milestones: 1.0.7, 1.0.6 Feb 6, 2017

@str4d str4d modified the milestones: 1.0.7, 1.0.8 Mar 10, 2017

@nathan-at-least nathan-at-least modified the milestones: 1.0.9, 1.0.8 Mar 20, 2017

@nathan-at-least nathan-at-least added this to In Progress in Continuous Improvement Apr 20, 2017

@nathan-at-least nathan-at-least moved this from In Progress to Work Queue in Continuous Improvement Apr 20, 2017

@nathan-at-least nathan-at-least removed this from Work Queue in Continuous Improvement May 10, 2017

@nathan-at-least nathan-at-least removed this from the 1.0.9 milestone May 10, 2017

@nathan-at-least nathan-at-least moved this from In Progress to Nominated for Release in Monitoring, Metrics, and Analysis Jul 3, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.