This doesn’t tie your key to your phone number
Discussion
i think it technically does in a reverse search way tho
but i also think that it has utility if you can find a way to do it that is vague enough in its matches to make it a requirement the user scan through a few dozen possible matches, that it isn't completely terrible
ultimately if you are privacy focused you aren't gonna put such a hash on the network, it's for normies with a lower sense of the importance of privacy
This is why I’m trying to come up with a way that makes it computationally infeasible to reverse it.
Range hashes are still on the table, so there would be no exact number
unfortunately i think that's the thing, the less it leaks metadata the more candidates you are gonna turn up, which defeats the purpose
but i do think, regardless, that for building DVMs able to find any kind of data that this kind of cryptography is the way to make it possible for someone with a sufficiently high entropy clue set to match it up to a highly obfuscated data point
broaden your concept of how to generate the match set and balance your expectations with the idea that people who will publish such hashes are maybe putting a bullseye on their backs