-
Notifications
You must be signed in to change notification settings - Fork 0
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
Validator epochs/ZIP25 #1298
Open
theo-zil
wants to merge
14
commits into
main
Choose a base branch
from
validator-epochs-zip25
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Validator epochs/ZIP25 #1298
Changes from 3 commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
ceb10c2
Implement epochs (ZIP-25) in deposit contract.
theo-zil 028f7cc
Merge branch 'main' of github.com:Zilliqa/zq2 into validator-epochs-z…
theo-zil 92b97ad
fmt, clippy
theo-zil 92eaaf5
Fixes and debugging. Basic tests passing for staker deposit (new stak…
theo-zil 0399314
whoops, deadlock in tests
theo-zil c6824b0
Merge branch 'main' of github.com:Zilliqa/zq2 into validator-epochs-z…
theo-zil 8d41db7
extra check for new max committee size limit
theo-zil 71ab43b
nightly fmt...
theo-zil 7ede49f
james: make stakers pre-compute changes to committee
JamesHinshelwood e00fc3e
wip
JamesHinshelwood d04c12d
Merge remote-tracking branch 'origin/main' into validator-epochs-zip25
JamesHinshelwood 6ebbd9f
wip
JamesHinshelwood a17385a
Apply formatting changes to solidity files
JamesHinshelwood 91e49c9
Merge remote-tracking branch 'origin/main' into validator-epochs-zip25
JamesHinshelwood File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Our consensus now depends on successful EVM calls - and not just read-only checks as before, but a complex write transaction.
This raises the question of what to do if the
tick_epoch()
call fails for any reason. Should we assume that it must never fail, and crash the node if it does (potentially crashing the network if a buggy state is reached)? The approach taken here is to soft-ignore errors; the network then will remain alive, but with a static validator set since epoch changes will be broken. Measures can then be taken to upgrade to fix the root cause of the issue (e.g. upgrading the deposit contract) to restore normal functionality.But, especially right now in the early testnet phases, perhaps hard-crashing the network on any bugs might be preferable to discover any issues immediately.