-
Notifications
You must be signed in to change notification settings - Fork 92
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
Missing anchors #1045
Comments
I keep parsing in my local environment, will add into first post if there are more missing anchors |
Have you scanned the BTC chain to see if there are orphaned transactions that were never registered on the Factom side? All the anchoring entries were made by the same address ( |
No, I am noticing responses from factomd in this thread.
I build anchors parser in explorer the same way it parses dblocks — from 0 height to latest.
If anchor is missing, parsing stops.
It was unexpected for me that there are a lot of missing anchors from 2 years past, so I add placeholder to db and explorer continues fetching anchors until next missing. I wrote all missing anchors on github (for Factom Inc and me) to get back to them later and add manually, once they created.
|
I refactored Explorer so it will be parsing only missing anchors. Something like: {"result":[{"db_height":200000}, {"db_height":200001}, …]} Will it be useful? @PaulSnow @WhoSoup @carryforward |
For audit purpose — all missing BTC and ETH anchors |
(edited)
Missing BTC and ETH anchors:
#1045 (comment)
The text was updated successfully, but these errors were encountered: