Week 11 at a Glance

The Gonka development team closed 33 issues during the week of March 7–13, 2026 — one of the most productive weeks since MainNet launch. Three major themes dominated: IBC integration, a security hardening sweep driven by CertiK audit findings, and deep performance optimization of the inference pipeline.

IBC Goes Live

Inter-Blockchain Communication support landed with two key issues (#615, #814). The implementation adds IBC pool functionality and trade support, opening the door for cross-chain token transfers and liquidity. This is a foundational step toward Gonka becoming interoperable with the broader Cosmos ecosystem.

Security Hardening Sweep

A concentrated batch of security fixes addressed findings from the ongoing CertiK audit and internal review:

  • BLS group key validation (#848, #851) — removed a fallback that allowed self-validation when previous epoch data was missing
  • DKG dealer consensus (#849, #852) — fixed a mismatch where dealer consensus used unweighted participant votes while quorum required slot weights
  • CometBFT update (#652, #675) — patched CSA-2026-001 (Tachyon vulnerability) by upgrading to CometBFT v0.38.21
  • ML pipeline RCE (#863) — eliminated a potential remote code execution vector via torch.load() in the training pipeline
  • TLS hardening (#865) — replaced hard-coded dummy TLS certificates in the Gloo transport training manager
  • Data race conditions (#543) — resolved concurrent access issues across multiple components

Inference Pipeline Optimization

The StartInference and FinishInference message flow received a complete overhaul across five linked PRs (#608, #780–783). Key verification was optimized (#779), and MsgValidation plus MsgClaimRewards got dedicated performance improvements (#874). A critical fix also prevents permanent token loss during partial payout failures in ClaimRewards (#741).

Governance and Economics

Two governance-related changes shipped: a new transaction type for deleting governance models (#465, #773), and a policy change redirecting slashed coins to the governance pool instead of burning them (#772, #775). Multi-user vesting proposals also received a fix (#834).

Infrastructure

The application.db bloat issue (#819, #867) was resolved with proper pruning, and the semantic cache gained an L2 quality gate with adaptive coherence floor (#859). API container migration changes were defined (#731), and integration tests were updated (#871).

By the Numbers

Metric Value
Issues closed 33
Security fixes 8
Performance PRs 7
New features 3
Period March 7–13, 2026