Release/2.0.0

[basfroman]

Note

High Risk
Breaking public API and FFI for weight commitments, with reveal timing driven by new chain-parity simulation—wrong epoch logic would cause commits to miss on-chain reveal windows.

Overview
v2.0.0 replaces legacy commit-reveal timing with a stateful epoch model aligned with dynamic subnet tempo on chain.

Breaking API: get_encrypted_commit is removed in favor of get_encrypted_commit_v2, which takes epoch schedule fields (last_epoch_block, pending_epoch_at, subnet_epoch_index, tempo, blocks_since_last_step, current_block) instead of netuid plus modulo-based (block + netuid + 1) / (tempo + 1) math. Python, PyO3, and C FFI (cr_generate_commit_v2 in bindings.h) all follow the new signature; cr_generate_commit is gone.

Core logic: New epoch_schedule module simulates block_step / run_coinbase (including mempool COMMIT_INCLUSION_BLOCK_OFFSET and reveal-before-coinbase ordering) via predict_first_reveal_block, then maps the reveal block to a Drand round as before. Shared constants move to constants.rs.

Tests & docs: Table-driven Rust vectors and FFI/Python contract tests cover v2; legacy Python commit-reveal round-trip tests are dropped. README and changelog document the migration (bittensor>=11.0.0 / get_epoch_schedule_state). Package version is 2.0.0 (maturin reads version from Cargo.toml).

^{Reviewed by Cursor Bugbot for commit 0dff71e. Bugbot is set up for automated code reviews on this repo. Configure here.}