Validator action required: upgrade to ROKO v1.0.22

ROKO Network v1.0.22 is the required validator release before runtime spec 285 is activated. The release fixes the runtime mismatch that left the temporal EVM precompile unavailable at `0x0600` and preserves the native burn precompile already active at `0x0800`.

Release identity

Field	Required value
Release	`v1.0.22`
Source revision	`e63656b14135e47bdeacbebd659754e42b920af6`
Runtime after activation	mainnet spec `285`
Upgrade deadline	`2026-08-12 20:00 UTC`
Architectures	Linux `amd64` and `arm64`
Native artifacts	`https://downloads.roko.network/releases/v1.0.22/`
Container registry	`ghcr.io/roko-network/roko-node`
ABI	`https://downloads.roko.network/releases/v1.0.22/ITemporal.json`
Support and completion reports	`roko/roko_network#95`

Treat this as a priority validator maintenance release and complete it as soon as practical, no later than the deadline above. The live configured testnet runs the mainnet runtime flavor. Operators on this network must therefore select the `mainnet` archive or image, even though the network remains explicitly test-only.

Required action

1. Read the v1.0.22 node upgrade procedure. 2. Download only the architecture-matched mainnet artifact from the immutable release directory. 3. Verify `SHA256SUMS`, `BUILD-METADATA.json`, the release ID, and the exact source revision before touching the service. 4. Record the current binary or image digest, trusted genesis, finalized head, peer count, authority identity, and PTP² mesh state. 5. Replace software only. Preserve the chain spec, database, node identity, seven session keys, temporal key, and service credentials. 6. Require the full post-upgrade gate: expected revision, unchanged genesis, `isSyncing: false`, restored peers, advancing finality, correct active authority mapping, non-null producer index, and converged PTP² mesh.

Upgrade validators one at a time. Stop if the network is degraded and do not move to the next validator until the current node passes every gate. Retain the v1.0.21 executable or exact image digest until spec 285 and the EVM canary pass.

Installing v1.0.22 does not activate the precompile by itself. ROKO operators will submit the separately verified runtime upgrade only after the controlled fleet is ready. Report completion or a failed gate on issue #95 with the public node role, architecture, artifact checksum or image digest, and health result. Never post private keys, node keys, session keys, credentials, full service environments, or private topology.