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

Missing anchors #1045

Open
ilzheev opened this issue Aug 28, 2020 · 5 comments
Open

Missing anchors #1045

ilzheev opened this issue Aug 28, 2020 · 5 comments

Comments

@ilzheev
Copy link
Contributor

ilzheev commented Aug 28, 2020

(edited)
Missing BTC and ETH anchors:
#1045 (comment)

@ilzheev
Copy link
Contributor Author

ilzheev commented Aug 28, 2020

I keep parsing in my local environment, will add into first post if there are more missing anchors

@WhoSoup
Copy link
Member

WhoSoup commented Aug 31, 2020

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 (1K2SXgApmo9uZoyahvsbSanpVWbzZWVVMF), so it should be possible to find them if they exist.

@ilzheev
Copy link
Contributor Author

ilzheev commented Aug 31, 2020 via email

@ilzheev
Copy link
Contributor Author

ilzheev commented Sep 4, 2020

I refactored Explorer so it will be parsing only missing anchors.
I also can develop publicly available API that returns heights with missing BTC and ETH anchors.

Something like:
https://explorer.factom.pro/explorer/anchors/missing
https://explorer.factom.pro/explorer/anchors/missing/btc
https://explorer.factom.pro/explorer/anchors/missing/eth

{"result":[{"db_height":200000}, {"db_height":200001}, ]}

Will it be useful? @PaulSnow @WhoSoup @carryforward

@ilzheev
Copy link
Contributor Author

ilzheev commented Sep 5, 2020

For audit purpose — all missing BTC and ETH anchors
missing-anchors.zip

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants