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
Use cases like blockchain transaction payloads and content-addressable storage have a general requirement that securely hashing equivalent information generates the same hash. Has a canonical sort order for map keys been considered?
(There may be other considerations besides key sort order that prevent generating the same hash.)
The text was updated successfully, but these errors were encountered:
CBOR defines a "canonical encoding" [1] that, among other things, requires:
The keys in every map must be sorted lowest value to highest. Sorting is performed on the bytes of the representation of the key data items without paying attention to the 3/5 bit splitting for major types.
Use cases like blockchain transaction payloads and content-addressable storage have a general requirement that securely hashing equivalent information generates the same hash. Has a canonical sort order for map keys been considered?
(There may be other considerations besides key sort order that prevent generating the same hash.)
The text was updated successfully, but these errors were encountered: