Week 25 Dev Digest: v0.2.13 Testnet Cut, Escrow Fix, Bridge Audit Final

The week of June 15–21, 2026 was lighter on the core chain and heavy on release plumbing and user-facing documentation. Two pull requests landed in the main gonka repository, both around DevShards economics, while the gonka-docs repository saw 17 merges covering the Ethereum bridge, WGNK trading on Uniswap, and wallet onboarding. The headline event was the v0.2.13 devshard build reaching the testnet branch.

DevShards are the developer-facing variant of inference shards: the off-chain coordination layer (introduced in v0.2.11) that moves AI execution off the chain, with its own escrow and settlement accounting added in v0.2.12. Most of this week's chain work touched that accounting.

v0.2.13 lands on testnet

The v0.2.13 devshard release merged into the testnet/main branch via PR #1344, authored by @maria-mitina. It is a large integration: 520 changed files across 17 commits, folding the accumulated devshard work into a single testnet candidate.

This build runs on testnet only. It is not a MainNet release, and there is no governance proposal attached yet. The point of a testnet cut is to let hosts and validators exercise the new devshard settlement paths against a running network before any MainNet upgrade is proposed. The most recent MainNet release remains v0.2.12 from April.

Escrow distribution, corrected for v0.2.14

The one substantive logic change this week targets the in-development upgrade-v0.2.14 branch. PR #1347, from @0xMayoor, fixes how leftover money is split when a devshard escrow goes unsettled and is pruned.

Here is the plain version. When a group of validators runs a devshard, funds are held in escrow and paid out per slot, where a slot is a weighted unit of work and one validator can hold several. If that escrow never settles and gets cleaned up, the remaining balance is shared among the participants. The old code divided the balance by the count of distinct validator addresses, so every validator got one equal share regardless of how many slots it held. That under-paid validators holding many slots and over-paid validators holding one, which is out of line with how normal settlement pays per slot.

The fix divides by slot count instead and aggregates per recipient, so a validator occupying N slots receives N shares. Distribution order follows the first appearance of each address in escrow.Slots, and payments iterate that slice rather than a map, keeping the result deterministic. The integer-division remainder still stays in the module account, as before. The change is two files, 66 additions, and ships with a regression test, TestPruneDevshardData_UnequalSlotsPaidPerSlot.

This is orthogonal to the earlier CacheContext atomicity fix tracked in #1013: that one governs whether payments commit all-or-nothing, this one governs what each recipient is owed. The two compose cleanly.

Ethereum bridge: CertiK report goes final

The gonka-docs repository published the final CertiK Ethereum Bridge audit report this week. The PDF went through a restore-and-replace sequence — PR #1239 restored the earlier audit asset, then PR #1245 swapped it for the final report. The CertiK audit of the bridge had been the gating security item for cross-chain transfers, and the public document now reflects the completed engagement rather than a preliminary draft.

WGNK on Uniswap and wallet onboarding

A second documentation thread covered how ordinary holders interact with the token. WGNK — the wrapped form of GNK on Ethereum — is now tradable on Uniswap, and the docs caught up:

• PR #1235 rewrote the "Can I buy GNK" FAQ entry to point at WGNK on Uniswap.
• PR #1242 added a Disclaimer page and a Uniswap call-to-action to the landing site.
• PR #1229 and PR #1228 documented Cosmostation and Fox Wallet flows for existing users and added a tip for adding WGNK as a custom token in Ethereum wallets.

The quickstart also got attention: PR #1246 reframed the opening so a developer's first API request visibly runs on Gonka, and PR #1227 added a demo screencast for the Mingles Router broker.

By the numbers

No issues were closed in the tracked roadmap this week beyond the two merged PRs; the cross-referenced #1013 remains open as the companion atomicity fix.

Coming up

The next visible target is upgrade-v0.2.14, where the escrow distribution fix already sits. Expect more devshard accounting changes to gather on that branch before a MainNet upgrade proposal. On the testnet side, v0.2.13 now needs real validator exercise before it can move forward. With the CertiK bridge report final and WGNK live on Uniswap, the documentation focus is shifting from "how the bridge works" to "how a holder actually uses it."