This would allow people to cat someones peer id. which a lot of people seem to want to do.
Contributor guide
Tech stack
go
Domain
backenddatabase
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.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
Go programmingIPFS architecture basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25
Research direction
First, understand how public keys (e.g., peer IDs) are currently stored in IPFS, likely in the datastore or identity layer. Then, explore the blockstore package (e.g., `blockstore/`) to determine if adding public keys as blocks is feasible. Review existing comments and linked discussions for prior proposals or blockers. Finally, propose a concrete implementation plan, including whether to create a new block type or extend existing ones.
public keys should be added to blockstore · ipfs/kubo#1898 | Good First Issue
