libp2p / libp2p/specs

Allow attaching peer routing records to other peer routing records.

Open
#306 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement needs review
Dominant language
No language data
Stars
1.8k
Forks
320
Avg merge
11d 15h
Merged PRs (30d)
1

Description

Currently, when advertising relay addresses, we advertise /relay/transport/p2p/QmRelay/p2p-circuit. Unfortunately:

  1. This means we need one entry in our peer record per relay address.
  2. These relay addresses are not certified by the relay itself.

Proposal:

  1. Advertise relay addresses as simply /p2p/QmRelay/p2p-circuit.
  2. Allow attaching additional peer records to a peer record. Peers using relays would attach the relay's peer record to their own.

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

The issue names no files, tests, or entry points. Start by locating the peer-record and relay-address specifications, then determine how attached peer records and the proposed relay address form should be represented. Done means the specification defines both behaviors and their certification implications clearly enough to implement.

Written by the indexing model from the issue text.

Assessment

Domain
networking
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.