-
Notifications
You must be signed in to change notification settings - Fork 9
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
no epoch switch #248
Comments
|
might be connected to the point that the Node Software does not respect the gas limits |
retested, does not apply anymore after latest fixes |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
in the latest local tests, i have observed issues for switching to the next validator set.
It is not sure if it is tightly connected to the smart contracts,
and the behaviour has been seen on different versions on the smart contracts.
Versions:
[email protected]:DMDcoin/diamond-contracts-claiming.git
5ec8cbdb226663ecdb41ae6e73e7cdf6294c54cd
[email protected]:DMDcoin/diamond-contracts-core.git
8320ba1
[email protected]:DMDcoin/diamond-contracts-dao.git
4fe48d29dc16af84c65cb946b91e0e8284b9635a
[email protected]:DMDcoin/diamond-node.git
ca61bf7ad23a7457d6ca6957a709fc86d7db5cba
[email protected]:SurfingNerd/honey-badger-testing.git
f526d4341e11940e850afa208252ff056a35e746
watchdog.log
The text was updated successfully, but these errors were encountered: