ipfs/kubo

ipfs name resolve '-k' option unecessary

Open

#3,900 建立於 2017年5月5日

在 GitHub 查看
 (7 留言) (0 反應) (0 負責人)Go (13,906 star) (2,725 fork)batch import
help wanted

描述

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

貢獻者指南

技術棧
go
領域
clideveloper experience
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
Go programmingIPFS namingCLI argument handling
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
60
研究方向
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.