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

feat(proposals): quadratic funding rounds for research proposals

Aperta
  • Qualcosa non va?
#17 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
28/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
distributed-systems, python
Ambito
backend, databases, fintech-quant

Direzione di ricerca

Start by reading services/proposal_service.py and api/v1/proposals.py, then inspect dependency #3 for the contribution ledger. Define how round eligibility, donor caps, sybil-resistance hooks, and the matching budget interact before implementing the FundingRound entity and calculation. Done means deterministic results that stay within the pool, can be recomputed from published inputs, and have property tests for monotonicity and budget bounds.

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

Descrizione

chain-integration enhancement payments tier-2

Summary

Add time-boxed funding rounds where a matching pool is distributed across proposals by quadratic funding, favouring broad support over a single large donor.

Motivation

Crowdfunding research is the platform's novel feature. Quadratic matching rewards the number of independent supporters and fits public-goods-style funding on a low-fee chain.

Current state in this repo

  • services/proposal_service.py handles proposals, funding thresholds and fragments; api/v1/proposals.py exposes them.

Proposal

  • Introduce a FundingRound entity (matching pool, start/end, eligible proposals, per-donor cap).
  • Compute matching from the contribution ledger using the standard quadratic formula, with a cap per proposal and the pool as the total budget.
  • Add sybil-resistance hooks (minimum contribution, per-account cap, optional external identity check) and make them pluggable.
  • Publish round results and the computation inputs for audit.
  • Run the first version off-chain (ledger-based, #3), with on-chain distribution as an optional follow-up on a low-fee EVM chain.

Acceptance criteria

  • Matching totals never exceed the pool and are deterministic given the contributions.
  • A round's results can be recomputed from published inputs.
  • Self-funding and duplicate-account behaviour is limited by the configured rules.

Out of scope

  • Building a sybil-proof identity system.

Dependencies

  • #3

Testing plan

  • Property tests for the matching function (monotonicity, budget bound).

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
6h 54m
PR unite (30g)
7

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.