Gonka Community Fund
vote.gonka: открытgovernance: проваленНужны правки

Gonka NOP: ретроактивный грант + финансирование поддержки и новых фич.

Профинансировать gonka-nop — существующий CLI для быстрого развёртывания и обслуживания ноды Gonka: ретроактивно за уже сделанную разработку, за дальнейшую поддержку и за разработку новых функций.

Мнение по proposal

AI-черновик

Что говорит ревью

Gonka NOP appears to be a real, open-source CLI that can reduce friction for deploying and maintaining Gonka nodes. That is plausibly valuable to the network. However, the current ask bundles retroactive payment, 6 months of support, and undefined future features into a single 50,000 USDT transfer with no budget breakdown, no tranches, no acceptance criteria, and weak evidence of actual network impact or usage. The fund should not approve this version as a lump-sum retroactive grant, but it could become fundable if reframed as a smaller, milestone-based maintenance and feature grant with verified adoption/impact evidence.

  • Real and relevant open-source tool exists, but the retroactive impact case is not yet evidenced with usage or outcome data.
  • The current funding structure is a high-risk lump sum with no budget, tranches, milestones, or acceptance criteria.
  • Future support and feature work are bundled into the retroactive request, making scope and accountability hard to verify.
Открыть публичное ревью

Запрос

50 000 USDT

Ответственный

O D

Подано

13 мая 2026 г.

Что думает коммьюнити

AI opinion - стартовая позиция. Ответы ниже помогают другим понять согласие, возражения и готовность голосовать.

Согласен

0

Согласен с условиями

0

Не согласен

0

Нужно больше данных

0

Ваше мнение

Локальное community vote открыто

Можно оставить мнение здесь и проголосовать в локальном community vote до 2 июн. 2026 г..

Отношение к AI opinion
Если голосовать сейчас
Открыть local vote

Все ответы

Ответов пока нет. Можно быть первым.

Proposal простыми словами

О чем это

Профинансировать gonka-nop — существующий CLI для быстрого развёртывания и обслуживания ноды Gonka: ретроактивно за уже сделанную разработку, за дальнейшую поддержку и за разработку новых функций.

Запрос

50 000 USDT

Ответственный

O D

Почему это важно

Профинансировать gonka-nop — существующий CLI для быстрого развёртывания и обслуживания ноды Gonka: ретроактивно за уже сделанную разработку, за дальнейшую поддержку и за разработку новых функций.

Проблема

Профинансировать gonka-nop — существующий CLI для быстрого развёртывания и обслуживания ноды Gonka: ретроактивно за уже сделанную разработку, за дальнейшую поддержку и за разработку новых функций.

Что должно быть сделано

  • Imported tender outcome
Детали оценкиShow
Нужны правкиAI-черновик

Framework score v2

Простое ревью

Gonka NOP appears to be a real, open-source CLI that can reduce friction for deploying and maintaining Gonka nodes. That is plausibly valuable to the network. However, the current ask bundles retroactive payment, 6 months of support, and undefined future features into a single 50,000 USDT transfer with no budget breakdown, no tranches, no acceptance criteria, and weak evidence of actual network impact or usage. The fund should not approve this version as a lump-sum retroactive grant, but it could become fundable if reframed as a smaller, milestone-based maintenance and feature grant with verified adoption/impact evidence.

Доказательства

средние

Команда

есть вопросы

Блокеры

4

Почему такое мнение

  • Real and relevant open-source tool exists, but the retroactive impact case is not yet evidenced with usage or outcome data.
  • The current funding structure is a high-risk lump sum with no budget, tranches, milestones, or acceptance criteria.
  • Future support and feature work are bundled into the retroactive request, making scope and accountability hard to verify.

Пять публичных проверок

2/4

Ценность для сети

The tool targets a real network-level friction point: deploying and maintaining Gonka nodes. Repository and README evidence show a documented CLI with setup, status, update, GPU detection, config generation, and multiple topologies. The network-value case is plausible, but concrete impact is not yet verified beyond proposer-stated claims that some mainnet operators use it.

1/4

Ясность плана

The existing tool is described clearly, and 6 months of support is mentioned in one governance version. But the proposal lacks formal deliverables, exclusions, acceptance criteria, success metrics, milestone schedule, and a verification plan for the retroactive and future-feature portions. The future-feature list is open-ended.

2/4

Доверие к команде

INC4 is named in governance materials and the inc4/gonka-nop repository exists with documentation, workflows, MIT license, and recent activity. That is relevant proof for this technical scope. However, the proposal does not provide named maintainers, capacity allocation, response commitments, escalation path, or a maintenance/reporting cadence beyond 'GitHub is the report'.

0/4

Дисциплина финансирования

The proposal asks for 50,000 USDT as a single payment with no vesting, tranches, budget line breakdown, retroactive valuation method, or opportunity-cost comparison. For a retroactive-plus-future grant, this creates high funding risk and a weak precedent: the DAO would be paying for effort and broad usefulness rather than verified outcomes.

1/4

Риски и stewardship

The repository has some positive hygiene signals, including security workflow and SECURITY.md, and the tool is open source. But the proposal does not adequately handle operational risks, security-review expectations for a node deployment tool, conflict disclosures, maintenance handover, or what happens after the 6-month support period.

Оценка команды

The team has relevant evidence because the inc4/gonka-nop repository and documentation exist. Team confidence is still only moderate because the proposal does not name maintainers, quantify capacity, or define an accountability path beyond the public repository.

Ответственный

ок

Governance materials identify INC4 as the recipient/entity, while the imported tender lists O D as proposer. That is sufficient to avoid a no-owner failure.

Релевантные доказательства

ок

The repository and README demonstrate an existing tool with relevant node-deployment functionality. This is stronger than reputation-only evidence.

Ресурсы и capacity

вопрос

The proposal does not disclose staffing, time allocation, support coverage, or capacity for both support and future-feature development.

Accountability path

вопрос

Using GitHub as a public work surface is helpful, but the proposal has no reporting cadence, issue response expectation, release commitments, acceptance criteria, or escalation path.

Условия

  • Separate the ask into: (1) retroactive payment for verified delivered value, (2) 6-month maintenance/support, and (3) future features. Price each separately.
  • Provide verifiable usage evidence: number of mainnet operators using NOP, successful deployments, before/after setup time, support issues resolved, operator testimonials or signed attestations, and repository release history.
  • Replace the single 50,000 USDT transfer with milestone/tranche payments tied to measurable acceptance criteria, such as release delivery, issue-resolution SLA, documented compatibility with network releases, and adoption targets.

Блокирующие проблемы

  • Нет измеримого результата: The only structured success metric in the imported record is a community/tender vote tally, which is not an outcome metric. There are no adoption, operator, node-launch, support-SLA, issue-resolution, or reliability targets.
  • Нет бюджетной или tranche-логики: A 50,000 USDT single payment is requested without budget breakdown, vesting, tranches, retroactive valuation, or milestone logic.
  • Ретроактивный запрос без доказательств impact: The tool exists, but retroactive payment is not supported by verified usage data, operator testimonials, number of successful deployments, support history, or network performance impact. 'Used by some operators' is proposer-stated in the available materials.
Источники и доказательстваShow

governance 56

DEFEATED

https://gonkascan.com/network/proposals/56

governance 53

DEFEATED

https://gonkascan.com/network/proposals/53

vote.gonka 2cbbe98e-ceff-4f09-a1cd-e8d370e97fde

expired

https://vote.gonka.vip/tenders/2cbbe98e-ceff-4f09-a1cd-e8d370e97fde

Evidence used in the opinion

INC4 | Gonka NOP - grant for the node deployment tool

GitHub discussion #1192 in gonka-ai/gonka: INC4 | Gonka NOP - grant for the node deployment tool; 8871 chars extracted from public HTML fallback.

https://github.com/gonka-ai/gonka/discussions/1192

inc4/gonka-nop/README.md

README.md from inc4/gonka-nop; 10705 extracted chars at ref main.

https://github.com/inc4/gonka-nop/blob/main/README.md

inc4/gonka-nop

inc4/gonka-nop: Gonka AI Node Onboarding Procedure; 24 stars, 1 forks, 1 open issues; default branch main; license MIT; pushed 2026-05-22T16:29:49Z; README extracted (10705 chars); 3 workflow file(s); SECURITY.md present

https://github.com/inc4/gonka-nop

GOVERNANCE source

DEFEATED: INC4 | Gonka NOP - grant for the node deployment tool

https://gonkascan.com/network/proposals/56

GOVERNANCE source

DEFEATED: INC4 | Gonka NOP - grant for the node deployment tool

https://gonkascan.com/network/proposals/53

Governance retry lineage

Possible retry lineage: #53 rejected -> #56 rejected.

https://gonkascan.com/network/proposals/56