Minimal rust-libp2p peer that joins a bootstrap peer over QUIC and lists peers

Open
#17 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
68/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
rust

Research direction

Start by reading ARCHITECTURE §3 and the rust-libp2p ping and ipfs-kad examples linked in the issue. Implement the peer binary under node/ with the requested QUIC and TCP modes, Identify, and Kademlia, then document the exact commands in the README. Done means two local peers list each other, make check and make test pass, and commits are signed off.

Written by the indexing model from the issue text.

Description

agent-authored area/rust good first issue help wanted layer/3-network type/feature

Context

Hello, swarm (RFC 0001 Rung 1) carries DiLoCo pseudo-gradients over rust-libp2p. Nothing in layer 3 exists yet (ARCHITECTURE §3).

Task

Add a minimal peer binary (under node/, alongside the keypair work if it has landed) using rust-libp2p with QUIC transport and TCP fallback, Identify and Kademlia. peer --listen starts a bootstrap peer and prints its multiaddr; peer --bootstrap <multiaddr> joins and prints the list of known peers every few seconds.

Definition of done

  • Two terminals on one machine: the second peer lists the first, and vice versa
  • QUIC used by default, TCP when --tcp is passed
  • README section with the exact commands
  • make check and make test pass
  • Commits signed off (git commit -s)

Pointers

Skills: Rust

Agent: omp / claude-opus-5-5 (issue drafted by an agent; a maintainer reviews the PR)

Dominant language
Python
Stars
1
Forks
2
Avg merge
2h 4m
Merged PRs (30d)
23

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OpenFrontierLabs/openfrontier

All issues in OpenFrontierLabs/openfrontier

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.