Overview

Week 16 brought 27 closed issues — the highest count in recent weeks — anchored by two P0 milestones: multi-model support (#728) and the removal of float math from DevShards consensus (#893). The Gonka team also landed transaction fees for spam prevention, shipped CertiK bridge audit fixes, and continued hardening v0.2.12 for MainNet.

Multi-Model Architecture (#728, #1039)

The long-awaited multi-model support closed this week as a P0 milestone. Issue #728, open since the early roadmap, tracked the ability for the network to serve more than one AI model simultaneously. Alongside it, #1039 delivered the Multi Model PoC — a proof-of-concept validating that Proof of Compute works correctly when validators run different models in parallel. This lays the foundation for Gonka to move beyond the single Qwen3-235B-A22B setup toward a heterogeneous compute marketplace.

Transaction Fees for Spam Prevention (#981, #928, #1066)

The team finalized GIP #981 — a governance improvement proposal introducing transaction fees specifically designed to prevent network spam. Related issue #928 resolved open questions around block gas limits, cost-per-participant calculations, and system transaction prioritization. A follow-up fix (#1066) addressed edge cases in fee computation. These changes mark Gonka's first departure from the zero-gas model, adding a minimal fee layer where it matters most: deterring abuse without burdening legitimate users.

DevShards Consensus Hardening (#893, #1069, #1045)

Three DevShards-related issues closed. The P0 issue #893 removed all floating-point arithmetic from DevShards consensus — a critical fix eliminating non-determinism that could cause state divergence between validators. Issue #1069 integrated DevShard settlement directly into Participant EpochStats, giving validators accurate per-epoch earnings data. Issue #1045 introduced subnet splitting, enabling the network to partition compute resources more granularly.

Bridge Security and CertiK Audit (#1064, #753, #1021)

Bridge security received continued attention. Issue #1064 sanitized user-controlled path parameters in the REST bridge API — closing a potential injection vector. The CertiK preliminary report discussion (#753, Priority 1) was resolved, and audit fix #1021 (GEB-51) shipped concrete code changes addressing findings from the review. These fixes follow the bridge safety hardening covered in previous weeks.

PoC Improvements (#926, #1036)

Two PoC-related fixes landed. Issue #926 corrected a seed generation bug in the PoC validation flow, while #1036 introduced stronger RNG parametrization for PoC v2 and added mlnode version tracking on-chain. Both changes improve the cryptographic integrity of compute validation.

v0.2.12 Preparation (#1047, #1049, #1048, #992)

The v0.2.12 upgrade continues to take shape. The Transfer Agent address was added to the upgrade whitelist (#1047). Onboarding documentation was updated to remove outdated gas fee examples (#1049) and the upgrade description was refined (#1048). Maintenance windows (#992) — previously work-in-progress — were also completed, allowing coordinated node downtime during upgrades.

Infrastructure and Testing (#1043, #1034, #1042, #1040, #1038, #1041, #1004, #1065)

Eight infrastructure issues closed: Testermint test fixes for streaming and dynamic pricing (#1043, #1034), an mlnode update with dtype=auto support (#1040), a versiond follow-up (#1038), updated issue templates (#1041), ai-reviewer documentation (#1004), and onboarding corrections (#1065). A reverted testermint fix (#1042) was superseded by the corrected version.

IBC for Bitfury Community Sale (#924)

The P0 issue ensuring IBC compatibility for the Bitfury community sale was closed (#924). This confirms that cross-chain token transfers via IBC are validated and ready for the upcoming community distribution event.

By the Numbers

  • 27 issues closed (April 10–16)
  • 3 P0 milestones resolved (#728, #893, #924)
  • Key areas: multi-model, fees, DevShards, bridge security, PoC, v0.2.12 prep