Yuma validator recovery package 0.1.0

Installs the state-preserving recovery command for Yuma's Linux amd64 UID79 validator at legacy directive 23. The command authenticates feed enrollment with the existing validator hotkey, then runs the published native recovery and host upgrade. No public-key exchange with UMI is needed.

On the validator host:

curl -fLO https://github.com/Umi-BitSign/umi/releases/download/validator-recovery-package-0.1.0/umi-validator-recovery_0.1.0+c0503f5_amd64.deb &&
sudo apt install ./umi-validator-recovery_0.1.0+c0503f5_amd64.deb &&
sudo umi-validator-recover yuma

Confirm in the terminal that this is the only validator using the hotkey and approve up to four fee-paying recovery-marker transactions. Private keys stay on the host. The package has no installation scripts; recovery starts only when the command is run. It preserves the original journals and recovery state. Once the recovery service starts, it continues after logout.

Progress: sudo umi-validator-recover status. Completion requires a fresh finalized weight update from UID79. Keep existing state intact if recovery reports a hold.

The package embeds the unchanged bootstrap from host c0503f5, SHA-256 57c074c600a9b62affb59f3fa5eecde2e8467e5c74714ec4b41a04e8e59e7720. It retains the pinned signed host and C4 runtime checks. C4's certified package and allocation are unchanged.

Validation: 19 Linux checks passed, including native enrollment signatures, wrong-key and replay checks, root-owned restricted SSH enrollment, command ordering and refusal paths. The Debian package was installed in an isolated dpkg root and its installed files and command entry point checked. Dependency resolution was omitted only in that empty test root; package dependencies remain declared. Tests substitute wallet, transaction and service operations where needed; no Yuma upgrade or fresh Yuma weights are claimed. The existing host release retains its own recovery qualification and CI results.

The attached source archive contains the package and enrollment sources, build command and tests. SHA256SUMS covers the package and source archive. Retain the dedicated compatibility feed until Yuma completes a verified migration to the successor system.

Linux amd64 validator recovery installer (c0503f5)

Signed recovery host c0503f5809e8a8af16d270bc396c0e182e10ffcd for Yuma's Linux amd64 UID79 validator at legacy directive 23.

Use install_yuma_recovery_launch_fix.py for the corrected bootstrap. Its SHA-256 is 8bcaa66c4a044a8c5b12007d52fa3342d7a38ce57a6791c8a78bdf22be221e2f. The original install_yuma_recovery.py and package 0.1.0 select a missing executable and must not be used to launch recovery. They remain available for diagnosis. The corrected bootstrap calls the included umi.competition_switch_recovery module, retains itself separately, and prepares fresh controls in controls-launch-fix.

For an already prepared installation that failed before recovery with exit code 2, use the targeted copy-paste launcher correction supplied to Yuma. It preserves the original installer, controls and validator journals and reuses downloaded artifacts. Do not repeat initial recovery if it has already reached signing or source publication; preserve that recovery state and use its documented continuation path. The sole-writer requirement and explicit consent for up to four paid marker transactions remain in force.

The native upgrade reconciles the audited unresolved version-1 attempt and installs the C4 competition host. C4's signed runtime, package, original admission and recipient amendments remain unchanged. The compatibility feed publishes fresh authorizations automatically. A fresh finalized weight update from UID79 establishes recovery completion.

The exact published Linux bundle reproduces exit code 2 for the missing executable and successfully starts the module's upgrade CLI. Six focused operator-block checks verify correction and rejection of changed installer/service state. Earlier installed migration checks use synthetic chain/transaction ports, and earlier bootstrap checks intercepted service start. None establishes successful recovery on Yuma's host.

SHA256SUMS retains the original artifact checksums. launch-fix-SHA256SUMS covers the corrected bootstrap. Preserve the compatibility feed and recovery state until this consumer completes a verified successor migration.

Signed validator recovery host 6db1d11 (Linux amd64)

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.

C4 validator runtime recovery artifact

Preserved C4 Linux amd64 weight-worker bundle at revision baf4285271c1f076edb89a096fd04f254a9477cb, provided as an immutable recovery and qualification dependency. Its bytes match the originally signed C4 release.

Bundle SHA-256: 8fdd65be14cbd290d1b6ec7ce10d36b4842b0993b781daaafeb61cca1b2553ff.

Recovery installation remains governed by the signed host package, operator consent and state-preserving upgrade procedure.

Cohort 4 miner connection inputs (policy 8)

Public configuration inputs for cohort 4 (policy 8), roster block 9,120,990. Miner revision: f76e3d85f73fe6ac79dccf6de4760ec3396ebc4e.

