BLAKE3 VS collapseos

> 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

Something like this is probably a lot more realistic than (as fast) "integrated circuits at home" : http://collapseos.org/

http://collapseos.org/

I know the point of it isn't to run on new hardware, but this would be a way to learn it on a stable platform without having to worry about dealing with constant problems from old hardware before trying to implement it on said.

There is something called Collapse OS I read about here on HN:

http://collapseos.org/

I myself am a collector of old devices, having raised three kids plus being a web dev. Hate throwing them away too I was just think about this today could I extract the CPUs or RAM or something to reuse rather than destory for the metals. I'd like to learn more hardware but no time.

Some hope for Colapse OS [1] perhaps?

[1] http://collapseos.org

http://collapseos.org/

Here is a quick guide to the science for those with the brain worms:

Maybe start with sufficient support for a simple OS that allows you to edit and compile programs. Something like FreeDOS or CollapseOs. Once you have that working you can extend it.

During collapse we'll all be using Dusk OS and post collapse we'll be using cobbled together rugged computers running on Collapse OS. I imagine at that point we can probably put the sub name to a vote. Maybe "r/ordinarylife".

Not Linux....but you could just install Kolibri OS for a very light desktop or consider CollapseOS and DuskOS....think Dusk should run bare metal on now and won't be too bloated, but there's always CollapseOS if you prefer to keep things light