Closed DHT Based Routing
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 20/100
- Issue 类型
- 功能
- 描述清晰度
- 需要澄清
- 活跃度
- 停滞
调研方向
没有指定文件、测试或入口点。首先审查提案和相关讨论，以确定成员关系、路由表、共识和记录生命周期方面的要求。只有在设计达成一致并确定实施计划后，才能算完成。
由索引模型根据 Issue 内容生成。
描述
Libp2p currently relies on a fully p2p Kademlia DHT. Unfortunately, even if we get it to the point where it behaves optimally, it still won't scale enough to support our content routing needs.
Proposal: Implement a "closed" DHT with known members. Note: This is often called a "Distributed KV Store".
Unlike our Kademlia DHT:
- This system would be permissioned instead of permissionless. Joining as a DHT "server" would require either human or blockchain consensus.
- Have a fixed, well-known routing table, fetched when initially connecting to this DHT.
Motivations:
- 1-RTT lookup
- batch put
- long-lived routing records
Performing a 1-RTT lookup and/or a batch put requires a known routing table. The round-trips in traditional p2p DHTs all come from discovering this routing table along the way.
A known routing table requires some form of consensus on the members of this routing table. That's where the trust comes in.
The last part of this is long-lived routing records. The Internet Archive has ~400e9 files which equates to at least 35TiB of "provider records". However, the IA isn't adding 400e9 files per day. Given stable nodes that can be trusted to keep long-lived records alive, the IA wouldn't have to keep re-broadcasting old records to keep them alive.
Notes:
- Really, we may want to treat large services like the IA as "trackers". However, the current system won't even scale for smaller services.
- We may also want to integrate payment for large users to prevent abuse but we can probably punt on that for now.
CC @Kubuxu, IIRC you already proposed something kind of like this but I couldn't find the proposal.
CC @obo20 as this is really important for pinning services.
- 主要语言
- 没有语言数据
- 星标
- 38
- 派生
- 2
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
libp2p/notes 的其他 Issue
-
难度 5/5 一周以上 新手友好度 20/100
-
难度 5/5 一周以上 新手友好度 20/100
-
DHT
难度 5/5 一周以上 新手友好度 25/100
-
enhancement
难度 5/5 一周以上 新手友好度 25/100
-
难度 5/5 一周以上 新手友好度 25/100
相似的 Issue
-
area-testing p1-recommended
难度 2/5 1-3 小时 新手友好度 66/100
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 83/100
-
enhancement needs-triage
难度 2/5 1-3 小时 新手友好度 68/100
aws/aws-durable-execution-conformance-tests#157 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 74/100
platformatic/mcp#368 ·
维护者通常 1 天内回复