

if the dev(s) gets compromised there’s the same issue, except with an extra checkmark on it.
Aspiring polymath.Trying to make things better. Opinions are my own and subject to change


if the dev(s) gets compromised there’s the same issue, except with an extra checkmark on it.


I understand that’s an issue with open source in general, but this specific implementation should be using zero knowledge proofs, which is provable. They are, by definition, provable programs where you can prove properties of data without revealing secrets.
The way this works in practice is:
The nullifier is whats used to make sure someone can’t use their passport more than once on multiple accounts, which is the real tricky part … but there are solutions live and usable out in the world today to mitigate this problem while providing a decent level of privacy.
Really, we shouldn’t have these laws at all, they are fucking stupid…but if we are going to have them, we should at least do it the best we can.


that’s a bit harder if it’s sold out and you want to sell your ticket to your friend/coworker at cost.


they should just ban it for a profit, you should be able to resell tickets for what you paid for them, plans change.


the zk proofs should be generated locally on whatever device you are using. It won’t be any actual photos, it’ll likely be NFC, it depends on verifying the cryptographic signature has signed the data you are trying to prove, and image doesn’t have that.


they said it’s open source, so it should be verifiable, otherwise it definitely shouldn’t be trusted.


you have a pico pencil, not uncivilized
Human review really should be what’s needed, maybe not even just by the package maintainers.