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
The name Hash32HexString shows up in many places despite many of these hashes actually being hash28. Presumably this was caused by many of these hashes previously being 32 until some of them were changed to 28 in the binary spec. Since some hashes are 28 and some hashes are 32, it may be simpler to just rename this to not include the length in the name (or you can create a "Hash28" type)
The text was updated successfully, but these errors were encountered:
Yes the opportunity to generalise the label of this scalar to Hash was missed at the 2.0.0 release. We'll consider the best approach to correct this once CIP5 lands.
The name
Hash32HexString
shows up in many places despite many of these hashes actually being hash28. Presumably this was caused by many of these hashes previously being 32 until some of them were changed to 28 in the binary spec. Since some hashes are 28 and some hashes are 32, it may be simpler to just rename this to not include the length in the name (or you can create a "Hash28" type)The text was updated successfully, but these errors were encountered: