3 ms·
Theoretically a good idea, practically there are couple challenges with it- 1. Some one makes an intermediary service where they allow users to get the age ver
by sandeepkd 1y ago
Theoretically a good idea, practically there are couple challenges with it-
1. Some one makes an intermediary service where they allow users to get the age verification from them. Get the information from the user provided to them by merchant, use their own (service providers) bank account to get the token and return back to the user. Identity less age verification is not practically possible, somewhere down the line you have to peg the identification for the user with a common identifier that services can mutually trust.
2. WebAuthn flow has timeouts (everyones spec implementation might be different) associated with it, most people are going to run into that
- jwally 1y agoFair point on the timeout. Webauthn ties the public keys to your device; chases signature of it verifies it; your webauthn authentication of chases signed version of your key proves it was you the whole time. Nested dolls/Chain of custody. What am I overlooking?
- sandeepkd 1y agoChase signed a key that was provided to it, and chase verified for that user who logged in to chase. For whom the key was generated for and who entered in the chase site/api can be altogether two different entities. This is where it breaks. And chase like banks do not have any practical reason/motivation to provide such a functionality where they are vouching for something but dont really control how that information is used. The legal would never approve it, there is nothing but risk in it for them.