4 ms·
This is amazing. A true proof of work. Have you considered finding hashes with leading zeros or making sure each hash starts with 1337?
by haute_cuisine 9mo ago
This is amazing. A true proof of work. Have you considered finding hashes with leading zeros or making sure each hash starts with 1337?
- keepamovin 9mo agoNo but perhaps you can create at git-coin command? I added three new options --difficulty <leading zeroes> --prefix <leading digits> --hex-prefix <leading hex digis> Be warned tho, this makes it excessively hard. It takes a long long time.
- haute_cuisine 9mo agoWow, that's fast. Do you know if committer's email also goes into calculation of a git hash? If it is, it should be possible to manipulate git hash in a very discrete way through the email address like this: user+<nonce>@example.com
- keepamovin 9mo agoYes author is hashed i believe.
- Retr0id 9mo agoThis already exists btw https://github.com/tochev/git-vanity https://github.com/tochev/git-vanity
- brw 9mo agoWhat about changing the committer timestamp slightly until you find a match like https://github.com/mattbaker/git-vanity-sha https://github.com/mattbaker/git-vanity-sha? That would make it entirely invisible
- keepamovin 9mo agoI don't like that. I want time the canonical when something happened, and metadata surfaced explicitly in an appropriate place. Zero fakery, zero bullshit, zero magic. That's what I want.