v0.1.3 — Identical-forecast pooling, protocol 2044

Endure v0.1.3 moves scoring to protocol key 2044. Miners that reveal identical forecasts share one payout: a pool earns what its best member would earn alone. See the release notes for the upgrade and rollback steps, and Identical forecasts share one payout for the rule. Pooling prices exact replication only; the economic limitations still apply.

Upgrade

• Miners and validators upgrade together, between 00:00 and 11:00 UTC. A key-2044 validator rejects key-2043 submissions.
• No migration and no chain-parameter change. The burn rate commitment (endure.burn_bps=9800) is unchanged.
• Two startup checks: the market-data endpoint must be a mainnet archive, and health_tick_max_duration_seconds must exceed resolution_budget_seconds + 600. The defaults pass both.
• Upgrade once the canary, UID 195, has a confirmed key-2044 vote and its /miners reports pool_size. We announce it when it does.

Release identity

• Tag commit: e678c65ff7658133dcf30eb4c45fbdee7508c655, the staging commit testnet runs. It adds only docs and CI to the release commit f65d9e0 (#84), so both run the same code.
• Version 0.1.3, protocol key 2044, protocol digest 777d3671ffd72c112fd853dc018c7f38449821da16a9d8539f113b07cc35ed47.
• Content revision f21318874c043f136f626b1bd0f4f7af4a2a4be64456219e7982b601d11cb186.

Soak checkpoints (testnet, owner's scoped exception of 2026-10-16)

• Private qualification on the release code (f65d9e0): make verify (1,898 tests) and a local devnet run (16 of 16 checks; identical reveals share one payout, and a restart rebuilds the pools). The owner waived repeating it on e678c65, which differs only in docs and CI.
• CI, localnet qualification and image publication passed on e678c65.
• /health reported key 2044, f65d9e0 and the content revision above at 08:08 UTC on 10-20.
• First confirmed key-2044 vote: 11:30 UTC.
• Deliberate restart at 11:34 UTC. Coolify performed it as a redeploy of staging's tip, e678c65, with the same content revision. The restarted process confirmed its predecessor's vote at 12:41 and its own at 13:48.
• Full round 10-20, on key 2044 from its commit window to its reveal close: revealed at 00:00 on 10-21, with its tie seed (finney block 9,328,179) readable from the mainnet archive. The vote computed after it confirmed at 01:55 UTC: 98.00% to the owner at the 9800 burn, 2.00% across 17 miners, including two pools of two.
• Noted: two horizons due at midnight resolved at 00:53 and 01:01, past the 30-minute grace, so testnet /health read degraded for half an hour, with no failures.

Images

• Validator: ghcr.io/endure-network/endure-subnet-validator@sha256:f8f594406b6af57c77eff4a87dba88d8fb61a1daca02a1e263e2eb1f74cc429c
• Miner: ghcr.io/endure-network/endure-subnet-miner@sha256:8cde423f465c99e4aad45c95a6454c6cfb5973d20baddd0ffd545ec42b197381

Both carry exactly e678c65's code (checked layer by layer). Production publication retagged them without rebuilding, and registry reads at 05:14 UTC confirmed that :prod, :v0.1.3 and sha-e678c65… resolve to exactly these digests.

Mainnet

• The canary, UID 195, has run v0.1.3 since 05:34 UTC on 10-21. Its first key-2044 vote confirmed at 06:55 UTC, and its /miners reports pool_size. Operators can upgrade now.
• UID 176 has run v0.1.3 since 07:04 UTC; its first key-2044 vote confirmed at 08:25 UTC.