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

feat(payments): Uniswap any-token funding and payout-token choice

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
python
领域
backend, payments

调研方向

Start by reading services/proposal_service.py and agentkit_service.py to trace how funding and escrow currently use USDC; also check the chain registry and issues #2 and #3. Confirm Trading API support and routing options for a testnet before choosing an integration path. Done means non-USDC funding meets the escrow and slippage criteria, failed or partial swaps are recorded, and agent caps and token allowlists are enforced with tests and documentation.

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

描述

chain-integration enhancement payments tier-2

Summary

Let users fund proposals or jobs with any supported token by swapping to USDC through Uniswap before escrow, and let workers pick a payout token.

Motivation

Requiring USDC up front is a friction point. Swapping in-flow keeps escrow and accounting in one currency.

Current state in this repo

  • Proposal funding and escrow are USDC-only (services/proposal_service.py, agentkit_service.py).

Proposal

  • Add a swap service that requests a quote and a transaction from the Uniswap Trading API (API key via env), enforces slippage and deadline limits, and executes from the funder's wallet on a registry EVM chain.
  • Add a swap_tokens agent tool that respects agent caps and an allowlist of tokens.
  • Optionally add a payout-token preference for workers (swap USDC to their token after escrow release).
  • Treat the quote as binding only within a short window; re-quote on expiry.

Acceptance criteria

  • Funding with a non-USDC test token results in the exact USDC amount escrowed, within the configured slippage.
  • Failed or partial swaps never leave funds in an unrecorded state (payment events show the outcome).
  • Agent swaps obey per-transaction and daily caps and the token allowlist.

Out of scope

  • Liquidity provision or trading strategies.
  • Mainnet.

Technical notes and risks

  • Uniswap routing, Permit2 approvals and MEV protection options vary by chain. Start on one testnet chain with real liquidity.

Dependencies

  • #2
  • #3

Testing plan

  • Mocked Trading API tests; one scripted testnet swap.

Verify before implementing

  • Trading API availability on the chosen testnet.
  • Unichain chain ids and supported routing types before adding it to the registry.

References


Part of ##1. Ground rules for all issues in this roadmap are listed there (testnet-first, no secrets in the repo, chain logic behind the registry, tests and docs with every PR).

主要语言
Python
星标
2
派生
4
平均合并
6 小时 14 分钟
30 天内合并 PR
18

环境准备

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

从这里开始

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

QMeshPy/distributed-quantum 的其他 Issue

查看 QMeshPy/distributed-quantum 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

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