ipfs/kubo

ipfs name resolve '-k' option unecessary

Open

#3900 opened on May 5, 2017

View on GitHub
 (7 comments) (0 reactions) (0 assignees)Go (13,906 stars) (2,725 forks)batch import
help wanted

Description

We should just be able to resolve named keys by doing ipfs name resolve keyname. Since named keys cannot contain slashes, we can disambiguate them from hashes by an optional /ipns/ prefix on hash keys.

ipfs key gen foobar
ipfs name resolve foobar # should work
ipfs name resolve QmBeepBoop # should check if we have a key named QmBeepBoop, then try to resolve a hash key
ipfs name resolve /ipns/QmBeepBoop # definitely a hash key, don't check for named keys

Contributor guide

Tech stack
go
Domain
clideveloper experience
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-3 hours
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.
mostly clear
Prerequisites
Go programmingIPFS namingCLI argument handling
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Review the current implementation of `ipfs name resolve` in the codebase, likely in the `core/commands/name.go` file. Understand how the ` k` option is handled and how named keys are currently resolved. Then consider modifying the resolution logic to check for named keys before treating the argument as a hash. Ensure backward compatibility by allowing an optional `/ipns/` prefix. Review the comments in the issue for any additional considerations.