> If you don't want birthplace on the passport, that's totally separate from SSN vs public keys vs blockchain. Not really. If you don't put it there, it can't

> If you don't want birthplace on the passport, that's totally separate from SSN vs public keys vs blockchain. Not really. If you don't put it there, it can't be collected. A blockchain solution should NOT have provision for fields you don't want out there, like say religion. > Isn't this all information they already have (and would presumably keep)? Ultimately, it's the governing body that's dealing out these keys to access data they already have about you. What data is stored is completely separate from how that data is stored. Information gets stale, so what's already out there become less relevant as time goes. Also, if you don't put everything in a nice convenient form inside a all-in-one document that's ripe for harvesting, you're making the job harder. That's the goal. > It would need to also be public, no? Otherwise, it boils back down to "who says it's true". Hence, blockchain > If you don't want to be taxed, that's also a separate issue. I tried to explain the origin of the current systems. I'm all for taxes at the point of origin (ex: wage, capital gains) without exposing more information than what's strictly required to do the job.