Upgrade to animica 7.1.1 before block 42,000
Animica's consensus rules tighten at two coordinated block heights. Every full node — miners, pools, exchanges and self-hosted wallets — must be running 7.1.1 (or newer) before block 42,000, or it will diverge from mainnet and stop following the real chain.
What is changing
Two forward-only consensus rules activate at fixed block heights. They are grandfathered below their activation height, so history the network already accepted stays valid.
Consensus address-freeze
Block import rejects any block containing a non-coinbase transaction that spends from — or pays to — a known-compromised address. It's a validation-only reject rule: it writes no state and never halts the honest chain. The frozen set is a single entry: the ANM-2026-07 attacker address, already clawed back and holding ~0 ANM. No ordinary address is affected.
Foundation subsidy split
The per-block mining subsidy is re-split 85% miner / 15% foundation treasury — total emission is unchanged. This is an emission change, not a reject rule: an older node stays on the same chain but keeps crediting the whole subsidy to the miner, so it silently reports wrong balances. Anyone tracking balances — exchanges, explorers — must run 7.1.0+ to stay accurate.
Who must act
- mustMiners & pool operators — an un-upgraded miner builds blocks the network rejects; your rewards land on a dead fork.
- mustExchanges & custodians running their own node — deposits/withdrawals will track a non-canonical chain if you don't upgrade.
- mustFull-node / RPC / self-hosted wallet operators — your node silently diverges at block 42,000.
- safeUsers of hosted Animica services (animica.org, wallet.animica.org, the explorer, the pool front-end) — nothing to do; that infrastructure is already on 7.1.1.
How to upgrade
Install the latest release and restart your node before block 42,000.
# upgrade the node software (delivers 7.1.1) pip install -U animica # confirm the version, then restart your node/miner/pool process animica --version # → animica 7.1.1
What happens if you don't
The two rules fail differently — and the second is easy to miss.
Fork off the network
The freeze becomes a block-validation rule. An un-upgraded node stops enforcing it, so if a block spending the compromised address is produced, the upgraded majority rejects it while your node accepts it — splitting you onto a dead minority fork that no longer tracks mainnet. Upgrading is the only way to be guaranteed on the canonical chain.
Silently wrong balances
This one does not reject blocks. Your node stays on the same canonical chain but keeps crediting 100% of the subsidy to the miner, so every balance it reports drifts from the network's — with no visible error. Exchanges, explorers and anyone settling on reported balances must upgrade, or they will quote and pay out wrong numbers.
Recovery in both cases is the same: install 7.1.1 and let your node re-derive state on the canonical chain.
FAQ
Are my funds at risk?
No. The address-freeze affects exactly one known-attacker address (already clawed back). No legitimate balance is frozen, moved, or altered by these forks.
I only use the web wallet / hosted explorer. Do I need to do anything?
No. Hosted Animica services already run 7.1.1. This notice is for operators who run their own node software.
Is this a new token, airdrop, or migration?
No. No genesis, no token swap, no address change. It is a software upgrade that tightens consensus at two block heights.
Can I set the activation height manually?
Each fork honors an ANIMICA_FORK_<NAME>_HEIGHT override, but the coordinated mainnet heights (42,000 / 42,001) are compiled into 7.1.1. Simply upgrading is the supported path — don't override on mainnet.
How do I know I upgraded in time?
Run animica --version (must read 7.1.1) and check your node's head at height ≥ 42,001 matches the public explorer/RPC.