Skip to content

EveryFrame Validator v0.5.1

Choose a tag to compare

View all tags
@github-actions github-actions released this 23 Oct 03:22
v0.5.1
6292fd4
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

EveryFrame Validator v0.5.1

Compatibility release for chain-derived miner emission accounting, plus a reveal-tracking correction.

Changes

  • Support chain-miner-emission-v1: reconstruct the actual miner bucket from finalized per-block alpha-out rates and parent-state emission splits, including SN117's approximately 33% miner share. This is not 33% of the previous 41% bucket.
  • Verify signed public emission evidence independently against chain storage before calculating/signing weights. Bound archive queries, share pinned SDK metadata, and cache only fully verified evidence bound to the complete artifact and boundary hashes.
  • Preserve historical legacy/fixed-41% reports and existing journals, authorizations, state and commitments.
  • Add doctor --check-emissions for read-only full-window archive/readiness checks before the new policy is enabled. Mainnet defaults to the official Finney archive; explicit RPC overrides remain supported.
  • Fix reveal/application observations for chain-epoch-v3 submission records as well as v2.

Upgrade

Stop the existing validator before replacing its code/image. Use ghcr.io/everyframe-studio/everyframe-validator:v0.5.1 or the immutable digest in image.txt. Keep the same state directory/volume, wallet mounts, RPC configuration and signing command. Do not rerun init, clear journals, recreate wallets or renew authorization just to upgrade.

For a source installation, install this release's wheel into the existing service virtual environment while that service is stopped. This package is not published to PyPI.

Before restarting the existing instance, confirm:

everyframe-validator --version
everyframe-validator doctor --state-dir YOUR_EXISTING_STATE
everyframe-validator doctor --state-dir YOUR_EXISTING_STATE --check-emissions

The emissionHistory check must pass using that operator's actual RPC. Read-only checks do not unlock a private key or submit a transaction.

Coordinated activation required

Publishing/installing v0.5.1 does not activate the new accounting policy or upgrade running validators. v0.5.0 rejects the new evidence format. Upgrade the accounting publisher, owner validator and independent validators (including Yuma), verify readiness, then coordinate explicit owner writer opt-in with --chain-emission-policy. The live writer remains unchanged by this release. No chain parameters, historical reports or recovery approvals are changed.

Verification

401 local validator tests and 97 sibling subnet tests passed. A clean installed candidate wheel verified test-signed evidence against live mainnet storage, rejected validly signed altered evidence, and checked wallet compatibility without a public sidecar. The read-only owner-profile probe passed. GitHub Actions separately tests Python 3.10, 3.13 and 3.14, clean wheel installs, and the non-root Linux amd64 container. No production signing key, chain transaction or service restart is used for release verification.

Release assets include wheel/source distributions, deployment templates and SHA256SUMS. Independently verify the checksums and review the upgrade instructions.

Assets 13
Loading