Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

feat(proposals): quadratic funding rounds for research proposals

Aberta
  • Algo errado?
#17 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
28/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
distributed-systems, python
Domínio
backend, databases, fintech-quant

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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

Linguagem predominante
Python
Estrelas
2
Forks
4
Merge médio
5h 19min
PRs com merge (30d)
11

Preparar o ambiente

  • Inclui um Dockerfile ou arquivo Docker Compose
  • Sem modelo de pull request
  • Sem guia de contribuição

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de QMeshPy/distributed-quantum

Todas as issues de QMeshPy/distributed-quantum

Issues semelhantes

Mais issues de Python

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.