-
Notifications
You must be signed in to change notification settings - Fork 37
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
Feature Request: Bitcoin Signed Message For Confirming! #1400
Comments
+1 It seems to me that the Bitcoin proof is somewhat lacking when compared with other keybase methods of proof. Other methods include a public broadcast of a message signed with the private PGP key. Right now there is no broadcast set up for the Bitcoin proof. Maybe a message signed first by the PGP key and then the Bitcoin secret key could be posted somewhere as Muhammad suggests? Perhaps a keybase receiving BTC address could be set up which would receive some satoshis (proving ownership of the BTC private key) with a comment attached to the transaction that contains a hash of a proof posted somewhere else?? |
That would be good but most of them doesn't like to spent their BTC for this. So first signing with BTC address and then signing it with PGP or vice-versa would be good.
|
I agree Bitcoin should be verified as weil. |
+1 I think this should at least be an option. |
Hello,
When I made a confirmation about the BTC address, only PGP signed message was asked. I feel this isn't a good idea. To prove the ownership of the address, I think it is good to ask a Bitcoin signed message. It should atleast include : Date of current day and a code. This can be posted in any of the verified networks(Github, Twitter or Reddit suggested) and verify it and put a link to the post. Else, this can be done by storing it within the system and put a link to it similar to PGP public key(https://keybase.io/kzm279/key.asc), https://keybase.io/kzm279/btc_signed_message.asc. Looking forward to suggestions/opinions.
Kindly,
Muhammed Zakir
The text was updated successfully, but these errors were encountered: