> >Truly there are almost zero situations in which an entity needs to know your real identity. > 1000 percent this! > What entities really need to know to do

> >Truly there are almost zero situations in which an entity needs to know your real identity. > 1000 percent this! > What entities really need to know to do their function is shockingly small compared to what they ask for. Here are some examples: > - Bank: proof you are authorized to make decisions for a given bank account. (Possibly jurisdiction info if the government forces banks to screen on citizenship.) > - Voting: proof that you didn't vote twice. (Possibly jurisdiction info if you are only allowed to vote in a specific area.) > - Job: a nickname, contact info, where to send compensation, a way to grant (and revoke when terminated) your access to non-public information. (Possibly jurisdiction info if the government forces companies to screen on citizenship or calculate taxes in a specific way.) > - Social media network: way for others to connect with you (eg email). > - Bars: (possibly proof of age, if the government forces establishments to limit sales on that basis.) > - Online or in-person payments: proof that the funds transferred to the business's account. But for all of these use cases, who would be the provider of these attributes to the third parties? Haven't we already seen issues with centralization of identifying information? (Like the case with the OPM breach?)