Linux amd64 validator recovery installer (c0503f5)

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.

State-preserving recovery installer for the Linux amd64 UID79 validator at legacy directive 23. It retires the audited unresolved version-1 attempt through the native recovery procedure and installs the C4 competition host. Other hotkeys or predecessor states are rejected. The release includes host c0503f5809e8a8af16d270bc396c0e182e10ffcd and an authenticated compatibility-feed profile. C4's certified container, package, original admission and recipient amendments remain unchanged. The dedicated feed publishes fresh authorizations automatically. Prepare On the validator host: curl -fL https://github.com/Umi-BitSign/umi/releases/download/validator-recovery-host-c0503f5/install_yuma_recovery.py -o install_yuma_recovery.py printf '%s\n' '57c074c600a9b62affb59f3fa5eecde2e8467e5c74714ec4b41a04e8e59e7720 install_yuma_recovery.py' | sha256sum -c - && sudo python3 -I -B ./install_yuma_recovery.py prepare Send the final JSON, containing the generated public feed key, to the UMI operator for enrollment. The private key stays on the validator. Preparation verifies pinned downloads and native host signatures and installs the feed connection service. It does not stop the validator, open its wallet or submit a transaction. Upgrade after feed enrollment Confirm that every other instance using this hotkey is stopped. The command below consents to at most four paid recovery-marker transactions and approves this compatibility stream starting at block 9,160,937. That block is the start of the approved history; current owned finality is still required for activation. sudo python3 -I -B /var/lib/umi-yuma-recovery-c0503f5/install_yuma_recovery.py upgrade --confirm-only-validator --accept-marker-fees The native upgrade owns stopping the old supervisor, preserving its journals, reconciling the unresolved attempt, switching the host and starting the new service. It does not require a coldkey. If it holds, preserve the recovery state and send the selected status: sudo python3 -I -B /var/lib/

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.