“This user has been verified to be at least [Age]. Sincerely, [Government Authority]” Assuming this is an identical token thats the same for everyone? Sure. I’m not opposed to this.
“This user has been verified to be at least [Age]. Unique Token ID: 23456” Hell No. When the government eventually wants to deanonymize someone, they could ask the website: “What was the token ID that was used to verify the user?” then if the website provides it, now the government can just check the database to see who the token belongs to. And this could also lead to the government mandating the unique token id to be stored.
/cdn.vox-cdn.com/uploads/chorus_asset/file/25763157/2185229698.jpg)
Depending on what the token contains.
There are two implementations I could think of:
“This user has been verified to be at least [Age]. Sincerely, [Government Authority]” Assuming this is an identical token thats the same for everyone? Sure. I’m not opposed to this.
“This user has been verified to be at least [Age]. Unique Token ID: 23456” Hell No. When the government eventually wants to deanonymize someone, they could ask the website: “What was the token ID that was used to verify the user?” then if the website provides it, now the government can just check the database to see who the token belongs to. And this could also lead to the government mandating the unique token id to be stored.
Why not just look up how it actually works in the real world instead of hypotheticals