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.)
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.)