feat(vault): open any CID from a link or paste, with trustless-gateway fallback
维护者通常 1 天内回复
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 55/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- javascript
调研方向
Start by reading features/ipfs/lib/helia-init.ts to see how Helia is initialized, then trace the existing vault page and content decoding flow. Implement the CID route, gateway configuration, validation, and verified fetch with mocked gateway tests. Done means a valid remotely pinned CID opens in a fresh profile, invalid CIDs and unreachable gateways show distinct messages, and fetched content is verified before display.
由索引模型根据 Issue 内容生成。
描述
Summary
Add a page that resolves a CID that is not in the local blockstore, so shared results open without the sender's browser.
Estimated size: M
Motivation
Today a CID shared with another user resolves only if they obtain the block by other means.
Current state in this repo
- Helia runs with
createHelia({ blockstore, datastore })and no custom libp2p or block-broker configuration (features/ipfs/lib/helia-init.ts).
Proposal
- Add
/vault/cid/[cid]with a paste box. - Configure the trustless-gateway block broker with a configurable gateway list (env).
- Show a verified-against-CID indicator and cache fetched blocks locally.
- Validate the CID and the decoded record schema.
Acceptance criteria
- A CID published and pinned elsewhere opens on a fresh browser profile.
- Invalid CIDs and unreachable gateways give distinct messages.
- A fetched block is verified against its CID before display.
Out of scope
- Browser-to-browser transports (see the Kubo browser-connectivity issue).
Technical notes and risks
- Gateway choice affects privacy (the gateway sees the CID); document it.
Dependencies
- None; can be picked up independently.
Testing plan
- Mocked gateway tests; one manual cross-profile check.
Part of #43. Ground rules for the content layer: no secrets in the repo, content-layer failures must never block or discard quantum execution, and tests and docs ship with every PR.
- 主要语言
- Python
- 星标
- 2
- 派生
- 4
- 平均合并
- 5 小时 19 分钟
- 30 天内合并 PR
- 11
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
QMeshPy/distributed-quantum 的其他 Issue
-
enhancement good first issue helia storage tier-1
难度 2/5 1-3 小时 新手友好度 78/100
QMeshPy/distributed-quantum#53 ·
维护者通常 1 天内回复
-
chain-integration enhancement payments research-spike tier-2
难度 4/5 3-5 天 新手友好度 55/100
QMeshPy/distributed-quantum#78 ·
维护者通常 1 天内回复
-
chain-integration enhancement payments research-spike tier-2
难度 3/5 1-2 天 新手友好度 66/100
QMeshPy/distributed-quantum#77 ·
维护者通常 1 天内回复
-
chain-integration enhancement payments tier-2
难度 5/5 一周以上 新手友好度 35/100
QMeshPy/distributed-quantum#76 ·
维护者通常 1 天内回复
-
documentation good first issue kubo storage tier-1
难度 2/5 1-3 小时 新手友好度 42/100
QMeshPy/distributed-quantum#75 ·
维护者通常 1 天内回复
查看 QMeshPy/distributed-quantum 的全部 Issue
相似的 Issue
-
bug
难度 1/5 1 小时以内 新手友好度 88/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复
-
documentation
难度 2/5 1-3 小时 新手友好度 84/100
sergey-miryanov/gcmon#230 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
Azure-Samples/azure-search-openai-demo#3249 ·
维护者通常 1 天内回复
-
[BUG] Failed archive extraction deletes the dataset cache可能已有人在做 @dajiaohuang 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
alibaba/GraphScope#4674 ·