Shared / Multisig / Sharded IPNS Keys

未关闭
#416 3 条评论 2 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 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 内容生成。

描述

need/community-input

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

主要语言
HTML
星标
1.2k
派生
250
PR 合并指标
30 天内没有已合并 PR

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

ipfs/specs 的其他 Issue

查看 ipfs/specs 的全部 Issue

相似的 Issue

更多 Cryptography Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。