Shared / Multisig / Sharded IPNS Keys
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 18/100
- Issue 类型
- 功能
- 描述清晰度
- 需要澄清
- 活跃度
- 停滞
- 技术栈
- go, javascript
调研方向
从 specs.ipfs.tech/ipns/ 上的 IPNS 规范、main.go 中 threshold-ipns 的先前实现,以及 boxo/ipns 和 js-ipns 参考库开始。解决围绕分片阈值、密钥替换和旧版客户端兼容性的功能问题,同时检查 issue 376。完成标准是确定功能集合,并形成一份包含经过审查的实现指导的 IPIP 提案。
由索引模型根据 Issue 内容生成。
描述
This is a placeholder issue for tracking this topic.
Why
Publishing updates is important.
Being able to do it without dependency on censorable DNS, or paying for Gas to some blockchain grows the pie of use cases IPNS could serve.
Would be beneficial to the IPFS ecosystem if
- https://specs.ipfs.tech/ipns/ includes a golden path spec that is known to work, and has been reviewed by more than one dev
- devs had built-in support and examples in some reference libraries that work with boxo/ipns (go) or js-ipns
- this allows for people to build things that resolve fine in regular clients, without waiting for implementations like Kubo
How (Feature Set)
TBD, topics to discuss:
- could it work with existing spec and legacy clients? (do not require custom signature)
- is the goal to have N sub-keys (shards) and only M required for publishing (M<=N, both >=1), or something else?
- details tbd, the most common ask has been to require min. 2 sigs to ensure peer review before publishing IPNS Record update
- is there a way to replace shards with new ones?
TODO
- gather prior art from community 👈 we are here
- please comment on this issue, ideally with working code or spec draft
- an ideal MVP is to have a solution for the default key type (currently ED25519) what works with legacy IPNS clients (only publisher needs to support multisig)
- If you feel confident in your solution, and want to discuss technical details, proposing IPIP in a PR is appreciated
- decide on feature set
- find a champion to open a PR with IPIP
- wait for https://github.com/ipfs/specs/issues/376 as it needs to happen before anything else
Prior Art
- threshold-ipns by @TheFrozenFire (ed25519 with threshold shards)
- 主要语言
- HTML
- 星标
- 1.2k
- 派生
- 250
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
ipfs/specs 的其他 Issue
-
need/triage
难度 2/5 1-3 小时 新手友好度 68/100
-
need/triage
难度 5/5 一周以上 新手友好度 30/100
-
dnslink:// URIs未关闭need/triage
难度 5/5 一周以上 新手友好度 30/100
-
难度 5/5 一周以上 新手友好度 35/100
-
need/triage
难度 3/5 1-2 天 新手友好度 55/100
相似的 Issue
-
cms: CHOICE types in `SET OF` are ordered as `SEQUENCE OF INTEGER`, not by their bytes可能已有人在做 @brother-z 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 82/100
RustCrypto/formats#2538 · 1 条评论 ·
维护者通常 1 天内回复
-
Decryption panics when importing invalid key components可能已有人在做 @P4suta 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 70/100
-
难度 2/5 1-3 小时 新手友好度 88/100
-
RSA PKCS#1 v1.5 verify fails for SHA-512/224, SHA-512/256 and SHA-3 (UnhandledMatchError on 4.x)未关闭
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100