-
samuelgoto catsoo WebAuthn requires the client generated a public key which is stored on a back end system by the site they want to log into. In that sense it is not self contained. In theory you could use multiple clients and have multiple private keys with access to the same account / system...Permalink On twitter.com
Mood +1 🙂
-
samuelgoto catsoo So from the client side a private key is not a 1 to 1 identifier of an account. WebAuthn keys are therefore not unique from the server perspective nor self contained from a client perspective (they can travel with you, but no guarantee)...Permalink On twitter.com
Mood 0
-
samuelgoto catsoo By contrast a wallet is a unique identifier, as, to access what it authenticates you into, you only have one wallet ID and you must carry it with you into every interaction with a login system. And it is self contained in that the wallet is the login entire,...Permalink On twitter.com
Mood 0
-
samuelgoto catsoo With a wallet your ID is understood as a single unique presence on the blockchain and therefore your capacity to brandish it is enough proof of your 1 to 1 identifier that the system you log into need not take further steps than reading it.Permalink On twitter.com
Mood 0
-
samuelgoto catsoo An easy way to understand this is: if you login with your face on an iPhone and a fingerprint on your Android tablet, you are essentially two different private keys. Your single wallet, however, must travel across systems itself in order to do the same process.On twitter.com
Mood +1 🙂