Load key_hash from orakl-cli & compare with incoming VRF request
#365
+51
−36
Conversation
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
|
/integration |
|
/integration |
martinkersner
deleted the
i-360/feat/vrf-listen-only-to-keyhash-specific-requests
branch
|
/integration |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
This PR adds a new field
key_hashforVrfKeytable in SQLite oforakl-cli. Consequently, thiskey_hashis loaded in VRF listener and used to compare with incoming requests that include a key hash representing an entity that should respond with random words.Note:
key_hashis loaded in listener in global scope. This is a not good practice, and we plan to fix it together with other listener related issues at #236Type of change
Checklist before requesting a review
Deployment