Fix snap_getBip32PublicKey manifest validation
#970
Merged
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
FrederikBolding
approved these changes
Nov 16, 2022
Mrtenz
force-pushed
the
mrtenz/fix-bip-32-public-key-manifest-validation
branch
from
1a611bc
to
5038f08
Compare
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.
snap_getBip32PublicKeyandsnap_getBip32Entropyuse the same caveat, meaning that the permissions in the Snap manifest should be validated the same. Before, we would validate thesnap_getBip32PublicKeyJSON-RPC params, rather than the caveat.