Manifest SHA-256: f5a984457a53549fb06d9076c3c446fa5149f164a902a9ed608753374adfda28.

These inputs are available for miner preparation. The manifest and deployment snapshot correctly report preparation-only status with assignment delivery and evaluation false. Check the live readiness API for current deployment status. Publishing this input bundle does not activate assignments or competition rewards.

The policy, signature, ancestry and transport binding were checked by the pinned miner CLI at finalized block 9,120,210. The same inputs passed connected startup and restart on the owned Studio miner. Old policy-7 assignment/finality databases must be preserved; use new C4 state paths, retain the existing nonce database, and update sidecar transport configuration. Inference allowance: 600 seconds. Request window: 24 hours; cohort cadence: 48 hours.

The current connection guide will link this verified bundle. No private clips, labels, wallets or credentials are included.

Cohort 3: provisional scores (uncertified)

Cohort 3 closed without a final settlement certificate. These are provisional computed results, published for inspection. C3 competition rewards have not been activated. There is no confirmed date for C3 rewards to enter on-chain weights.

• 174 miners: 70 scored outcomes and 104 void outcomes.
• Download cohort3-provisional-results.csv for a spreadsheet, or cohort3-provisional-results.json for the website and other integrations.
• Scores use the signed policy's weighted quality calculation, on a scale from 0 to 1 with higher values better. The JSON includes exact fractions, per-stratum scores and candidate case-status counts.
• Score ranks are within track and preserve ties. A score rank does not establish reward eligibility. Voids have no score or rank and must not be displayed as zero scores.
• Every row in the CSV and the JSON metadata identifies the results as provisional and uncertified. Neither file authorizes weight submission.

The 70 scored results were recalculated from signed retained results using the pinned CPython 3.12.14 scoring environment. Void records were matched to their retained evidence and decision digests. This publication does not replace the missing final settlement certificate.

Verify the downloads with shasum -a 256 -c cohort3-provisional-results.sha256. That file is a download checksum list, not a quorum certificate.

Round: 19cdf0a16b415190574b609d0852becdb54bef7b4e74416c862205bda418535f.

Computed settlement: 0f347c0274b7268d8ff9dcd594e69cc34d577956e599bdf927baf64cd6800a8f.

Retained round references · Computed settlement

Open competition miner bundle v1 (feed config + pinned artifacts)

Signed feed configuration and pinned runtime artifacts for the SN78 open
competition, as promised in OPEN_COMPETITION.md.

Start here: COMPETITION_MINER_ADDENDUM.md. It applies on top of the
reference miner runbook. If you already run the reference miner in
inactive_shadow, this is a wiring change, not a rebuild.

Supported targets: aarch64-apple-darwin, x86_64-unknown-linux-gnu.
ARM64 Linux is not yet published.

Verify before use:

shasum -a 256 -c SHA256SUMS

transport-policy.json must hash to
d030da694b5dd8d0e02c4c5a9d607107ed54d8feec47e2ea0e7f6b1070630168.
Both verifier binaries are additionally pinned inside that policy and
re-checked by the miner at startup.

SHA256SUMS is signed (sr25519) by the release authority
5DPEtjXkt9y216Mc6u8jNcM69ULppSCvpys5sUHxtVf2ebkS; see SHA256SUMS.sig.

Correction to an earlier notice: the cohort cadence is round_stride_blocks
= 2880 blocks (about 9.6 hours), not 1440 (about 4.8 hours).

SN78 direct bootstrap cutover v1 inputs

This prerelease publishes the immutable inputs for the temporary SN78 direct
bootstrap cutover. It does not claim that the owner fence or service row has
been applied.

• UMI revision: b769ca152e22c6c4027584a7d2a368474ddb6194
• Signed eligibility manifest file SHA-256:
  5b819ae5b25cd353293b72a2f53b1fb5084e877767f2bb28e63a872c49fba350
• Signed manifest's canonical inner identity:
  7901ff0aeeb01e46556b26676969a41ba1d8a5a7e77164116a0b08db49189c4c
• Direct transition authorization file SHA-256:
  acf1c7b4c8e8335ef45d5340196454362d58f02c95dda14ba304de0a29da47b2
• Authorization submission ID:
  671794b7f6180d8cb018ff64b355347bff70214214a3caec1494a6d2d3aea8de
• Authorization interval: finalized blocks 9,031,052 through 9,033,000
• Coordinator hotkey:
  5GsPXiSyzpK3rRoeAmjT4F5Cqa1RmP1CyBvNpwNDsDejyNZ4

The release assets preserve the exact canonical bytes consumed by the pinned
operator. Translation weights and bootstrap service weights remain inactive
until the final on-chain row is independently verified and its evidence is
published.