nice to see libinfnoise working as expected, just want to know if it will switch to blake2b (or blake2x for larger output per hash function call)
looked through the history of SHA3 competition, NIST chose keccak for it's performance in hardware implementation (they even talk about using ASIC...hmm).
For the software implementation blake gives better result (~3 times faster, reference ), let alone blake2 which is significantly faster than blake. blake2x can give up to 256 GiB hash (or up to 4GiB if XOF digest length is set), although it's not finalized but with health checker available it's still a possible choice.
nice to see libinfnoise working as expected, just want to know if it will switch to blake2b (or blake2x for larger output per hash function call)
looked through the history of SHA3 competition, NIST chose keccak for it's performance in hardware implementation (they even talk about using ASIC...hmm).
For the software implementation blake gives better result (~3 times faster, reference ), let alone blake2 which is significantly faster than blake. blake2x can give up to 256 GiB hash (or up to 4GiB if XOF digest length is set), although it's not finalized but with health checker available it's still a possible choice.