-
Notifications
You must be signed in to change notification settings - Fork 129
Enforce encrypted transaction inputs on submission #2389
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
Merged
Merged
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
1bebafc
refactor: force tx input encryption on submission
juan518munoz e3bdc23
fix: pass formatting and feature checks
huitseeker e781db4
feat: verify transaction encryption key attestations
huitseeker 6e54db5
fix: require verified keys for transaction sealing
huitseeker d5c7e98
fix: remove stale relay key caching
huitseeker 6adfa66
fix: configure trusted keys for local clients
huitseeker d434321
fix: address encrypted submission review
huitseeker c6de87e
fix(rpc): fan out sealed batch inputs
huitseeker 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
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
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
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
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
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
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
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
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.
Question (relevant for some other places too): is this a temporary simplification? The monitor should be able to get validator's signing keys from the blockchains (i.e., the block headers) - right?
Uh oh!
There was an error while loading. Please reload this page.
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.
Yes.
MIDEN_MONITOR_VALIDATOR_SIGNING_PUBLIC_KEYis temporary. #2389 uses it to trust encryption-key attestations. The monitor should instead read validator signing keys from authenticated block headers.#2390 and #2393 keep the fixed setting. After they land, #2373, including #2382, will be rebased on top. That integration should pass chain-derived validator keys to #2373’s schedule verifier and remove the environment variable. The same change should remove fixed validator keys from the other node submitters. Each submitter will then follow validator changes through trusted chain state instead of local config.
/cc @juan518munoz