EveryFrame Validator v0.5.0

EveryFrame Validator v0.5.0

Fixes the accounting-input divergence between owner and independent validators.
Validators now authenticate the same signed assignment for each finalized chain
epoch and independently calculate weights from its exact report hash. Their own
start dates, old queues and missing-report scan cursors no longer choose inputs.

Changes

• Canonical epoch-start cutoff, finalized chain-start hash, immutable assignment
  and report verification. HTTP 404/network errors wait; they do not imply zero work.
• No historical report replay, journal reset, chain parameter change or relaxed
  zero-fee/signing policy. Existing commitments remain reconciled independently.
• Owner-only reviewed missed-reward carry-forward: deduct received rewards,
  reserve against the future pool, keep excess pending, and reopen only reviewed
  unpaid portions after a failed or partial recovery. Publishing is not payment.
• Restricted accounting-assignment feed publisher, owner audit/finalization and
  recovery tools, with deployment documentation and numeric GET/HEAD routes.
• Read-only canary checks work outside signing windows. Actual signing windows
  remain enforced. Includes v0.4.1's legacy-hotkey fixes; no defaultpub.txt is needed
  when public metadata is present in the existing private hotkey file.

Upgrade

Coordinate the signing cutover with the subnet operator; a release does not
upgrade running validators or peers automatically. Preserve the existing state,
wallet, authorization and journals. Do not run init again or clear old cursors.
Verify that doctor accepts canonicalAssignment before starting the signing loop.

Image: ghcr.io/everyframe-studio/everyframe-validator:v0.5.0

For an existing virtualenv, install the attached wheel after stopping the existing
process, run everyframe-validator --version and doctor with the same state, then
restart only at the coordinated cutover. This package is not published on PyPI.
SHA256SUMS covers every attached artifact; image.txt contains the immutable image.

Accounting boundary

Owner journal absence is not evidence that a miner received zero rewards: other
validators, previously revealed weights and pending commitments must be reviewed.
This release does not automatically approve historical compensation, recover old
burned emissions, guarantee USD payouts or treat weight application as settlement.
See OWNER-ACCOUNTING.md for the review and carry-forward procedure.