-
Notifications
You must be signed in to change notification settings - Fork 33
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
[fix] epoch scheduler #136
[fix] epoch scheduler #136
Conversation
@0o-de-lally wouldn't it be better (as was proposed in the past), to "piggy back" another process for the epoch change to trigger? I think this epoch flip tx can be easily automated and put on a cron by multiple nodes, but having self dependency here seems safer. |
9be780b
to
f41c6f0
Compare
Yes. Though the first step is to see how it works with more control, and then we can automate it. |
…epoch boundary tx.
f41c6f0
to
2002daa
Compare
958ce68
into
0LNetworkCommunity:main-rebase
Co-authored-by: 0o-de-lally <[email protected]>
Co-authored-by: 0o-de-lally <[email protected]>
Co-authored-by: 0o-de-lally <[email protected]>
Co-authored-by: 0o-de-lally <[email protected]>
Co-authored-by: 0o-de-lally <[email protected]>
Co-authored-by: 0o-de-lally <[email protected]>
Co-authored-by: 0o-de-lally <[email protected]>
Co-authored-by: 0o-de-lally <[email protected]>
Co-authored-by: 0o-de-lally <[email protected]>
Co-authored-by: 0o-de-lally <[email protected]>
Co-authored-by: 0o-de-lally <[email protected]>
Co-authored-by: 0o-de-lally <[email protected]>
Co-authored-by: 0o-de-lally <[email protected]>
Co-authored-by: 0o-de-lally <[email protected]>
This changes the epoch boundary trigger to a "lazy" pattern. Now, the VM does not execute any functions, since it may abort.
For epoch boundary any end user can call Epoch Trigger when the time is right (Boundary Bit getting set). This moves any abort case to the user, instead of the VM. This is harmless to the user.
This is appropriate for times around upgrades.