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

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

Aperta
  • Qualcosa non va?
#20 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, solidity
Ambito
blockchain, fintech-quant

Direzione di ricerca

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.

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

Descrizione

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

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.