Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

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

Aperta
  • Qualcosa non va?
#12 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
python
Ambito
backend, payments

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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

Lingua principale
Python
Stelle
2
Fork
4
Merge medio
5h 19m
PR unite (30g)
11

Preparare l'ambiente

  • Include un Dockerfile o un file Docker Compose
  • Nessun modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di QMeshPy/distributed-quantum

Tutte le issue di QMeshPy/distributed-quantum

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.