I don’t know what you mean by Keybase protocol. Keybase does its own implementation of public proofs. I’ll write my implementation that works with the blockchain.
Social X does NOT require a user to have a Keybase account.
We are talking about public social network identities here. If you are not comfortable with disclosing them, then don’t.
It’s a technical detail that will be disclosed when implementation is finished.
laudney Thanks for taking the time to create this topic and answer questions. Reading explanations like this makes me feel that Reddcoin is right at the cutting edge of technology and finance. It’s fascinating to see it all unfold.
Regarding questions 1 and 2: That’s kind of what I thought but your response really clears things up.
Regarding question 3: My main concern is associating all of a user’s social network identities to each other by linking them to a single address and storing that information on the blockchain. I guess it will be possible to just link a different Reddcoin address to each identity in order to avoid associating any of the identities with each other?
GrayPhoenix Very good questions. The implementation will allow one to associate an arbitrary set of social network identities with a single Reddcoin public key, which means one can associate all her identities with one key, or several different subsets of identities with several different keys or one different key for each identity. As you wish.
GrayPhoenix Domain names are supported. Their ownership can be proved publicly and cryptographically by storing signatures in TXT DNS records. As for emails, I’m afraid that there is no way to achieve that. The best one can do is to trust a central authority who sends email confirmation for authentication, which is out of the scope of our decentralised design.