Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add ethereum adress to allow for smart contract verification of identity #7560

Open
veqtor opened this issue Jun 28, 2017 · 6 comments
Open

Comments

@veqtor
Copy link

veqtor commented Jun 28, 2017

If keybase would let users add an ethereum adress, it could be used to verify the identity on the ethereum blockchain using oracle services like oraclize.
This would help a lot of smart contracts that would require a reputation system, for example querying reddit post karma, etc to provide a somewhat working proof-of-individuality

How this would work:
User adds ethereum adress
User calls contract with ethereum adress
Contract calls oraclize (or other oracle)
Oraclize calls keybase
Oraclize returns adress to contract
Contract can call oraclize to determine scoring using keybase data

@veqtor
Copy link
Author

veqtor commented Aug 17, 2017

Anything happening with this? Really need it

@tommorris
Copy link

This broadly duplicates #4266.

Other cryptocurrency issues: #6208 (Monero), #5788 (reusable payment codes), #7042 (altcoins).

This was referenced Oct 6, 2017
@REPTILEHAUS
Copy link

Second this, would really love to see it asap

@ensingerphilipp
Copy link

ensingerphilipp commented Feb 27, 2021

Edit:
misunderstood OP

@junderw
Copy link

junderw commented Feb 28, 2021

Oraclize can do this already.

  1. They run a Bitcoin node to verify the merkle root commitments from Keybase embedded in the Bitcoin blockchain.
  2. They tell keybase users to run some commands to sign an ETH address and upload to their public folder. This message should also be cross-signed by the ETH address's private key as well. (To prove you control both)
  3. They download the signed data from the user's keybase, verify the signatures, verify the state hash, calculate the merkle root, verify the merkle root embedded in Bitcoin.
  4. Cache this info on their side with references to all the data that is needed to quickly verify the signature's link to the Bitcoin blockchain. Maybe periodically check it, or just check it once and store the address to keybase user mapping on a contract somewhere etc.

That said, keybase could make this process easier for them by offering a simple API for fetching and getting data related to the merkle root and a given leaf, and they could lower costs a ton by just taking keybase's word on it and not running a Bitcoin node... (defeating the purpose of keybase to begin with... but whatever floats your boat)

@ensingerphilipp
Copy link

@junderw I misunderstood the issue - I was actually just looking for a way to add my ethereum address to keybase (no need to verify if i hold the private key)

As you posted on another issue in 2019:
Bitcoin and ZCash addresses are just signed by your keybase keys. Keybase does not verify you hold the private key.
--> Why is no such option available for ethereum addresses?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants
@tommorris @veqtor @REPTILEHAUS @junderw @ensingerphilipp and others