onflow / onflow/flow

Documentation on private keys, public keys, seed phrases, and instructions for the case something got compromised

Open
#936 0 comments 2 reactions 1 assignee View on GitHub

@srinjoyc is already working on this.

Since May 5, 2022.

Docs Site Document Feedback T-Documentation 📃
Dominant language
Go
Stars
361
Forks
159
PR merge metrics
No merged PRs in 30d

Description

There seems to be confusion on how these relate and what to do.

For example, an explanation for the concepts would be great, then a walkthrough (e.g. create new private key (not from potentially compromised seed!), add public key to account, revoke old public from account).

Contributor guide

Open the contributing guide

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.