Specialized Subset(s) of the Public IPFS Swarm
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 25/100
- Issue 类型
- 功能
- 描述清晰度
- 需要澄清
- 活跃度
- 停滞
- 技术栈
- blockchain
调研方向
首先审查将 Core Node Network 拆分为 core nodes 和 lite nodes 的提案,包括其在兼容性、服务、存储、激励、权限和隐私方面的目标。未指定任何文件、测试或实现入口;除了社区讨论和未来更详细的设计之外,没有定义 done。
由索引模型根据 Issue 内容生成。
描述
We are trying to build a more stable and reliable network in the ipfs public network to improve the efficiency of the IPFS network for online services, which we call "Core Node Network".
The Core Node Network will divide IPFS into core and lite nodes, optimizing the access efficiency of online and offline data, as well as the optimization of data volume storage for different scenarios. At the same time, the Core Node Network is fully compatible with the IPFS public network for full connectivity. We will have more requirements for the nodes joining in the heavy node network (we call them core nodes), such as maintaining stable service delivery and operation in line with expectations. This allows the core node network to provide more stable and fast file services and more reliable file backups.
In addition, we are currently designing incentives for core nodes, permission control system based on core node network and blockchain, and data privacy security design, etc. Some of them have been implemented, but of course there is still a lot of work in progress.
Now we are willing to contribute the design ideas of this network and discuss them with everyone. Any criticism, suggestion or approval will be of great help to us, and if we mention anything inappropriate or have any problems, your suggestions and guidance will be most welcome and appreciated. We are also looking forward to receiving the community's approval and submitting more detailed designs for discussion with you to promote the development of the IPFS community and technology applications.
- 主要语言
- 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
-
难度 2/5 1-3 小时 新手友好度 80/100
blinklabs-io/gouroboros#3026 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
stellar/stellar-etl#512 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 64/100
VelaPayments/vela-payments#223 ·
-
forge: fork preflight reads still send `requireCanonical: false`, which Rootstock rejects (-32603)可能已有人在做 @Ynyesto 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 72/100
foundry-rs/foundry#18485 ·
维护者通常 1 天内回复
-
100 points complexity:trivial drips-wave go good first issue help wanted test
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复