Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

MCP: print each merchant's payer address on start when there is no vault

未关闭
#27 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
69/100
Issue 类型
功能
描述清晰度
描述清楚
活跃度
活跃
技术栈
typescript
领域
api, backend

调研方向

Find the MCP server startup path, budget_status implementation, and paid_fetch error handling; the issue does not name specific files. Trace how burnerPayers(seed, …) derives each merchant address, then check the relevant tests. Done when startup prints each payer to stderr only when no vault is set, budget_status includes the address, the failure message is updated, and tests verify the printed addresses.

由索引模型根据 Issue 内容生成。

描述

enhancement good first issue

Why

Without a vault, the MCP server derives one payer address per merchant from AGENT_PAY_BURNER_SEED, and the user funds those addresses. Nothing shows which addresses to fund.

What

  • On start, when vault is not set, print to stderr one line per merchant: payer for <origin>: 0x… (stderr only: stdout is the MCP channel).
  • Include the payer address in budget_status output too.
  • Tests: the addresses printed match burnerPayers(seed, …) for each merchant.

Also small: when paid_fetch fails for a URL that is not an approved merchant and the request itself fails, say so (Request failed (not an approved merchant, no payment attempted): …).

主要语言
TypeScript
星标
0
派生
0
平均合并
1 小时 37 分钟
30 天内合并 PR
2

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

DeepFirstHQ/deepfirstsearch 的其他 Issue

查看 DeepFirstHQ/deepfirstsearch 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。