3 ms·
I plan to outline exactly what data I store. I don't plan to store raw passport number/name details, rather a hash so I can verify the same passport isn't used
by dom96 2y ago
I plan to outline exactly what data I store. I don't plan to store raw passport number/name details, rather a hash so I can verify the same passport isn't used twice.
So even if the DB leaks no one (except the government) will be able to tie your real life identity to the account.
- ddtaylor 2y agoIn the US there are a lot of companies that do these kinds of identity verification for you. I had to do one when I was setting up a new Steam Developer account and many use them for regular day-to-day verification like for work or when submitting important government requests. It would seem a lot better to just partner with an existing company that takes care of that part of identity verification. Your job is still to compose all of these signals and metrics and distill them into a simple "everyone is human" network, but the actual job of being a passport jockey can be avoided IMO.
- dom96 2y agoYep. I’ve considered doing it myself but it would require setting up an app for iOS and Android. For now relying on existing services will be fine. If this takes off I might set up my own passport verification service.