Signed validator recovery host 6db1d11 (Linux amd64)

SN78's earlier identity: Filed under SN78 from a source its on-chain identity named before. The identity has changed and no longer names this source, so the item is not listed as news of the subnet on SN78 now.

This signed Linux amd64 host contains the recovery and C4 integration from PRs #195 and #196. It supports the audited legacy version-1 bridge submission and preserves its original journal while recording the historical transaction outcome as unknown. These are host runtime artifacts, not a complete installation-specific upgrade bundle. They do not automatically update a validator or authorize a transaction. Use the installed-configuration inspection to prepare the matching signed controls, source approval and local operator consent before recovery. Do not delete existing journals or start another writer for the same hotkey. Runtime source: 6db1d112a2ada7b4b1084816d33453c4efafb850. Signed host manifest: 05ea0cb6281f0c76b20615e360ad8f715feb02eaf90ac8acdefefde1d5a96229. Platform: linux/amd64; source identity: 92a70f6c9a408b5515a8b15416bf1d2b64f1019baf0fe8c442ec006609f4c2a3. host.bundle.gz expands to the native host bundle. The detached authority signature is in signed-host-manifest.json; the SHA256SUMS file checks downloaded bytes and does not replace signature verification. C4 continues to use its original pinned worker image. The signed consent approves host source mounted read-only into that image, scoped to the exact C4 package, release and amendment. Runtime source passed full CI and six native Linux jobs. The combined amd64 migration test also passed with C4's exact original image, including an uncertain legacy submission, marker outbox, recovery checkpoint, interrupted installation and restart. The test uses synthetic chain/transaction ports and a supervisor probe; it does not establish a real marker or successful Yuma weights. Final qualification is recorded in PR #196. See the recovery and upgrade contract. Completion requires a fresh finalized weight update from the recovered validator.

Read the release notes on GitHub ↗

Taosis indexes announcements, articles, posts and releases about Bittensor subnets from their own channels and keeps a record of each. The text above is the source’s; the figures are read from the chain by Taosis.