-
Notifications
You must be signed in to change notification settings - Fork 170
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
Epoching AnteHandler rejects genesis staking transactions #36
Comments
Thanks for the finding and adding this check to CI. I will look into this issue and submit a PR to patch it tomorrow. |
I suspect that the cause of this issue is that during genesis, a set of validators is created using genesis transactions. This means that we need to modify those transactions that are generated for genesis to transactions that are handled by the |
You are right, the issue's root cause is the module initialisation, including genesis and parameters. The AnteHandler has to skip the genesis so that the genesis transactions can be executed correctly. I'm working on a PR (#41) to fix this issue, as well as other initialisation stuff of the epoching module, as they need to be done anyway. However, there is a test that constantly fails, blocking this PR. It seems that the issue is also about initialisation, where each module's genesis will be exported to somewhere. Do you have any idea on this? |
Just tested it on the branch and I don't get this kind of error. What sequence of commands are you executing? Maybe you need to remove the directory in which you instantiated the testnet files and rerun. Also, |
Well I just fixed it 5 min ago in the last commit... I forgot adding some stuff in |
Currently, the chain cannot bootstrap:
If the change introduced by #18 inside
x/epoching/keeper/drop_validator_msg_decorator.go
is reverted, the code works fine.@SebastianElvis @aakoshh thoughts? If an immediate fix is not available, I suggest reverting the commit because it is currently blocking development on other features since the chain can't be ran.
The text was updated successfully, but these errors were encountered: