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
Currently we only use the first 40 bytes of the 64 byte hex encoding of the 32 byte SHA256 digest. We should instead use all of the digest i.e. the entire 32 bytes, not hex encoded.
james-chf
changed the title
Use the full SHA256 digest in our Address types
Ensure we're utilizing the full SHA256 digest in our Address types
Aug 21, 2022
james-chf
changed the title
Ensure we're utilizing the full SHA256 digest in our Address types
Ensure we're utilizing full SHA256 digests in our Address types
Aug 21, 2022
Currently we only use the first 40 bytes of the 64 byte hex encoding of the 32 byte SHA256 digest. We should instead use all of the digest i.e. the entire 32 bytes, not hex encoded.
e.g. when generating an
EstablishedAddress
namada/shared/src/types/address.rs
Lines 372 to 386 in d1a06a2
Also see #112 for extra context
The text was updated successfully, but these errors were encountered: