since @1617 found a flaw with vanityhash in this usecase i …

Hey there 🙈 what's your handcash handle? I want to have you in my friend's list ×_×

How did you work around the \n bug?

i didn’t. either we all agree to use a new fork of the lib or we just make the /n a part of the standard. i was just going with the ladder

$priyan

https://twetch.app/t/01affed24a7fb26a0bdd48fdb5a6ff8bd12e924e16ddf2b6f64555e4647eea79

😂🤣🤣🤣🤣🤣
@1882 give me your handle ×______×

agreed - i think this is up to the 21e8 guys @1623 @9

i have an inkling it’s actually up to *us* :)

vanity... -b 32 -w 2 -d.../hash.txt
Reading input data and adding... done.
Original data: 64 bytes... a2e...429
Searching for 21e8000 at position 0... done.
Match found: 0xfa6f6d2e -> SHA256 21e8000fae712f4f2fbf5b07aee254217f9869cd87e29eaee0538785eb1bdbde

ok, let's do *this* and stick with vanityhash.

coded my own mockup where sha256 of source is based on string not the file. but the solution is based on my company's ide and therefore not publicly available. ->> which is why i vote for using vanityhash.

$tetapsepi