-
Notifications
You must be signed in to change notification settings - Fork 93
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
refactor: quorum creation is the divine right of the registry coordinator #28
Merged
Merged
Changes from all commits
Commits
Show all changes
25 commits
Select commit
Hold shift + click to select a range
70cdc89
style: use for loop indices when the index is just an index
wadealexc 7be39b3
refactor: Use a signed delta value in StakeRegistry to remove tons of…
wadealexc 27568d2
style: use over , and simplify
wadealexc d5f0241
feat: only update total history for nonzero delta, and dont push upda…
wadealexc 5f49736
style: use uint256 in registry coordinator
wadealexc a0d2c34
test: fix broken tests for StakeRegistry changes
wadealexc b4709cb
refactor: wip refactor to move "createQuorum" to the registry coordin…
wadealexc 50e4bca
merge into m2-mainnet
wadealexc 066a6dc
chore: update core contract submodule
wadealexc 12b09de
fix: fix compilation issues and tests
wadealexc aa1d513
refactor: wip refactor for index and blspubkey registries to simplify…
wadealexc 27a3cba
style: pull out common logic to a helper method
wadealexc 708acb5
style: pulled additional logic out into a helper method
wadealexc 21f97b1
refactor: simplify registry coord state variable names and clean logi…
wadealexc 60ccc13
fix: enforce invariant that existing indice have nonzero length histo…
wadealexc 88abb15
style: shorten state variable and function naming in registry coordin…
wadealexc 5cd0d96
style: shorten state variable and function naming in stake registry
wadealexc 698d818
style: remove unused index registry function
wadealexc b883fd0
refactor: pk compendium stores operator pubkeys and can look them up
wadealexc 5968dcf
style: shorten state variable and function names to be more consisten…
wadealexc 231bbe3
style: removed redundant check and swapped param order to be consiste…
wadealexc c5d5dc8
Merge pull request #43 from Layr-Labs/alex/refactor-registries
wadealexc 1adb1d6
Merge branch 'alex/refactor-quorums' into alex/refactor-pubkey-registry
wadealexc bb4011e
style: remove redundant checks from pubkey compendium
wadealexc 9a060e5
Merge pull request #51 from Layr-Labs/alex/refactor-pubkey-registry
wadealexc 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.
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.
good question. relatedly, should we actually push the hash of the zero point in the first update, rather than zero per se?
I think this probably shouldn't revert in this case, but am not strongly opinionated
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.
question for @gpsanant
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.
good point, let's push the zero hash
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.
so to confirm, the change is to push the zero hash for the first update, and have this method fail if
apkHash == 0
?Should it also fail if
apkHash == ZERO_HASH
?