multiformats / multiformats/rust-multiaddr
Consider an inline representation for small multiaddrs
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 101
- Forks
- 56
- PR merge metrics
- No merged PRs in 30d
Description
Similar to https://github.com/multiformats/rust-multihash/pull/47
Using the same approach, for a total size of 64 bytes, you get 62 bytes of data. That is enough to store a multiaddr like /ip4/<32 bit addr>/tcp/<port>/ipfs/<256 bit node hash> or even /ip6/<128 bit addr>/tcp/<port>/ipfs/<256 bit node hash> inline, which should be quite useful.
Rust-libp2p nodes frequently store peer ids multiple times, so this would be a nice optimisation.
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 reviewing the linked rust-multihash pull request and the current rust-multiaddr implementation. Define how a 64-byte inline representation would store the example IPv4 and IPv6 multiaddrs, then verify that the optimization preserves the stated multiaddr data and supports repeated peer IDs.
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