v0.1.7 - Native verifier hotfix

Summary

Validator-only hotfix for native full-proof verification.

Changes

• Load Torch before importing the native zkgemm_cuda extension so required shared libraries are available.
• Fix full/native proof verification on validator hosts using the shipped zkgemm_cuda artifact.
• Bump validator_version to 1007.
• Keep miner_version at 1006; miners are not required to update.

Operator Notes

Validators should update to v0.1.7.

Miners do not need to update for this release. If auto-update is enabled, miners will not restart because miner_version did not change.

Our validator has been updated and verified with successful spot and full proof checks after restart.

Full Changelog: v0.1.6...v0.1.7

v0.1.6 - Bittensor runtime compatibility

Summary

This release updates Nodexo for the recent Bittensor runtime metadata change that affected netuid decoding on current chain metadata.

Changes

• Update runtime dependencies to bittensor==10.5.0 and bittensor-cli==9.23.2.
• Replace main-runtime substrate-interface signing/SS58 usage with the current Bittensor SDK APIs.
• Add a one-time runtime migration for existing installs that removes old substrate-interface / scalecodec packages before Bittensor is imported.
• Bump miner, validator, and spec versions to 1006.

Operator Notes

Validators should update as soon as possible. Older environments may fail metagraph/subnet calls and stall scoring or weight setting.

Miners should update as soon as possible. Older environments may fail validator discovery/auth paths and lose proof/heartbeat broadcasts to some validators.

Fresh installs require no manual cleanup.

Existing installs should migrate automatically on first startup after update. If startup still fails with a scalecodec / cyscale conflict, run:

cd /path/to/nodexo
source .venv/bin/activate 2>/dev/null || source venv/bin/activate

pip uninstall -y substrate-interface scalecodec cyscale
pip install -e .

v0.1.5 - Allocation migration readiness and miner version gate

This release prepares Nodexo for the allocation-ledger migration while keeping current chain-backed rental locks active.

Validator

• Adds subnet-config support for scoring.min_miner_version.
• Validators can gate unrented miners below the configured minimum version from scoring and rentable inventory.
• Already-rented miners remain active and scoring until their rental ends.
• Validator scoring now treats fresh API allocation locks as rented for scoring compatibility.
• Validator auto-update will handle this update when enabled.

Miner

• No immediate miner update is required while the minimum miner version remains permissive.
• Updating to 0.1.5 / 1005 is recommended.
• If a miner is currently rented, do not force an update during the rental. Auto-update will schedule the update after the rental ends.

Current rollout

• Live subnet config currently keeps min_miner_version=1001.
• Allocation writes remain chain-backed for now.
• A later config change can raise the minimum miner version and then switch allocation writes to API mode.

v0.1.4 - Validator Discovery, Operator Diagnostics, and Allocation Authority

Highlights

• Improved miner discovery for EVM and native validator endpoints.
• Improved broadcast handling when external validators are temporarily warming registry state.
• Added operator dashboard diagnostics for chain-active executors that are temporarily not scoring.
• Added allocation authority support for the upcoming off-chain rental lock migration.
• Cleared canary hard flags after successful recovery.
• Reduced noisy warnings for non-primary validator broadcast paths.

Upgrade Notes

Validators using the standard auto-update setup will update automatically.

Miners:

• Idle and unrented miners update automatically when auto-update is enabled.
• Do not force an update while actively rented.
• Auto-update defers restart until the rental ends.
• Manual update is fine after the rental has ended.
• Enabling auto-update is recommended.

Versions

• Miner version: 0.1.4
• Validator version: 0.1.4
• Spec version: 1004

v0.1.2 - Validator discovery hardening

Stabilizes validator discovery for miners across EVM registry validators and native validator endpoints.

Changes:

• Merge active EVM registry validators with native validator endpoints.
• Retry partial discovery quickly when native validator endpoints are temporarily inconclusive.
• Keep validator registry endpoints active across normal restarts.
• Default shutdown deactivation off for validator registry entries.
• Preserve miner version at v0.1.1; validator/spec remain v0.1.2.

Nodexo v0.1.1

Initial public release of Nodexo, a verified decentralized compute subnet on Bittensor.

Included

• Miner and validator daemons
• Public testnet and mainnet chain configuration
• One-command installer and setup scripts
• GPU proof generation and validator-side proof verification
• Operator CLI for fleet, inventory, and registration flows
• Validator rental, billing, inventory, scoring, and weight-setting components
• Prebuilt ZkGEMM runtime artifacts for supported environments

Validator

• Sets validator weights by on-chain block cadence instead of wall-clock sleep.
• Uses cached chain head data for scheduler timing and refreshes metagraph only near the due window.
• Prevents validator weight staleness when no positive miner score is currently available by falling back to the configured burn UID.
• Bumps validator_version to 0.1.1.

Miner

• Miner version remains 0.1.0.
• No miner update is required for this release.

Compatibility

• spec_version remains 0.1.0.
• No subnet weight-version change is required.
• Validators running with auto-update enabled will update when they detect validator_version = 0.1.1.
• Miners should not auto-update from this release because miner_version is unchanged.

Upgrade

Fresh install:

curl -fsSL https://raw.githubusercontent.com/nodexo-ai/nodexo/main/install.sh | bash

**Full Changelog**: https://github.com/nodexo-ai/nodexo/commits/v0.1.1