Skip to content
This repository has been archived by the owner on Jun 11, 2024. It is now read-only.

Tracking of missed blocks #349

Closed
4miners opened this issue Dec 10, 2016 · 1 comment
Closed

Tracking of missed blocks #349

4miners opened this issue Dec 10, 2016 · 1 comment

Comments

@4miners
Copy link
Contributor

4miners commented Dec 10, 2016

We should track information about missed blocks - that will give us better network overview. To achieve that we need additional table in database, for example missed_blocks in which we will store information about outsiders:

  • block height
  • slot number
  • expected generator public key

We should check if need to delete from that table in case of round backward-tick.
Also proper endpoint that will return those missed block should be added to API.

Resources:
https://github.com/LiskHQ/lisk/blob/development/logic/round.js#L25
https://github.com/LiskHQ/lisk/blob/development/sql/rounds.js#L8
https://github.com/LiskHQ/lisk/blob/development/modules/rounds.js#L242

@shuse2
Copy link
Collaborator

shuse2 commented Jul 29, 2019

Closing due to no active discussion.
Also, this should be done in extra module, maybe monitoring module.

@shuse2 shuse2 closed this as completed Jul 29, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants