Gonka NOP: ретроактивный грант + финансирование поддержки и новых фич.
Профинансировать gonka-nop — существующий CLI для быстрого развёртывания и обслуживания ноды Gonka: ретроактивно за уже сделанную разработку, за дальнейшую поддержку и за разработку новых функций.
Запрос
50 000 USDT
Ответственный
O D
Подано
13 мая 2026 г.
Advanced vote context
Reviewer median
39.75
Raw score
39.75
Final score
39.75
Reviewer scorecards
| Criterion | Weight | Value | Points |
|---|---|---|---|
Strategic bottleneck Node deployment complexity is a credible strategic bottleneck for a network that wants broader operator participation. The score is not 1 because the proposal itself notes current operators are few and mostly managing themselves, and one community comment questions timing until the next miner wave. Evidence
| 14 | 0.75 | 10.5 |
Network-level leverage An open-source deployment tool can leverage network growth by lowering onboarding barriers for many future operators and standardizing automation for experienced ones. The leverage is plausible but unproven without adoption targets or usage data. Evidence
| 13 | 0.75 | 9.75 |
Measurable impact No measurable project impact criteria are supplied. The tender voting tally is not a success metric for the funded work. There are no baselines or targets for deployments, active operators, support response times, release cadence, reliability, or feature completion. Evidence
| 12 | 0 | 0 |
Team / execution reliability | 15 | Team module | 10.25 |
Scope / deliverables The scope includes meaningful categories, but future deliverables are broad and illustrative rather than binding. The proposal lacks exclusions, milestones, normalized acceptance criteria, and prioritization for the proposed new features. Evidence
| 10 | 0.25 | 2.5 |
Funding structure / tranches The funding structure is a single payment with no vesting, tranches, milestones, holdbacks, or split between retroactive compensation, support, and future development. Evidence
| 9 | 0 | 0 |
Budget discipline The amount is stated, but no rationale, market comparison, staffing estimate, line-item allocation, or cost-per-deliverable is provided. Community comments also flag the amount as possibly high. Some partial credit is given because the amount is explicit and open for discussion in the tender text. Evidence
| 7 | 0.25 | 1.75 |
Incentive alignment Open-source work and 6 months of support are aligned with the network, but the payment is upfront and bundled, includes retroactive compensation and unspecified future work, lacks outcome metrics, and has no structured conflict disclosure. This weakens alignment between payment and delivered network value. Evidence
| 8 | 0.25 | 2 |
Sustainability / handover There is a limited 6-month maintenance promise, but no longer-term sustainability model, handover process, maintainer succession, documentation ownership plan, or plan for what happens after the funded period. Evidence
| 7 | 0.25 | 1.75 |
Governance precedent / opportunity cost The proposal has no explicit opportunity-cost analysis or alternatives. It sets a precedent for a large single-payment package covering retroactive work, support, and broad future development without milestones, which should be evaluated carefully before approval. Evidence
| 5 | 0.25 | 1.25 |
| Raw score | 39.75 | ||
This proposal has a credible network-relevant purpose: a working open-source CLI that lowers the barrier to running Gonka nodes and could improve operator growth and resilience. There is meaningful execution evidence through the existing tool, documentation, demo, and claimed mainnet use. However, it is not ready for strong Community Fund scoring as written because it combines retroactive compensation, 6 months of support, and broad future feature development into a single 50,000 USDT payment with no budget breakdown, no tranches, no milestones, no project impact metrics, no explicit exclusions, no security review plan, and incomplete conflict/maintenance handover disclosures. The main unresolved concerns are not whether the tool is relevant, but whether the amount, payment structure, future scope, and accountability mechanisms are disciplined enough for CommunityPool funding. Reviewer questions: - What exact portion of the 50,000 USDT is for retroactive development, 6-month support, and each future feature area? - Who are the named technical maintainers and what are their time commitments during the 6-month support period? - What concrete milestones and acceptance criteria will govern future work such as GUI/TUI, local monitoring, and Ansible module support? - What measurable success targets will be used, such as number of successful node deployments, deployment time reduction, active operators onboarded, support response time, resolved issues, or releases supported? - Will the DAO receive any milestone-based reporting beyond GitHub activity, and should payment be split into tranches or holdbacks? - What is the security review plan for a tool that installs dependencies, configures Docker/Gonka components, and registers nodes? - What happens after the 6-month support period: who maintains the tool, under what funding model, and what handover documentation will exist? - Are there any affiliations, compensation relationships, or conflicts involving INC4, proposer O D, major voters, node operators, or Gonka core contributors that should be disclosed? - What evidence can be provided for current usage: number of operators, deployments completed, issues resolved, and production reliability? - What alternatives were considered, such as funding only support, funding only specific features, using bounties, or requiring matching/community maintenance contributions?
Optional voter scorecard
Relevant delivery proof
Weight 4
Domain fit
Weight 3
Technical / operational capability
Weight 3
Commitment / capacity
Weight 2
Governance communication
Weight 2
Maintenance accountability
Weight 1
Strategic bottleneck
Weight 14
Network-level leverage
Weight 13
Measurable impact
Weight 12
Team / execution reliability
Weight 15
Scope / deliverables
Weight 10
Funding structure / tranches
Weight 9
Budget discipline
Weight 7
Incentive alignment
Weight 8
Sustainability / handover
Weight 7
Governance precedent / opportunity cost
Weight 5