feat(vault): server-side pinning broker routes
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 54/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- next.js, typescript
调研方向
Start by locating the existing /api/vault/pin* and /api/vault/quota/* route handlers, the session authentication and user-scoping code, and the Pinata and Lighthouse service adapters. Then read the route handler tests and run them to understand the current conventions. Done means adding authenticated broker routes for pin, unpin, and quota, with mocked-provider tests for success, auth, size limits, and typed errors that do not leak tokens.
由索引模型根据 Issue 内容生成。
描述
Summary
Add session-authenticated routes that perform pin, unpin and quota calls to Pinata and Lighthouse on the server, so provider credentials never reach the browser.
Estimated size: M
Motivation
Provider tokens are currently shipped to every browser as NEXT_PUBLIC_* variables.
Current state in this repo
services/pinata.tsreadsNEXT_PUBLIC_PINATA_JWTandservices/lighthouse.tsreadsNEXT_PUBLIC_LIGHTHOUSE_KEYin the browser./api/vault/pin*and/api/vault/quota/*only record audit data; they do not call the providers.
Proposal
- Add
/api/vault/broker/pin,/unpinand/quotaroute handlers, authenticated with the existing session and scoped to the user. - Read credentials from server-only env vars (for example
PINATA_JWT,LIGHTHOUSE_API_KEY); choose the provider by request parameter. - Enforce a request body size limit and basic rate limiting.
- Additive only: leave the browser adapters untouched in this PR (they switch over in the follow-up).
Acceptance criteria
- Unauthenticated requests get 401.
- A pin, unpin and quota call succeeds through the broker against mocked providers.
- No provider secret is read from a
NEXT_PUBLIC_*variable on the broker path. - Errors from the provider are mapped to typed responses without leaking tokens into logs.
Out of scope
- Switching the browser adapters over (separate issue).
- New providers.
Dependencies
- None; can be picked up independently.
Testing plan
- Route handler tests with mocked provider HTTP; auth and size-limit cases.
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
-
README.zh-CN/ja/es still hard-code 501 test counts after README.md went count-free可能已有人在做 @Aaqibhafeezkhan 今天认领。 未关闭beginner documentation good first issue
难度 2/5 1-3 小时 新手友好度 75/100
BistaDinesh03/critique#164 · 1 条评论 ·
维护者通常 1 天内回复
-
bug IO
难度 2/5 1-3 小时 新手友好度 65/100
MrNeRF/LichtFeld-Studio#3824 ·
维护者通常 1 天内回复
-
bug confirmed issue
难度 2/5 1-3 小时 新手友好度 72/100
open-webui/open-webui#33200 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 72/100
-
The changelog workflow excludes otelbot but not dependabot, so every Dependabot pull request fails the changelog check可能已有人在做 @ocelotl 今天认领。 未关闭
难度 1/5 1 小时以内 新手友好度 82/100
open-telemetry/opentelemetry-python#5825 ·
维护者通常 2 天内回复