v0.1.25 - Miner Diagnostics and Validation Hardening

Summary

This release adds opt-in miner diagnostics, hardens validator state around recycled Bittensor UIDs, improves capacity-audit validator discovery, and prevents unverified output-token counts from inflating throughput scoring.

Changes

• Added an opt-in, cached miner diagnostics state with UID and executor/model-index views for scores, canaries, receipts, probation, capacity-audit gates, recovery estimates, and network incentive state.
• Added public read-only diagnostics routes at /v1/miner-debug/help, /v1/miner-debug/{uid}, and /v1/miner-debug/{uid}/entries/{model_index} on enabled proxies.
• Reconciled reusable Bittensor UID ownership against current hotkey and EVM identity, excluding stale prior-owner endpoints and resetting mutable score, probation, audit, and weight state when ownership changes.
• Kept cached capacity-audit validator targets available while chain discovery refreshes in the background and retained chain-discovered targets after inconclusive health probes.
• Bound reported output-token counts to the request limit, inference commitment, and proof bundle before throughput is accepted.
• Added a defensive per-receipt output cap for legacy or imported scoring data.
• Allowed miner environment prechecks to run before the proof wheel is installed, producing actionable compatibility errors earlier in setup.
• Reduced eager package imports so setup and precheck paths do not load unnecessary runtime modules.

Operator Notes

• Validators and proxies: auto-update will handle the 0.1.25 update and restart automatically.
• Miners: updating is not required, but is recommended for improved stability and the latest capacity-audit validator discovery and setup precheck improvements. Miner auto-update is not triggered because the miner version is unchanged.
• Miner diagnostics are disabled by default and must be explicitly enabled by the validator/proxy operator.
• Miners must report an output_tokens value that matches the committed and proven output and does not exceed the request limit.

Version

• Validator/proxy version: 0.1.25
• Miner version: unchanged at 0.1.0
• Spec version: 0.1.25

Validation

• Targeted validator, proxy, diagnostics, UID ownership, capacity-audit discovery, scoring, and token-accounting test suites passed.
• Production staging accepted a correctly counted, proof-valid response and rejected mismatched and over-limit token counts.
• Production capacity-audit receipt/proof processing, diagnostics cache generation, API health, and x402 challenge generation were verified after restart.