feat(vault-pinning): pin original blocks as a CAR so the pinned CID equals the Helia CID
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 48/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- javascript, python
调研方向
Start by reading the current provider adapters and their JSON-pin paths, then check the broker dependency in #45 and verify the CAR upload endpoints supported by Pinata and Lighthouse. Reproduce CID behavior with provider mocks or a test account before choosing an upload path. Done means tests show both providers return the Helia CID, mismatches raise a clear error, and the JSON path remains available behind a flag.
由索引模型根据 Issue 内容生成。
描述
Summary
Upload the blocks Helia already holds, instead of re-submitting the JSON for the provider to re-encode.
Estimated size: M
Motivation
A provider that re-encodes JSON can return a different CID than the one the user shared, which breaks citation.
Current state in this repo
- Adapters send JSON content to the provider's JSON-pin endpoint.
- The Helia integration overview reports that the returned CID can differ; this has not been reproduced in this repo yet.
Proposal
- Step 1: add a test or script that reproduces any CID mismatch for each provider.
- Step 2: export the DAG with
@helia/carand upload it through the provider's CAR (or Pinning Service API) endpoint; verify each provider's supported endpoint first. - Step 3: fail with a clear error if the CID the provider reports does not match the local CID.
Acceptance criteria
- For Pinata and Lighthouse, the CID returned after pinning equals the Helia CID, checked in a test.
- A mismatch is surfaced as an error, never silently recorded.
- The JSON path remains available behind a flag until CAR upload is proven.
Out of scope
- UnixFS and large files.
Technical notes and risks
- Coordinate with the broker work: if it lands first, upload from the browser to the broker route; otherwise start against the current adapters.
Dependencies
- Soft: #45 (uploads will move to the broker).
Testing plan
- Provider mocks plus one manual run against test accounts.
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
- 平均合并
- 6 小时 54 分钟
- 30 天内合并 PR
- 7
环境准备
- 提供 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
-
难度 2/5 1-3 小时 新手友好度 82/100
volcengine/OpenViking#6445 ·
维护者通常 1 天内回复
-
BUG:Edit Album strips spaces from the password so albums with a leading/trailing space in the password can't be edited可能已有人在做 @ManyaJain111 今天认领。 未关闭bug enhancement possible-duplicate
难度 2/5 1-3 小时 新手友好度 77/100
AOSSIE-Org/PictoPy#1637 · 4 条评论 ·
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 74/100
deepspeedai/DeepSpeed#8884 ·
维护者通常 3 天内回复
-
难度 2/5 1-3 小时 新手友好度 76/100
flagos-ai/FlagQuantum#718 ·
维护者通常 1 天内回复
-
bug CI-failure high priority
难度 1/5 1 小时以内 新手友好度 86/100
vllm-project/afd-plugin#483 ·
维护者通常 1 天内回复