Refactor and rename Scalar::from_var_bytes
#137
Comments
moCello
added a commit
that referenced
this issue
Dec 5, 2023
It now used a 514-bit large destination string to hash into. New name: `from_blake2b`. Resolves: #137
moCello
added a commit
that referenced
this issue
Dec 5, 2023
It now used a 514-bit large destination string to hash into. New name: `from_blake2b`. Resolves: #137
moCello
added a commit
that referenced
this issue
Dec 5, 2023
It now used a 514-bit large destination string to hash into. New name: `from_blake2b`. Resolves: #137
moCello
added a commit
that referenced
this issue
Dec 5, 2023
It now used a 514-bit large destination string to hash into. New name: `from_blake2b`. Resolves: #137
moCello
added a commit
that referenced
this issue
Dec 5, 2023
It now used a 512-bit large destination string to hash into. New name: `from_blake2b`. Resolves #137
moCello
added a commit
that referenced
this issue
Dec 5, 2023
It now used a 512-bit large destination string to hash into. New name: `from_blake2b`. Resolves #137
moCello
added a commit
that referenced
this issue
Dec 5, 2023
It now used a 512-bit large destination string to hash into. New name: `hash_to_scalar`. Resolves #137 Co-authored_by: Victor Lopez <victor@dusk.network>
This was referenced Dec 8, 2023
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
With the latest discussions in #129 it makes sense to use these findings when generating a scalar from an arbitrary array of bytes using blake2b as a hash.
The text was updated successfully, but these errors were encountered: