Gonka Community Fund

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

О чем это

This proposal introduces new Qwen3 models including Qwen3-32B-FP8 and Qwen3-235B-A22B-Instruct-2507-FP8, along with updating parameters for Qwen2.5-7B-Instruct and QwQ-32B.

Запрос

Governance proposal does not expose a direct transfer ask in the imported messages.

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

Protocol proposer gonka18lluv53n4h9z34qu20vxcvypgdkhsg6nn2cl2d; accountable delivery owner not explicitly provided.

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

Not provided as a dedicated network-level value field. Source summary: This proposal introduces new Qwen3 models including Qwen3-32B-FP8 and Qwen3-235B-A22B-Instruct-2507-FP8, along with updating parameters for Qwen2.5-7B-Instruct and QwQ-32B.

Проблема

Not provided as a dedicated problem/bottleneck field. Source summary: This proposal introduces new Qwen3 models including Qwen3-32B-FP8 and Qwen3-235B-A22B-Instruct-2507-FP8, along with updating parameters for Qwen2.5-7B-Instruct and QwQ-32B.

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

Unstructured governance deliverable

Нужны правкиAI-черновик

Framework score v2

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

This is a protocol-change proposal to register new Qwen models and update model parameters, not a direct funding transfer. It has plausible network value because it expands Gonka-supported model options and gives operators a path to adopt them, with some supporting methodology and data references. However, it is not yet review-ready under the Community Fund framework: there is no named accountable technical owner, no explicit success/monitoring criteria, no rollback or mitigation plan, incomplete blast-radius analysis, and only a summary of the executable messages rather than full inspectable message fields in the supplied evidence. Recommendation: needs revision before community support as a well-stewarded protocol change.

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

средние

Команда

провал

Блокеры

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

Plausible network value from adding new supported models, but the proposal does not establish urgency, alternatives, or measurable outcomes.
The governance action is bounded and has no direct coin transfer, but full executable message contents are not available in the supplied evidence.
No named accountable owner or maintenance path is provided, which is a blocker for a technical protocol change with operator impact.

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

2/4

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

The proposal plausibly creates network-level value by adding or replacing supported inference models, including Qwen3-235B and Qwen3-32B. But the concrete bottleneck, urgency, alternatives, user/operator demand, and opportunity cost are not clearly stated in the governance text.

2/4

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

The proposal names the models and has bounded executable message type information, but it lacks acceptance criteria, explicit monitoring metrics, exclusions, full blast-radius analysis, and a rollback/mitigation plan. The supplied executable-message evidence is summarized, not fully inspectable field-by-field.

0/4

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

No named accountable owner, entity, technical maintainer, reporting path, or capacity commitment is provided. The proposer address is governance context, not sufficient accountability for technical maintenance and post-execution stewardship.

3/4

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

No direct GNK transfer or coin amount is detected, so budget/tranche issues are not central. The remaining funding-discipline concern is governance opportunity cost and operator cost, which are not analyzed.

1/4

Риски и stewardship

The proposal affects model registry/operator behavior but does not identify full blast radius, rollback path, post-execution monitoring, conflict disclosure, maintenance owner, or escalation route. Operational transition is mentioned, but detailed instructions are promised later rather than included.

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

Team confidence is the main blocker. The supplied materials identify a proposer address but not a named accountable owner or maintainer for the model registrations, threshold choices, operator transition, monitoring, or escalation.

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

провал

No named individual, organization, or technical owner is provided; only a governance proposer address is available.

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

неясно

The materials include a technical README and references to methodology, but no evidence tying a specific accountable team to prior similar delivery or operation of this exact scope.

Ресурсы и capacity

неясно

No time, resource, availability, or operational commitment is stated for maintaining the change or supporting operators after execution.

Accountability path

вопрос

The README says instructions will be announced through official channels, but there is no owner, reporting cadence, incident path, or escalation process.

Условия

Name an accountable technical owner or entity, with contact/escalation path and responsibility for post-execution monitoring and operator support.
Publish the complete MsgRegisterModel payloads and a prose-to-message checklist showing every model name, thresholds, parameters, and registry effect.
Add measurable post-execution checks: successful registration verification, operator adoption/compatibility checks, model availability, error/incident monitoring, and threshold validation criteria.

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

Нет ответственного owner: The proposal does not name an accountable owner or technical maintainer for this protocol change.
Нет измеримого результата: No baseline, target, post-execution checks, model-performance acceptance criteria, operator adoption metric, or incident-monitoring metric is provided.
Поддерживаемый asset без owner: Registering supported models creates ongoing operational and maintenance implications, but no maintainer or handover plan is identified.

Proposal introducing new Qwen3 models

О чем это

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

Источники