Upgrade Proposal: v0.2.16

Original Proposal Text

Upgrade Proposal: v0.2.16 The v0.2.16 upgrade includes protocol changes and bug fixes across the chain and API node. It also pays 104,150 USDT in bounties from community funds. Trusted Weight. Before v0.2.16, a sudden increase in claimed compute immediately increased a participant's power in governance, BLS, and PoC validation. The upgrade limits that power to compute confirmed in the previous epoch. New or returning participants start with zero voting power but still earn rewards. Dynamic Coefficients v1. Governance can set a target percentage of network compute and a coefficient range for each model. The protocol adjusts the coefficient inside that range to move compute toward the target. Compute above the target is scored at the minimum coefficient. Fee. The upgrade groups transaction types and adds per-message gas rules. The epoch and cosmos groups are enabled by default at 1 ngonka per gas. All other groups remain disabled. Before the upgrade, hosts must check that their cold-to-warm feegrant is valid. The cold account must have enough spendable GNK to cover fees. PoC Challenge. An approved challenger can require an active host to leave inference and run PoC at full capacity. The challenger locks a payment, which goes to the host if it passes or is refunded if it fails. Failure carries the same penalty as failed Confirmation PoC. Only allowlisted devshard escrow creators can open a challenge. If the allowlist is empty, anyone can open one. Upgrade Plan. Existing hosts are not required to rebuild their api or node containers. Devshard binaries stay on the versions already approved. New hosts joining after the upgrade should use the deploy/join files published with the final v0.2.16 release. Migration. The handler extends cold-to-warm grants with PoC Challenge and model intent messages. It moves approved devshard versions into a separate store without changing the approved list. It starts dynamic coefficients from current model scales and initializes PoC Challenge with a payment ratio of 0.1, at most 4 active challenges, and a minimum punishable segment of 300 blocks. Testing. The upgrade from v0.2.15 to v0.2.16 was rehearsed on a testnet using alpha builds. Compatibility testing covered devshard v4.1 and v5 with both v0.2.15 and v0.2.16. The full technical scope, contributor list, individual contributions, PR references, and bounty breakdown are available here: https://github.com/gonka-ai/gonka/blob/beb159be59e1b980f63e1caffcb51c89fce7bc23/proposals/governance-artifacts/update-v0.2.16/README.md