-
Notifications
You must be signed in to change notification settings - Fork 689
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
Ensure key ownership proof is optimal #4699
Conversation
The CI pipeline was cancelled due to failure one of the required jobs. |
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.
Looks good to me!
@serban300 the I don't see how this PR would impact that path, but needs double-checking from you. |
I think the root cause for the |
@bkchr I think I addressed all your comments. Could you PTAL ? |
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.
Looks good to me! Good work!
d604e84
Ensure that the key ownership proof doesn't contain duplicate or unneeded nodes. We already have these checks for the bridge messages proof. Just making them more generic and performing them also for the key ownership proof. --------- Co-authored-by: Adrian Catangiu <[email protected]>
Ensure that the key ownership proof doesn't contain duplicate or unneeded nodes.
We already have these checks for the bridge messages proof. Just making them more generic and performing them also for the key ownership proof.