keybase / keybase/keybase-issues
Coinbase "proof" messages are ambiguous - suggest stating exact field to put proof into
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
Issue topic states it all. It is ambiguous now where to put the proof on Coinbase profile pages.
Where to put it in the settings page is ambiguous - it may be prudent to, instead, state that the proof should go in the Public Key field on coinbase profile settings page.
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
Review the Coinbase proof instructions for the profile settings page and locate the wording that tells users where to place the proof. Update it to name the Public Key field explicitly, then verify the published guidance no longer leaves the destination ambiguous.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100