multiformats / multiformats/multiaddr
Ambiguity in /memory text format
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 482
- Forks
- 87
- PR merge metrics
- No merged PRs in 30d
Description
The /memory multiaddr can contain an arbitrary payload. But if this payload contains a /, then you can't properly serialize it without introducing an ambiguity.
I would propose to revert https://github.com/multiformats/multiaddr/pull/92
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 /memory multiaddr text-format handling and the linked pull request #92. Reproduce serialization and parsing when the payload contains /, then determine whether the ambiguity is resolved; done means /memory payloads serialize and parse without ambiguity, or the proposed change is reverted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100