If iโ€™m reading this right:

argon2(

argon2(

argon2(bob + first digit), bob + second digit) โ€ฆ ) ?

Reply to this note

Please Login to reply.

Discussion

Argon2 per digit of the number appending hash in each iteration. Not sure how complex that will be, but all you need is to have it compute in 1-3 second on the modern phone ๐Ÿถ๐Ÿพ๐Ÿค”

nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s nostr:npub137c5pd8gmhhe0njtsgwjgunc5xjr2vmzvglkgqs5sjeh972gqqxqjak37w doing 16 rounds of argon2 on (number + first block of the month) and a ratelimit on the server seems like a better choice

If itโ€™s on relay, then there are no limits. I think we are talking public storage of that db ๐Ÿถ๐Ÿพ๐Ÿคฃ

Something like that? ๐Ÿถ๐Ÿพ๐Ÿค”

function hashPhoneNumber(phoneNumber):

hashedValue = ""

for each digit in phoneNumber:

if hashedValue is empty:

hashedValue = argon2Hash(digit)

else:

concatenated = hashedValue + digit

hashedValue = argon2Hash(concatenated)

return hashedValue

I like this. It would be crazy hard to build a table for this, maybe by setting a large iteration security parameter? I would just have an initial salt value just in case this approach gets standardized, but otherwise Iโ€™m leaning toward this. I donโ€™t think you would even need the name to simplify it.

I think so! And we hardest iteration number youโ€™ll make it close to impossible to table for the next 5-10 years, which is sufficient for this level of information ๐Ÿถ๐Ÿพ๐Ÿซก

You all are so fucking smart itโ€™s ridiculous

But as usual, we're solving problems from a technical perspective. ๐Ÿ˜ž

what do you propose to solve this problem?

I propose not to stick with that old "phone number" stuff. Just don't do it, it's not necessary, we have nip05, I.e.

Using phone numbers for nsecs is like using coinbase for #Bitcoin.