Consensus Parameters
Consensus parameters are a set of configurable settings that determine how the Anemos blockchain operates. These parameters are agreed upon by all validators in the network, ensuring that validators behave in the same way and that the network operates consistently.
Here is the list of the consensus parameters:
Protocol Version
The version number of the blockchain protocol. Anemos ships a single protocol version with no enabling flags — split-reward, delegation, the consensus-embedded oracle, and the native stablecoin are all base protocol, active from genesis.
Block Time
The time interval in seconds between the creation of two consecutive blocks. This is set to 10 seconds, which means that a new block is created every 10 seconds.
Committee Size
The number of validators in the committee (the active set that proposes and votes on blocks). It is a genesis parameter, so it differs per network:
- Mainnet: 75 — matching the oracle target.
- Testnet: 11 — matching the oracle subset size.
- Localnet: the committee fills from the available validators you create.
The committee must exceed the number of genesis validators so a newly bonded validator’s power can clear the displacement rule and join the committee.
Block Reward
The reward given for each new block is minted by the emission schedule rather than being a fixed
constant: it follows a smooth, Kaspa-style geometric decay (from an initial 2 ANM/block) toward a
supply-indexed perpetual tail (≈2% of total supply per year, leading-digit “laddered”). Each
block’s reward R(h) is a pure function of the block height h, so every node computes the same value.
The reward is split between the block proposer (and its delegate) and the native
stablecoin reserve. See Incentive for the
emission curve and the reward split.
Time-to-Live Interval
The number of blocks that a transaction can remain unprocessed before it is removed from the transaction pool. This is set to 8640 blocks, which is almost one day.
Bond Interval
The minimum number of blocks that must elapse after a validator has submitted a bond transaction before they can participate in the consensus process and join the validator committee. This is set to 360 blocks, which is almost one hour.
Unbond Interval
The minimum number of blocks that must elapse after a validator has submitted an unbond transaction before they can withdraw their staked coins. This is set to 181,440 blocks, which is almost 21 days.
Sortition Interval
The maximum number of blocks that a sortition transaction can remain valid and be included in a block. This is set to 17 blocks on mainnet (the testnet generator uses 7 for faster validator-lifecycle testing).
Maximum Stake
The maximum amount of coins that can be staked by a validator. Unlike the original fixed cap, Anemos
makes this a height-resolved, supply-indexed value: it is ladder(0.008 × total supply), a
leading-digit-laddered, monotone-latched (only ever steps up) function of committed minted supply.
At the launch fair-launch supply (8,000,000 ANM) this is 60,000 ANM (60,000,000,000,000 Gust).
A fixed nominal cap would become a dust fraction of an elastic supply and stop bounding stake
concentration, so the decentralization brake scales with supply (the same survival logic as the
supply-indexed block-reward tail).
Minimum Stake
The minimum amount of coins that can be staked by a validator. It tracks the maximum stake at 1/50 of it (v0.7 tighter stake range — raised from 1/1000), so it is likewise height-resolved and supply-indexed. At the launch supply this is 1,200 ANM on mainnet and 800 ANM on testnet. A higher floor keeps dust validators off the committee and tightens the cap-to-min spread to 50:1, while the maximum stake (the 0.008 ladder) is unchanged.
Committee Term Limit
The maximum number of consecutive blocks a validator may hold a committee seat before it must rotate out. On mainnet and testnet this is 2,880 blocks (≈ 8 hours); on localnet it is 0 (disabled). When a seated member exceeds its tenure it is denied a re-sortition, ages to become the longest-serving member, and is then evicted the next time a replacement validator joins — eviction is always paired with a join, so the committee never drops below its size or quorum and never breaches the per-block rotation cap. Tenure is measured purely from committed on-chain state, so the rule is deterministic and adds nothing to the genesis hash. Term limits keep committee membership churning, which is the security compensator for the faster v0.7 oracle price time-weighted average.