-
Notifications
You must be signed in to change notification settings - Fork 2
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
blockchain reorg testing framework #44
Comments
blocks #45 |
https://github.com/drandreaskrueger/chainhammer https://github.com/wolfcw/libfaketime |
@InoMurko Can we just use geth chain config which defines block numbers for hard forks?
|
Hmm. This issue is specifically related to manually induce https://en.bitcoin.it/wiki/Chain_Reorganization |
some of my previous note talking with white block: https://omisego.atlassian.net/l/c/2ECjxSf6 |
This is cool. I would like to wait for @ayrat555 to review the task in detail, provide some feedback to us how difficult would this be to create on our own - since we would like to see this testable, we would need this continuously (in CI). |
Currently, I'm trying to do the following:
|
I would like to be able to trigger random reorgs on private geth chains of N depth. I believe something like that could possibly be achieved with docker engine and https://github.com/alexei-led/pumba (or similar tool, that allows you to manipulate network and containers).
This was we are going to be able to validate our assumptions in designing childchain and provide proofs of whit-standing these attacks and glitches.
linked: #31
The text was updated successfully, but these errors were encountered: