Open
Conversation
eladiosch
approved these changes
Jan 19, 2026
|
Changes look good. However this PR should NOT be merged into main, because this is not going to be the way the protocol will work. The idea is to keep all these changes ready in case we change course. I suggest creating a different branch (in all relevant repos) and make the PRs merge into that branch |
Contributor
Author
Agree. I suggest to use this branch |
eladiosch
reviewed
Jan 22, 2026
eladiosch
reviewed
Jan 22, 2026
eladiosch
approved these changes
Jan 26, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Which issue(s) does this PR fixes:
Remove intel, guardian/enclave fields from ValidatorKeyData when registering new validator (from PufferProtocol)
AB#4220