Skip to content
This repository has been archived by the owner on May 19, 2023. It is now read-only.

Handle reorg outside of confirmation range #192

Closed
AuHau opened this issue Jul 2, 2020 · 1 comment
Closed

Handle reorg outside of confirmation range #192

AuHau opened this issue Jul 2, 2020 · 1 comment
Assignees
Labels

Comments

@AuHau
Copy link
Contributor

AuHau commented Jul 2, 2020

The EventsEmitter can emit reorgOutOfRange event which specifies that reorg happened outside the confirmation range, which tells us that there is a possibility that our current state is invalid.

We have to handle this edge-case somehow. Generally, the solution is to rebuild the state, there are two approaches how to do that:

  1. Notify Devops that this happened with email, but this requires to implement mailing support - bleh.
  2. Automatically rebuild the database. This will be complex though as the precache can take long time to run, so we would want to make some sort of "precache on different DB file" and then swap them. But even then this might give some problems.
@AuHau
Copy link
Contributor Author

AuHau commented Sep 15, 2020

Closed with #273

@AuHau AuHau closed this as completed Sep 15, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants