multiformats / multiformats/rust-multiaddr
Tooling for unparsable `Multiaddr`
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 101
- Forks
- 56
- PR merge metrics
- No merged PRs in 30d
Description
Sample use-case:
- Roll out of new
Protocol::X. - Old DHT nodes should forward
Multiaddrs withProtocol::Xof new nodes even though they can't parse theMultiaddr. Currently they don't.
Considerations:
- Instead of providing e.g. an
Unparsabletype inmultiaddr, each user that cares could also carry aEither<Multiaddr, Vec<u8>>. - One could add a
Protocol::Unparsable(Vec<u8>)containing the remaining unparsable bytes. This might break existing implementations as they depend onMultiaddreither to succeed or fail, but not fail partially.
Related:
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 proposed approaches in this issue and the related multiformats/multiaddr issue #155. Inspect the current Multiaddr parsing and forwarding behavior, then clarify which representation should preserve otherwise-unparsable protocol bytes and how compatibility should be maintained.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100