Merged
Conversation
PaulLaux
reviewed
Jun 20, 2023
Collaborator
PaulLaux
left a comment
There was a problem hiding this comment.
one change is required to make it perfect.
Also,
- please fix comment on line 190: /// Converts this issuance validating key to its serialized form
to "spend key"
src/keys.rs
Outdated
| pub fn from_bytes(sk_iss: [u8; 32]) -> CtOption<Self> { | ||
| CtOption::new( | ||
| IssuanceKey(sk_iss), | ||
| SpendingKey::from_bytes(sk_iss).is_some(), |
Collaborator
There was a problem hiding this comment.
I don't think we need this check.
Collaborator
There was a problem hiding this comment.
what we need is to make sure we can derive IssuanceValidatingKey, IssuanceAuthorizingKey potentially by calling
impl From<&IssuanceKey> for IssuanceAuthorizingKey {
fn from(sk_iss: &IssuanceKey) -> Self {
let isk = to_scalar(PrfExpand::ZsaIsk.expand(&sk_iss.0));
// IssuanceAuthorizingKey cannot be constructed such that this assertion would fail.
assert!(!bool::from(isk.is_zero()));
IssuanceAuthorizingKey(conditionally_negate(isk))
}
}
/// and...
IssuanceValidatingKey {
/// Constructs an Orchard issuance validating key from uniformly-random bytes.
///
/// Returns `None` if the bytes do not correspond to a valid key.
pub fn from_bytes(bytes: &[u8]) -> Option<Self> {
<[u8; 32]>::try_from(bytes)
.ok()
.and_then(check_structural_validity)
.map(IssuanceValidatingKey)
}
}
Collaborator
Author
There was a problem hiding this comment.
I updated the check for IssuanceAuthorizingKey.
I think deriving IssuanceValidatingKey from IssuanceAuthorizingKey never fails (=> no check required for this part)
PaulLaux
approved these changes
Jun 20, 2023
Collaborator
PaulLaux
left a comment
There was a problem hiding this comment.
Approved with one comment.
Closed
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
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.
Updated constants for master (extended) issuance key according to ZIP 227. Previously, we used the same personalization for the master extended spending key and the master extended issuance key, as well as the same purpose constant for the spending master key and the issuance master key.
Now, the following updates have been made: