Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

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

未关闭
#20 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
python, solidity

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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

主要语言
Python
星标
2
派生
4
平均合并
5 小时 19 分钟
30 天内合并 PR
11

环境准备

  • 提供 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 没有贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

QMeshPy/distributed-quantum 的其他 Issue

查看 QMeshPy/distributed-quantum 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。