research(bounties): on-chain optimization bounties with verifier contracts

Aberta
  • Algo errado?
#20 2 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
35/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
python, solidity
Domínio
blockchain, fintech-quant

Direção de pesquisa

Start with application/financial_portfolio.py to understand the repository’s QUBO/Ising portfolio representation, then read dependency #2 and roadmap issue #1 for project constraints. Define a compact problem encoding, prototype a verifier on a testnet, and document gas and cost limits, feasible problem sizes, and fixed-point arithmetic. Done means the design and prototype demonstrate one accepted and one rejected submission.

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

Descrição

chain-integration enhancement research-spike tier-3

Summary

Explore bounties for small portfolio-style QUBO problems where anyone submits a candidate bitstring and a contract verifies feasibility and objective value and pays the best solution.

Motivation

Optimization is hard to solve but cheap to verify, which suits an on-chain contract and opens the platform to external solvers, quantum or classical.

Current state in this repo

  • Portfolio problems are QUBO/Ising formulations in application/financial_portfolio.py; there is no external-solver path.

Proposal

  • Define a compact on-chain problem encoding (small N, committed matrix hash with data availability off-chain or in calldata).
  • Prototype a verifier on one testnet (an EVM L2 and, optionally, Starknet) that checks the budget constraint and recomputes the objective.
  • Design the bounty lifecycle: post, submit, challenge window, payout.
  • Write up gas/cost limits and feasible problem sizes.

Acceptance criteria

  • A written design and a testnet prototype with at least one successful and one rejected submission.
  • Limits on problem size and fixed-point arithmetic are documented.

Out of scope

  • Mainnet deployment.
  • Production-audited contracts.

Technical notes and risks

  • Contracts must be treated as unaudited prototypes.

Dependencies

  • #2

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
15h 49min
PRs com merge (30d)
50

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.