You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the public key as input to Sign, Verify etc., we can define it either as a point of G2 or as an octet string. Rn we do the later, consistent with what the BLS spec does.
That said, passing it as a G2 point, will simplify the encode for has operation a bit, since we don't need a "special clause" there so we would not append it with it length, since it would be handled like any other point. See also here for context.
IMO defining it as an octet string is more intuitive, but Im fine with both.
The text was updated successfully, but these errors were encountered:
When using the public key as input to Sign, Verify etc., we can define it either as a point of G2 or as an octet string. Rn we do the later, consistent with what the BLS spec does.
That said, passing it as a G2 point, will simplify the encode for has operation a bit, since we don't need a "special clause" there so we would not append it with it length, since it would be handled like any other point. See also here for context.
IMO defining it as an octet string is more intuitive, but Im fine with both.
The text was updated successfully, but these errors were encountered: