libp2p / libp2p/go-libp2p-pubsub
[Roadmap issue] Short-term hardening
Open
Nobody has claimed this yet.
req:ethereum
req:filecoin
- Dominant language
- Go
- Stars
- 364
- Forks
- 221
- PR merge metrics
- No merged PRs in 30d
Description
Features needed by Filecoin and ETH2, in order of priority:
- Expose the peer that propagated the message to us (#218)
- Subscription options, which enables...
- Topic handles (#198), so we can...
- Configurable per-topic max message sizes (#209).
[ ] Duplicate consumption (#216), which is blocked by...[ ] Validator cache (we don’t want to validate dupes over and over again, requires message signing to be enabled).- Configurable outbound peer queue sizes (#217).
- Make Publish() report problems / coalesce queued messages (#217).
- Mark topics as relay-only (#28).
- Relative prioritization of traffic per topic (needs to be designed and thought carefully) (#210).
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 unresolved linked issues: #209, #217, #28, and #210, with particular attention to the Publish() entry point mentioned in the roadmap. The issue is complete only when one selected hardening item has a defined scope, implementation, and verification; the roadmap itself does not specify a single contribution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100