keybase / keybase/client

Create way to do identity proof on memo.cash

Open
#11,587 0 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
9.2k
Forks
1.3k
Avg merge
12h 58m
Merged PRs (30d)
56

Description

https://memo.cash

This popular system desperately needs a way to connect its identifying BCH address (more accurately raw hash160 since multiple address formats are in use) to identities on other systems, and keybase is the perfect way to do it.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the memo.cash system at https://memo.cash and how Keybase currently verifies identities. Define what proof should connect the BCH raw hash160 to an external identity, then document an agreed verification flow and its acceptance criteria before locating implementation entry points.

Written by the indexing model from the issue text.

Assessment

Tech stack
blockchain
Domain
authentication, blockchain
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.