refactor(vault-pinning): use the broker and remove NEXT_PUBLIC provider credentials
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 67/100
- Issue 类型
- 重构
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- javascript, next.js
调研方向
Start by reading the Pinata and Lighthouse adapters in services/*.ts and the vault pinning tests in frontend/tests/vault-pinning.test.mjs; check the broker routes from dependency #45. Update the adapters, tests, and docs, and add the production build credential check. Done means the NEXT_PUBLIC_* reads are removed, build output contains no provider credential, and the vault pinning tests pass against the broker.
由索引模型根据 Issue 内容生成。
描述
Summary
Point the Pinata and Lighthouse adapters at the broker routes and delete the browser-side credentials.
Estimated size: S
Motivation
Finishes the credential-safety work started by the broker.
Current state in this repo
NEXT_PUBLIC_PINATA_JWTandNEXT_PUBLIC_LIGHTHOUSE_KEYare read inservices/*.ts;frontend/tests/vault-pinning.test.mjssetsNEXT_PUBLIC_LIGHTHOUSE_KEY.
Proposal
- Adapters call the broker routes through
fetch. - Remove the
NEXT_PUBLIC_*reads, update tests and docs. - Add a short upgrade note: any provider key that was ever exposed as
NEXT_PUBLIC_*should be rotated.
Acceptance criteria
-
git grep NEXT_PUBLIC_PINATA NEXT_PUBLIC_LIGHTHOUSEreturns nothing. - The production build output contains no provider credential.
- Existing vault-pinning tests pass against the broker.
Dependencies
- #45
Testing plan
- Update
frontend/tests/vault-pinning.test.mjs; add a build-output check for the credential strings.
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 小时 54 分钟
- 30 天内合并 PR
- 24
环境准备
- 提供 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 天内回复
-
documentation good first issue kubo storage tier-1
难度 2/5 1-3 小时 新手友好度 42/100
QMeshPy/distributed-quantum#75 ·
维护者通常 1 天内回复
-
feat(provenance): IPFS storage adapter for bundle verification可能已有人在做 @vinayskanse 今天认领。 未关闭enhancement kubo storage tier-2
难度 4/5 3-5 天 新手友好度 56/100
QMeshPy/distributed-quantum#74 · 2 条评论 · 已指派 1 人 ·
维护者通常 1 天内回复
查看 QMeshPy/distributed-quantum 的全部 Issue
相似的 Issue
-
link-rot
难度 1/5 1 小时以内 新手友好度 67/100
-
难度 2/5 1-3 小时 新手友好度 82/100
developmentseed/titiler-cmr#265 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
Insecure Brotli version <1.2.1可能已有人在做 @jamescw19 今天认领。 未关闭
难度 1/5 1 小时以内 新手友好度 85/100
stac-utils/stac-fastapi-pgstac#438 · 1 个 reaction ·
-
bug triage
难度 2/5 1-3 小时 新手友好度 66/100
维护者通常 1 天内回复