Between May 25 and May 31, 2026, work landed across two active Gonka repositories: 24 pull requests merged (3 in gonka, 21 in gonka-docs) and 19 tracked issues closed. The week was anchored by the v0.2.13 microrelease, the arrival of two new inference models, and a round of hardening for the Ethereum bridge and the off-chain devshard layer.
Release: v0.2.13 microrelease
The v0.2.13 microrelease was prepared and merged on 2026-05-26 (PR #1143, 169 files changed). A microrelease bundles a set of fixes and parameter updates without a full feature cycle. This one closed several correctness gaps at once:
- Confirmation PoC no longer loses weight while a new model is bootstrapping. Confirmation PoC is the step where the network re-checks that a node really has the compute it claims; previously that check could under-count capacity during a model switch.
- DevShard storage growth is bounded by adding pruning and Postgres support, so the off-chain coordination state stops accumulating without limit.
- A host that recovers from an invalid state is now re-validated automatically instead of staying sidelined.
- Older inference APIs regained the complaint-response authorization grants they were missing.
Two new models: MiniMax-M2.7 and Kimi-K2.6
PR #1143 also registered the MiniMax-M2.7 governance model with its own Proof of Compute config (PenaltyStartEpoch = 278). Alongside the existing Qwen and Kimi options, the network can now route inference to more than one model.
Adding models means re-tuning how each one is scored. The release recalibrated WeightScaleFactor against a Qwen-on-B200 reference after the vLLM 0.20.1 release, where Kimi was scoring too high on Blackwell-class GPUs: Kimi settled at 0.78 and MiniMax at 0.3024. Validation thresholds were also updated from cross-version vLLM runs — Qwen 0.940, Kimi 0.900, MiniMax 0.922.
A related correctness fix landed in PR #1263: Kimi-K2.6 inferences were being flagged as inflated_tokens by mistake. The reasoning parser stripped <think> and tool-call markers from the streamed output while still counting them in the token total, so the validator's count came up short and the honesty check fired on honest work. A production sweep across 25 multi-turn, reasoning, CJK, and emoji prompts cut 9 false positives to 0.
Validation and rewards correctness
Six closed issues tightened how rewards and penalties are computed:
- #829 excludes invalidated inferences from the missed-validation check used by
ClaimRewards. - #830 makes reservoir sampling in
ClaimRewardsuse a deterministic seed, so every validator computes the same sample. - #1131 claws back a validator's shares when its work is invalidated, and #1132 bounds the finish cost before an invalidation refund.
- #1124 stops stale PoC validation promptly, and #1142 resets a node's consecutive-failure counter once it has been used.
Bridge and DevShard hardening
The Ethereum bridge picked up two safety fixes. #1196 canonicalizes deposit keys and adds a global completion dedup so a deposit cannot be processed twice, and #1197 validates the Ethereum destination address on withdrawal before funds move.
The devshard layer — the subnet that coordinates off-chain inference — closed three issues: #1157 keeps the upstream SSE stream alive through devshard_meta, #1159 finishes gossip on a missed diff, and #1166 adds a mainnet height oracle plus a test environment.
Upgrade tooling and governance
PR #1268 reworked how the chain records LastUpgradeHeight. It adds a query and CLI for the value, drops the old BeginBlock detection path in favor of a centralized upgrade-handler wrapper, and pulls in the v0.2.14 upgrade scaffold using the new tracked registration pattern. The change makes the height at which a software upgrade took effect directly queryable.
On governance, v0.2.13 reduced genesis guardian voting power to about 25% and set the chain-wide quorum to 0.25. With guardians abstaining, that leaves an effective one-third quorum among the remaining 75% of voting power.
Documentation
The gonka-docs repo carried the model rollout: MiniMax-M2.7 bootstrap and licensing pages, the v0.2.13 upgrade announcement, and quickstart updates referencing the node-configs repo. PR #1145 fixed the Ethereum bridge docs (QA-18/19/20), and PR #1093 restructured the governance section and expanded its guidance.
By the numbers
| Metric | Count |
|---|---|
| PRs merged | 24 |
| Issues closed | 19 |
| Repos active | 2 (gonka, gonka-docs) |
| Core PRs (gonka) | 3 |
| Docs PRs (gonka-docs) | 21 |
| New model registered | MiniMax-M2.7 |
Coming up
The v0.2.14 upgrade scaffold is already wired into the tracked upgrade path, so the next release cycle has its foundation in place. Issue #1274 opens the door to running Gonka's own documentation translation on the network itself — an early test of multi-model inference on a real workload.