Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto
  • ¿Algo no está bien?
#12 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python
Área
backend, payments

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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).

Lenguaje dominante
Python
Estrellas
2
Forks
4
Merge medio
5 h 19 min
PR fusionados (30 d)
11

Preparar el entorno

  • Incluye un Dockerfile o un archivo de Docker Compose
  • Sin plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de QMeshPy/distributed-quantum

Todos los issues de QMeshPy/distributed-quantum

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.