libp2p / libp2p/js-peer-id

Does a peer id require the private key and the public key to be carried around?

Open
#62 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

kind/support status/deferred
Dominant language
JavaScript
Stars
81
Forks
42
PR merge metrics
No merged PRs in 30d

Description

In this implementation of peer, it appears the constructor allows undefined public key and private key, is this meant to be allowed, or is peer id only useful if both pub and priv keys are available?

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 inspecting the peer constructor and the representation of peer IDs to determine whether public and private keys may be absent and what operations require them. Document the intended key requirements and peer ID behavior, with the relevant tests updated or added if the project has coverage for this constructor.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
networking
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.