multiprotocol: protocol identifiers
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 1.8k
- Forks
- 320
- Avg merge
- 11d 15h
- Merged PRs (30d)
- 1
Description
Had a quick discussion with @raulk, he thought I should mention it here. I've been working on a standard for identifying protocols in a multiaddress like way. The spec can be found here.
There are some issues that still need to be addressed, like being able to specify the transcoder so values can be more than just integers as they are right now. I decided to already open this issue however so it can be discussed transparently on what is still required and if this will be effective for libp2p. It may make sense to standerdize this as part of multiformats and then have libp2p implement its own protocol table.
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
Start by reading the linked multiprotocol specification and the open questions in this issue, especially transcoder support and how the protocol table should relate to multiformats and libp2p. Done requires a resolved design for protocol identification and a clear decision on the specification's ownership and required changes.
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
- Needs clarification
- Newbie friendliness
- 25/100