Gonka released an emergency fix for a PoC-v2 vulnerability that allowed participants to inflate their computational weight.
- LLM tokens this week
- 59.3B DevShard · input + output
- GNK this week
- -20.4%
- Pool trading volume
- $151k Uniswap v3 WGNK/USDT 0.3% on Ethereum
- Reporting period
- 6—12 July 6–12, 2026, UTC
GNK fell 20.4%
GNK fell from $0.2179 to $0.1734 over the week in the pool analyzed. Trading volume was $151.4 thousand, compared with $188 thousand over the previous seven-day period. These prices apply only to the pool analyzed, not all GNK markets.
More tokens from fewer requests
DevShard statistics showed 5.60 million completed requests, down 1.3% from the previous week. It processed 52.52 billion input tokens and 6.82 billion output tokens. Their combined volume rose 39.5%. MiniMax-M2.7 remained in the lead with 80.2% of tokens; Kimi-K2.6 accounted for 19.8%.
Test network approved, compensation rejected
Proposal No. 82 for a four-month pilot of External Test Lab and Community DevNet passed. It provides for monthly tranches of 22,000 USDT and allows remaining funds to be returned to the community pool through a vote. Approval alone does not confirm that funds have been transferred.
Proposal No. 80 on GRC compensation and No. 81 on compensation for Kimi operators were rejected. No. 84 on raising capital through Uniswap and No. 85 on an internal go-to-market team were also rejected.
Model stability and host incentives
Participants discussed slow responses and errors from Kimi. Suggestions included raising inference prices, increasing rewards for hosts serving this model, and optimizing the code. Opinions on GLM-5.2 were divided: some participants proposed temporary incentives and testing quantized versions, while others called for assessing demand and the economics of deployment first.
Emergency fix and DevShard v3
On July 6, the documentation reported that exploitation of the PoC-v2 vulnerability had been detected. Inflated weight affected rewards, consensus, and voting. An emergency API fix was released; a permanent fix is planned for the v0.2.14 chain upgrade.
A preliminary DevShard v3 build was published on July 9, and proposal No. 83 to approve it passed on July 11. The version is intended to serve inference during the upcoming chain upgrade. By the end of the period, the instructions directed authorized DevShard creators to switch traffic; approval does not confirm that all traffic has migrated.