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

Independent identity/reputation check reading MPP credentials — feedback welcome

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

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
20/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
活跃
技术栈
java, python

调研方向

No file or test is named. Start by reviewing the repository's MPP credential and payment-authentication entry points, then compare them with the proposed POST /verify flow and the linked Avel SDK. Done would require a maintainer decision on whether this integration belongs in mpp-java and a defined implementation scope.

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

描述

Sharing a verification layer that reads MPP credentials rather than competing with them.

Positioning up front: this isn't a payment method. Everything about moving money — the charge, the payout — stays on MPP exactly as it already works. What AVEL adds, for agent-to-agent commerce specifically: POST /verify with protocol: "mpp" reads the credential from the HTTP "Payment" auth scheme the agent already produced (EIP-3009 authorization, no extra signature) and returns a verdict plus reputation for both parties, built from real recorded outcomes — never custodies funds.

Fee is 1% of the verified amount, charged on both APPROVED and DENIED (as long as the caller's own signature is valid) — so there's no incentive to just say yes.

Live: https://aisrail.fly.dev. Python SDK + MCP server: github.com/Ensi81/Avel (MIT). Would value feedback from the MPP side on whether this is a sensible complement to the scheme.

主要语言
Java
星标
8
派生
8
平均合并
14 小时 52 分钟
30 天内合并 PR
5

环境准备

  • 提供 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

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

stripe/mpp-java 的其他 Issue

查看 stripe/mpp-java 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 发到你的邮箱

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