Add Reusable Payment Codes (BIP47)
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Associating a single bitcoin address with a Keybase identity lends itself to address reuse and loss of financial privacy. Reusable Payment Codes were created to allow a Bitcoin user to publish payment information without compromising privacy.
Technical details of the protocol are located in BIP47. Relevant to Keybase verification requirements is the payment code notification address, which may be derived from the payment code itself. The user would simply sign a message with the private key of that payment address.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked BIP47 specification, focusing on reusable payment codes and the payment code notification address. Trace how Keybase verification currently handles Bitcoin addresses and signed messages; done should include a defined integration path for publishing payment information and verifying ownership without address reuse.
Written by the indexing model from the issue text.
Assessment
- Domain
- blockchain, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100