Backfill/repair database after changes #84

Closed
opened 2021-06-11 13:59:03 +00:00 by i-norden · 1 comment
Member
- [x] leaf keys for deleted values: https://github.com/vulcanize/go-ethereum/issues/59 - [x] new logs table: https://github.com/vulcanize/go-ethereum/issues/79 - [x] code and codehash: https://github.com/vulcanize/go-ethereum/issues/90
Author
Member

We aren't going to backfill/repair, instead we are doing a complete sync (https://github.com/vulcanize/ops/issues/76) and will validate using the approach described in https://github.com/vulcanize/ops/issues/78

We aren't going to backfill/repair, instead we are doing a complete sync (https://github.com/vulcanize/ops/issues/76) and will validate using the approach described in https://github.com/vulcanize/ops/issues/78
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: cerc-io/go-ethereum#84
No description provided.