ipfs/kubo

announce custom protocol in `ipfs id`

Open

#10817 opened on May 24, 2025

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Go (13,906 stars) (2,725 forks)batch import
P2exp/intermediatehelp wantedkind/enhancementtopic/libp2p

Description

Checklist

  • My issue is specific & actionable.
  • I am not suggesting a protocol enhancement.
  • I have searched on the issue tracker for my issue.

Description

when using ipfs p2p listen, append announce custom protocol in ipfs id, following https://github.com/libp2p/specs/tree/master/identify . it can help nodes recognize protocol provider and to build service over ipfs

  • append announce custom protocol when using ipfs p2p listen
    • flag to disable announcing it

by the way:

  • set --allow-custom-protocol flag true
    • stop announcing protocol '/x/'

Contributor guide

Tech stack
go
Domain
backend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
basic understanding of IPFS and libp2pGo programming knowledge
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45
Research direction
Examine the implementation of the 'ipfs id' command in the kubo codebase (likely in core/commands/). Understand how current identity is announced. Also look at the 'ipfs p2p listen' command to see how custom protocols are handled. Investigate the libp2p identify spec to understand how custom protocols should be announced. Consider adding a flag to disable announcing. The issue is open for discussion; check any comments for maintainer feedback.