BLAKE3

[sergeevabc]

Dear @rhash,

BLAKE3 seems to be capable to replace the whole zoo of MD5/SHA1/2/3/Blake2 flavors to check files for malicious changes, while xxHash 128 is a relevant CRC32 replacement for catching accidental changes (e.g. network transmission errors and data rot). This consensus is maturing as we speak. (cc: @Cyan4973)

Alas, b3sum, the official CLI implementation of BLAKE3, has a serious drawback related to memory management and its devs are far from fixing it (cc: @veorq). So until now I’ve been fortunate to use the advantages of this algorithm mainly thanks to GUI apps such as RapidCRC by @OV2 and HashCheck fork by @idrassi. I believe a proper CLI implementation would benefit the community.

Be kind to add BLAKE3 (and sooner or later xxHash 128) to RHash, please.

[data-man]

Non-optimized and public domain https://github.com/michaelforney/blake3-tiny

[ghost]

@sergeevabc
There's a third GUI implementation - TurboSFV (which, incidentally, also has a neat CLI version). It's pretty fast, I think the fastest out of three.

[ghost]

Btw, I have done some tests, and according to my results TurboSFV cli version is x2 faster than RapidCRC, and about 40% faster than HashCheck. Not trying to promote turbo software, which is not free.

[QuAzI]

Still looks like Blake3 most perspective and fast to check files

[AxelPetermann]

Also vote for blake3 implementation