2 ms·
> However, not all applications require a blockchain. Exactly. However: > Services such as social networks could link the user's account to their global ident
by rvz 5y ago
> However, not all applications require a blockchain.
Exactly. However:
> Services such as social networks could link the user's account to their global identity by providing a signed document proving the user's public key is tied to a certain account, or users can do this on their own by providing a public cryptographic proof on their account. (Keybase)
Yet Keybase kept your private key on their cloud for 'convenience' purposes. If you decide to manage the keys yourself, well you're probably more likely going to lose it. Hence, maybe that is why it didn't take off at all and even after they got acquired.
As for 'blockchain application' is that also why Skiff [0] exists and supports using ENS for identities and will still work even after Skiff shuts down? [1]?
[0] https://skiff.org/ https://skiff.org/
[1] https://skiff.org/blog/skiff-x-ethereum-naming https://skiff.org/blog/skiff-x-ethereum-naming
- rodonn 5y agoThis is not true about Keybase. They do not ever store your private key on their servers https://book.keybase.io/security https://book.keybase.io/security "Your private keys are only stored on your devices. For extra security, your private keys are only stored on the device(s) you use Keybase on. They’re not even stored on Keybase’s servers. So if Keybase gets hacked, the security of your account isn’t compromised."