if you're wondering what c++ code I'm referring to, I'm talking about this code I wrote in order to help me find good hashes for the story https://github.com/blackle/Basilisk-Hunter
@snailerotica it's been running on a single thread on my computer for the last year (because if my computer goes idle it crashes for some reason)
surprisingly the smallest hash I was ever able to produce occurred within days of running it full time
@SuricrasiaOnline this is very good
also this is extremely nit-picky but aren't cryptographic hashes designed to be slow
@monorail oh right, that comes almost directly from the beginning of the Cryptographic hash function wiki article https://en.wikipedia.org/wiki/Cryptographic_hash_function
@monorail I think it depends on the hash function, some are designed to be fast and others are designed to be very slow
@monorail the fast ones are good for when you want to hash a giant file to check a signature on it, the slow ones are for passwords/proof-of-work systems
i wouldn't have said anything if it didn't seem like you were going for extremely hard scifi and that caught me off guard, so i'm glad to know it was the me who was in the wrong
@SuricrasiaOnline @monorail there are hash algorithms specifically designed to be slow, mostly to make brute forcing them difficult so you can't e.g. crack a password easily. SHA-256 is not one of these and this is one of the complaints about Bitcoin vs other proof of work cryptocurrencies, which led to e.g. Litecoin using scrypt. That said, the whole concept of burning compute power for, uh, making free money?? is an inherently flawed concept regardless of the proof of work system used.
@SuricrasiaOnline @monorail alternative hashes used sometimes require excessive amounts of memory to make parallelizing them difficult regardless of how fast the algorithm itself is. Funny how there's a bunch of research to make proof of work harder to break, which is ironic considering proof of work is only useful for terrible things in the first place.
@monorail cryptographic hashes for storing passwords absolutely should be slow, though. I think the standard for that is b-crypt?
@SuricrasiaOnline holy shit, even after clicking the link knowing this was fiction I *forgot* partway through and went to consult the sources in amazement. Excellent job.
@SuricrasiaOnline ngl this reads like a good SCP story, and i mean that in a good way
Good god this is well-done
@SuricrasiaOnline I was so excited for the basilisk trashing the shitcoin, and now I only feel emptiness inside.
@leo @SuricrasiaOnline you know seeing other unfiction like this has me thinking about the alameda weehawken burrito tunnel, which has a wildly different tone but is unmistakeably unfiction https://idlewords.com/2007/04/the_alameda_weehawken_burrito_tunnel.htm
@SuricrasiaOnline Great story.
Personal opinion: I think it can be even better with even more technobabbles by mentioning the rumor that its creator has a large quantum computer capable of running the Grover's algorithm, and how cryptographers say it doesn't actually work, first because such a computer doesn't exist, also because it requires XXXX qubits and XXX millions Toffoli gates, also because 256-bit hash still has 128-bit of preimage resistance post-quantum. Nevertheless, you can write that some researchers from PQCrypto 2020 raised the concern that the unknown attack may gain a quadratic speedup on a quantum computer, raising questions to the current belief that doubling the hash size is effective to stop quantum attacks.
You can cite DJB's trolling paper: https://cr.yp.to/hash/quantumsha3-20101112.pdf
@SuricrasiaOnline absolutely love the citation on the speculation that the basilisk collection is from satoshi
@techpriest yeah, I guess it might be wrong to use the layout but I really want the immersion that it provides
I may add a internet-archive-esque banner at the top that clarifies that it's fictional
@unascribed gonna disappear into the mountains with a stack of textbooks on preimage attacks and I'm not coming back until I build the basilisk myself