Skip to content

v0.1.2 — Owner-controlled burn, protocol 2043

Latest

Choose a tag to compare

@OrangutAI OrangutAI released this 05 Oct 16:35
cd847c4

Endure v0.1.2 introduces owner-controlled miner burn under protocol key 2043. Validators read the subnet owner's endure.burn_bps=<0..10000> commitment; at 9800 the owner's burn allocation is approximately 98%, with the rest distributed by earned miner score. See the release notes for the full upgrade and rollback procedure.

Upgrade coordination

  • Miners and validators must agree on key 2043. Key-2042 submissions are rejected by key-2043 validators.
  • Publish the intended SN30 owner commitment before upgrading validators. An absent or invalid commitment defaults to 100% burn. Validators still running 2042 ignore it.
  • Hotkeys under the subnet owner's coldkey do not receive earned allocations. Chain minimum allowed weights and maximum weight limit must both remain 1.
  • The mainnet canary on UID 195 and third-party cutover are separate from this publication. UID 195 remained healthy on its immutable v0.1.1 digest during release preparation.

Release identity

  • Source/tag commit: cd847c4bff4052543a22957dade4470786e3ea66 (the staging source promoted to main).
  • Package version: 0.1.2; protocol key: 2043.
  • Runtime content revision: bf64934a5ef82afd67372c63f041323f0d3017f716af8f4490b356fde223a5af.
  • Protocol digest: b99135ebe7bde1f22ab7edf33ff581f5cabc2735cde979d22a423b70a6e11cd0.
  • Production images reuse the qualified staging manifests without rebuilding. Exact digests are recorded below.

Verification and release exception

The protocol code already ran on testnet from October 3 (02ab118), with confirmed approximately 98% owner votes, miner commit/reveal activity and continued resolution. The October 5 release change only adds documentation, version metadata and version-pinned tests. The owner accepted that existing evidence and waived an additional timed soak; this is not a claim that the default seven-day gate passed.

  • The 2043 implementation previously passed independent Daybreak and Opus reviews.
  • Metadata PR #79: Daybreak approved, with 696 focused tests passing. Opus completed 336 tests and multiple static checks but reached its session limit before a final verdict; its wording observations were addressed.
  • GitHub's full release-PR suite passed all 1,788 tests. A loaded local run had three startup timeouts; all 12 startup-exit tests passed in isolation, and the remaining local gates passed.
  • Final-staging CI and localnet qualification passed. Both ordinary and burn cycles confirmed weights; the burn vote assigned 9800.07 bps to the owner and reported 9800 on health. The older CI runtime lacks MinerBurned, but its epoch incentive read was approximately 0.98 owner / 0.02 miner. Image publication supplies the exact manifests listed below.
  • Testnet redeployed at 15:58 UTC on October 5 and reports 0.1.2 / key 2043 with matching source and content identities. Its validator loop is alive, and the updated health probe passed. Devops verified each of the five miners on the same source/content/version and the endure-soak wallet. All five persisted October 5 committed state entries survived, and 16 pre-redeploy validator commit records remain. Fresh weight confirmation in the restarted validator is still pending; this release does not claim it has completed.

The earlier deployment had a known degraded-health window during weight commit/reveal recovery; sparse scheduled probes did not sample the whole interval. A new staging process can likewise wait through a startup fence before confirming its own weights. Do not interpret successful process startup as fresh weight confirmation.

Immutable images

  • Validator: ghcr.io/endure-network/endure-subnet-validator@sha256:cbc18cd0b1b46029fb2b58e8e46c1374569aec137ef74c4c82bf87d84e2cddad
  • Miner: ghcr.io/endure-network/endure-subnet-miner@sha256:58d6cbc62e4465f55976931bb6a20acb2075d01acb13e8e212cf7794ba9e3f69

Both were published from the qualified staging source. Production publication passed, and independent registry reads verified that :prod, :v0.1.2, and the source SHA tag all resolve to exactly these manifests. No images were rebuilt during production promotion.