drum55

You can’t submit a PR because your laptop is too slow? Rent some hash rate from someone, and now you’ve just made a system of paying botnet owners to be able to make a typo fix on a github repo. HashCash was never used in the real world for a reason, it sounds cute but the incentives are so insane as to only work in a vacuum where you assume everyone isn’t cheating.

Time crystal detection? 100% Accuracy? Give me a break.

If it's an actual product who knows, sort of hard to care when the website came from a Claude prompt.

It’s like saying a bicycle is a serious contender to a train, they both have kind of similar things going on but you’d have to be insane to suggest that they do as good of a job as one another at the things people actually want to achieve.

Modern bitcoin miners do a double sha256 hash and increment in just a little bit more than a single hash of work. The input is 80 bytes, which is two compression rounds of 64 bytes in sha256, only the data in the second round has changed (the appended nonce), so you don’t bother doing the first compression round again. With other quirks you can end up doing multiple hashes at once “asicboost” due to partial collisions within the input too.

    for (; ;) {
        const hashBuffer = await calculateSHA256(data + nonce);
        const hashArray = new Uint8Array(hashBuffer);

        let isValid = true;
        for (let i = 0; i < requiredZeroBytes; i++) {
          if (hashArray[i] !== 0) {
            isValid = false;
            break;
          }
        }

If LiPo was the issue, using LiFePo4 or LTO cells for planes would be a totally reasonable alternative too. LTO cells are so safe the manufacturer of them has videos on youtube of them hammering nails into the cells, cutting them with a saw, and crushing them with a press and they don't really care.

Bitcoin mining is a partial second preimage of 0x00 though, not a collision, that statement just seems to be so outside the realm of what they’re claiming to have done. Even MD5, the most widely known to be broken hash, would be secure when used in the same way bitcoin uses SHA256 (other than being too short now, bitcoin miners have done 80 bits of work at this point many times over).

Seems like an admission they’ve not really read the code either.

That's because it's in the .gitignore.

It's just very obviously made with claude, from the style, to the commits of tens of thousands of lines of code a day, to the parts where Claude commits something sensible and the author goes back to add in curse words. Nobody has ever developed software in the same way that claude tends to, where suddenly a whole readme appears in a commit fully formatted and filled with emojis.