v0.1.2 — Owner-controlled burn, protocol 2043

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.

v0.1.1 — Alpha Risk, protocol 2042

SN30 consensus-correctness cutover and the standing owner-vote fallback, under protocol key 2042. The economics remain experimental, and mainnet serving still needs the explicit operator acknowledgement.

• Package/API version: 0.1.1
• Protocol key: 2042, replacing 2041. Miners and validators upgrade together; a key-2041 peer is rejected with VERSION_MISMATCH.
• Source commit: f664a0002b0127080c32d6534b2f4fb3d294d23c
• Platform: Linux/amd64
• Chain parameters: unchanged. SN30's weights_version stays 2040, which accepts key-2042 submissions.

A served Alpha Risk validator now votes for the subnet owner whenever no miner score is positive, instead of abstaining, and returns to earned weights as soon as any score is positive, with no flag flip or restart. Every consensus decision is covered by the protocol digest, reveal persistence and snapshot closure are atomic, and the stake floor, commit/reveal caps and epoch length are fixed protocol values on served networks. This release adds no schema migration and no new dependency.

See the release notes, operator upgrade and rollback, the coordinated cutover, the economic limitations and the CHANGELOG. Full change set and review history: #72.

Production tags reuse the exact published staging candidate digests without rebuilding. Coolify builds separately from the same source; its deployed image digest is not asserted to equal these registry digests.

Published images

• Validator: ghcr.io/endure-network/endure-subnet-validator@sha256:ffd82fab195670a66ea376ddda8b045d6f347e4a07293e75389176eac72d6336
• Miner: ghcr.io/endure-network/endure-subnet-miner@sha256:8521489609cfb2ac584c76bec96955c6d4714ec1caa93584dc17bf89660f2b3e

For each role, :testnet, :prod, :v0.1.1, and the source-SHA tag resolve to the digest above at publication. The attached release-images.env preserves the source-to-digest record.

Verification

• Exact-source CI (1,629 tests, migrations, lint, types, guardrails, quality and deploy assembly), localnet qualification and candidate publication passed for the source commit.
• Production publication preserves the candidate digests; anonymous registry readback is attached.

Testnet soak

The source commit ran on the Endure testnet validator (SN504) from 2026-09-26T16:35:45Z and had run for 36 hours 40 minutes without a restart when this tag was cut. Checkpoints from the release decision:

• Confirmed key-2042 weights: the first key-2042 commit landed at block 8089423 and was revealed at 8089696 (WeightsSet(504, 0)). Weights kept confirming through the soak; the last confirmation before tagging was at 2026-09-28T04:37:51Z.
• Restart: the redeploy carrying this version restarted the validator at 16:35:45Z, and its weights confirmed again by 16:59Z.
• Full round cycle: round 2026-09-26 ran its commit (11:00–19:30Z) and reveal (20:30–00:00Z) windows on key 2042 and accepted 10 submissions from 10 distinct miners, including all five soak miners; its data published on schedule at 19:30Z on 2026-09-27. Resolution and publication also ran on this commit: on 2026-09-27 round 2026-08-27 closed after its 30-day horizon and round 2026-09-21 scored its 5-day horizon, and round 2026-09-25 published at 19:30Z on 2026-09-26 (10 submissions, 120 consensus rows).
• Probes: all 11 soak health-probe runs between the redeploy and the tag passed.

Known behaviour: /health can report degraded (HTTP 503) shortly after 00:30 UTC while the daily resolution passes run past the 30-minute overdue grace, and clears when they finish. /live, scoring and weight setting are unaffected.

v0.1.0 — Alpha Risk

Initial Alpha Risk release with experimental economics and explicit operator acknowledgement for mainnet serving.

• Package/API version: 0.1.0
• Protocol key: 2041
• Source commit: 05d2e7f2dd110841ec801a43eec83589cbf6b657
• Platform: Linux/amd64

This release includes signed commit/reveal submissions, bounded reveal persistence, the 15-subnet universe, active-coordinate scoring with retired reputation preserved, and independent validator/miner installation.

The owner accepted the accumulated staging run and the documented initial-release limitations on September 20, 2026, authorizing image publication while staging continues. This is a scoped exception to the default unchanged-revision soak requirement; economic acceptance, independent-validator qualification, and other disclosed limitations are not represented as resolved.

See the release decision and rollback guidance, economic limitations, and container installation guide.

Production tags reuse the exact published staging candidate digests without rebuilding. Coolify builds separately from the same source; its deployed image digest is not asserted to equal these registry digests. Publishing this release does not deploy any mainnet service or move wallets or funds.

Published images

• Validator: ghcr.io/endure-network/endure-subnet-validator@sha256:9b97df0c9d80a9570744a8b8d5d3462bab3fe7abc4d1b3ad86b4530ff6b4536e
• Miner: ghcr.io/endure-network/endure-subnet-miner@sha256:05a294d15337aba92e6dbec6488324fcc4aeda69b29b709cb351dcee17234d8c

For each role, :testnet, :prod, :v0.1.0, and the source-SHA tag resolve to the digest above at publication. The attached release-images.env preserves the source-to-digest record.

Verification

• Full local gate: 1,400 tests, 18 migration checks, lint, types, guardrails, Gitleaks, and duplication checks passed.
• Exact-source CI, localnet qualification, and candidate publication passed.
• Production publication preserves the candidate digests; anonymous registry readback is attached.