BLAKE3 VS bls-signatures

> might be easier with a public domain license instead of the current ones

There reference implementation is public domain (CC0) or at your choice Apache 2.0

https://github.com/BLAKE3-team/BLAKE3/blob/master/LICENSE

Fyi, blake3 was released in 2019 and should probably be used over blake2 unless you have some strong reason not to. It's basically a reimplementation of blake2 with performance tweaks.

https://github.com/BLAKE3-team/BLAKE3

Many people will argue that today's compilers are so smart/optimized that you'd be a fool to try to outsmart the compiler with asm. I'm not 1 of them, but I know some. IMO it's all a bunch of bullshit, there's a goddamn reason all the cryptocurrency mining CPU/GPU code is all hand-written asm. there's a reason blake3 is written in asm ( https://github.com/BLAKE3-team/BLAKE3/blob/master/c/blake3_sse41_x86-64_windows_msvc.asm ) - but the thing is, 99.99% of the time, life is too short to outsmart the compiler (unless you're Alexander Yee)

I have been trying to optimize my code to create a fast hashing function to create and check b3 file integrity but b3sum is way way faster than my aproach, i have been trying to modify my code acordingly to https://github.com/BLAKE3-team/BLAKE3/blob/master/b3sum/src/main.rs with no luck, so if anyone can give me some tips/clues on how to achieve better speeds it would be incredible. Thx!!

BLAKE3 might be faster than KangarooTwelve and is also an XOF. It doesn't have the benefit of getting a working RFC draft proposal however.

You're saying the hash speed is 133 kB/s? That's extremely slow, for example BLAKE3 achieves 6.8 GB/s which is over 50000 times faster. Nobody wants to use such a slow hash function.

Try this one if you want a smaller, and particularly interesting crate: https://github.com/BLAKE3-team/BLAKE3

blake3 is a cryptographic hashing function, which is used during plotting's "forward propagation" step

BLAKE3 claims to be faster and more secure than both MD5 and SHA1.

More information: https://github.com/BLAKE3-team/BLAKE3

$ git submodule update --init Submodule 'lib/BLAKE3' (https://github.com/BLAKE3-team/BLAKE3.git) registered for path 'lib/BLAKE3' Submodule 'lib/bls-signatures' (https://github.com/madMAx43v3r/bls-signatures.git) registered for path 'lib/bls-signatures' Submodule 'lib/libbech32' (https://github.com/dcdpr/libbech32.git) registered for path 'lib/libbech32' Cloning into '/home/plotter/chia-plotter/lib/BLAKE3'... Cloning into '/home/plotter/chia-plotter/lib/bls-signatures'... Cloning into '/home/plotter/chia-plotter/lib/libbech32'... Submodule path 'lib/BLAKE3': checked out '037de38bfec4e813ab6189a50cb7c4cbae47268a' Submodule path 'lib/bls-signatures': checked out 'd9e42922e4a21fe8fc50733b93c16f582022621f' Submodule path 'lib/libbech32': checked out '954b14fe81602dde0cf5cb6d45208403160fb76c'

Enter the directory and execute some necessary commands to install requirements and compile the tool: $ git submodule update --init Submodule 'lib/BLAKE3' (https://github.com/BLAKE3-team/BLAKE3.git) registered for path 'lib/BLAKE3' Submodule 'lib/bls-signatures' (https://github.com/madMAx43v3r/bls-signatures.git) registered for path 'lib/bls-signatures' Submodule 'lib/libbech32' (https://github.com/dcdpr/libbech32.git) registered for path 'lib/libbech32' Cloning into '/home/plotter/chia-plotter/lib/BLAKE3'... Cloning into '/home/plotter/chia-plotter/lib/bls-signatures'... Cloning into '/home/plotter/chia-plotter/lib/libbech32'... Submodule path 'lib/BLAKE3': checked out '037de38bfec4e813ab6189a50cb7c4cbae47268a' Submodule path 'lib/bls-signatures': checked out 'd9e42922e4a21fe8fc50733b93c16f582022621f' Submodule path 'lib/libbech32': checked out '954b14fe81602dde0cf5cb6d45208403160fb76c' $ ./make_devel.sh This command will produce a lot of output while compiling. In the end, you should get a message indicating the compile was successful: [...] [ 98%] Built target relic_s [ 98%] Built target gmock_main [ 98%] Built target UnitTests_bech32 [ 99%] Built target bls [100%] Built target chia_plot Try to call the program and get the usage help information: $ ./build/chia_plot --help If you can see the following line in the output, you have successfully built the chia-plotter version compatible with pool plots: -c, --contract arg Pool Contract Address (64 chars) Getting your keys sorted and jumping in the pool With the binary in place, it is time to check for the data required to create plots that fit your chia keys. To get those keys, execute the following commands: $ chia plotnft create -u https://farm.pool.garden -s pool It can take a little while until the transaction is confirmed. Once it is, execute: $ chia plotnft show Find the P2 singletom address (pool contract address) and save it for later - it should look something like this: P2 singleton address (pool contract address for plotting): xch1es7mmxmgxkv67q69m8j9p5akxk4zhv7h45hxvp*****k4q7527tqu6xhhc (64 characters) The other required key is the "Farmer public key". Execute the following statement to get it: $ chia keys show Note the Farmer public key and save it for later. Ignore the "Pool public key"! It is not the droid you're looking for.