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
In the previous implementation the transcript interface had a common_scalar and common_point interface. This allowed to have different prefixes when adding each type of arguments to the transcript (see here) as follows:
/// Prefix to a prover's message containing a curve point
const BLAKE2B_PREFIX_POINT: u8 = 1;
/// Prefix to a prover's message containing a scalar
const BLAKE2B_PREFIX_SCALAR: u8 = 2;
then, the hasher was initialised with
self.state.update(&[BLAKE2B_PREFIX_POINT]);
in case of a point and with
self.state.update(&[BLAKE2B_PREFIX_SCALAR]);
in case of a scalar.
Now we use the same prefix for every type of input. I believe that is fine, as the goal of these prefixes is to have a separator for every new input. However, I did want to check that I'm not missing out anything, and that it is indeed crucial that those prefixes are distinct.
The text was updated successfully, but these errors were encountered:
In the previous implementation the transcript interface had a
common_scalar
andcommon_point
interface. This allowed to have different prefixes when adding each type of arguments to the transcript (see here) as follows:then, the hasher was initialised with
in case of a point and with
in case of a scalar.
Now we use the same prefix for every type of input. I believe that is fine, as the goal of these prefixes is to have a separator for every new input. However, I did want to check that I'm not missing out anything, and that it is indeed crucial that those prefixes are distinct.
The text was updated successfully, but these errors were encountered: