Validators and voting
Validators validate transactions and blocks. Holders use votes to express support for the validators they want participating in the network.
The consensus design describes the draft’s elected set and how block production relates to finality.
Operating a validator
Section titled “Operating a validator”The intended mainnet has 53 elected validator seats. Operating one involves:
- Running a relay to validate and relay blocks, and a separate forger to sign scheduled blocks. Keep the account key off servers and each consensus key on exactly one forger. See Validator hardening.
- Running an IceRoot Connector on a separate machine or service to reproduce migration lists, using your own source-chain node or a declared provider. See Connector adapters.
- Maintaining availability, monitoring finality, and installing releases before their activation heights. Missed slots earn no block reward but carry no penalty; proven equivocation leads to jailing and withheld rewards, with no stake slashing.
- Publishing an operating proposal, declaring your operator, hosting provider, country, and source-chain access, and declaring any reward-sharing terms. A portal proposal is separate from on-chain registration and does not secure a seat.
The team handpicks the testnet validators, and later the 53 independent mainnet genesis validators from the public testnet’s operators, based on availability, contribution, and participation. For mainnet it looks for commitment, reliable uptime, and independence. There is no published points formula or minimum bar. After genesis, elections decide seat changes. ROOT supply and distribution explains the proposed rewards; they are not guaranteed income.
One validator per operator. Anyone who creates or runs more than one validator loses their mainnet seat, with no exception. This is a team policy for selection, not a consensus rule: consensus cannot tell whether different validator identities belong to the same operator. The relay, forger, and optional sentry relays of one validator are not additional validators.
How to apply
Section titled “How to apply”- Tell the team on Discord that you want to become a validator.
- Sync a lab devnet node completely, and accept outside peers so that the network’s nodes can connect to it. Keep it running.
- Send the team on Discord your node’s public address and P2P port, and the output of the two commands under Sync proof. The team then checks your node.
- If accepted, receive testnet tokens for registration and a dedicated validator role on Discord.
- Register your validator and keep your operating declarations and contribution record current.
Application and announcement invite: join the IceRoot Discord.
Sync proof
Section titled “Sync proof”The proof is a check that the team makes on your running node. Two things must hold at the time of the check:
-
The network sees your node. Your node’s address and P2P port appear in the peer list of the lab devnet’s relays and public reference node, with a height at or within a block or two of the current chain height. This is why the node must accept outside peers: a node that cannot be reached cannot be checked.
-
Your node reports itself synced on this chain. Run these two commands on the node and send the team the output:
Terminal window curl -fsS http://127.0.0.1:6003/api/node/statuscurl -fsS http://127.0.0.1:6003/api/blockchainThe status must show
"synced": true, and the block ID and height from the second command must match the block at the same height on scan.iceroot.com.
Use your own API port in the commands if you changed it. Keep the node running after you apply, because the team may check again before accepting you. A passed check shows a working, synced node. It does not secure a seat; selection works as described above.
Follow Network status. Publishing a portal profile does not submit an application or reserve a seat. A testnet token faucet bot is planned for later.
The relaunched public testnet is meant to be attacked and broken. Validators there are encouraged to crash nodes and look for attack vectors, and to report what they find privately under the security policy. That is why there is no points formula for validators.
The team handles participation case by case. How the 10,000,000 ROOT participation pool is split, the caps per participant, and its detailed rules are not decided yet. See Testnet and launch participation.
Hardware planning estimates
Section titled “Hardware planning estimates”These are planning estimates, not requirements. They allow room for synchronization, bursts of connections, and chain growth. Measured minimums will replace them before the early public testnet opens. There are no long-chain measurements or measured Rust memory minimums yet.
| Role | CPU | Memory | Storage | Network |
|---|---|---|---|---|
| Validator relay | 4 vCPU, dedicated preferred | 8 GB | Start with 250 GB NVMe SSD | 1 Gbit/s port; less traffic behind sentries |
| Optional sentry relay, each | 4 vCPU | 8 GB | Start with 250 GB NVMe SSD; retains the full chain | 1 Gbit/s port with DDoS protection; plan for 0.5 to 1 TB a month |
| Forger | 2 vCPU | 2 GB | 20 GB | Private link to two or three relays |
| Connector using a declared source-chain provider | 2 vCPU | 4 GB | Storage estimate not set | Separate machine or service |
Running your own Ethereum node adds separate resources. Allow roughly 2 TB or more of NVMe storage and 16 to 32 GB RAM as a planning estimate, then check the selected client’s current guidance. Heartwood nodes and operator tooling currently support Linux only; the tested architecture is x86-64. Keep clocks synchronized with NTP and follow the hardening guide.
The estimates use the following assumptions:
- Storage: 8-second slots give about 3,942,000 blocks a year. Headers of about 3.55 KB, mostly the 3,309-byte signature, add about 14 GB a year. Allow about 6 GB for database overhead, extrapolated from early, nearly empty blocks. Transactions of about 3.6 KB plus indexing add about 14 GB a year at 10,000 transactions a day. Allow roughly 20 to 35 GB a year at modest activity, or about 165 GB at 100,000 transactions a day. Every relay retains the full chain; there is no pruning.
- Memory: an account’s 1,952-byte public key brings estimated state to about 2.4 KB per account, or 2.4 GB per million accounts if state is held in memory. The relay also needs room for its database cache and transaction pool. The forger does not hold that state.
- CPU and disk: early measurements put signature verification at about 41 microseconds with a cached key and 99 microseconds from encoded bytes on one core of a fast desktop CPU. Database commits were limited mainly by disk synchronization. The table leaves headroom for initial sync and connection floods, not just ordinary block processing.
- Bandwidth: broadcasting to about 100 peers gives roughly 115 GB a month for an empty chain and 330 GB at 10,000 transactions a day, before serving history to new nodes. A hypothetical 0.54 MB block sent to 100 peers in one second needs about 430 Mbit/s. This illustrates burst capacity; block limits are still undecided. Peer broadcast behavior may also change.
These estimates exclude extra public API and history services. Monitor disk use and allow for logs, larger votes, and new accounts as activity grows.
What remains unsettled
Section titled “What remains unsettled”Several values in the whitepaper are not fixed yet, including the base fee rate, block and transaction size limits, the finality vote window, how long jailing and withheld rewards last, how a forger on a separate host authenticates to its relay, the evidence procedure for false migration attestations, and the payout grace window for reward sharing. The participation pool split, the caps per participant, and anti-abuse conditions beyond one validator per operator are not decided yet. The detailed participation rules, validator independence statement, and sync proof procedure are not published yet.
Follow Network status for release updates, and see Protocol design for other open details.
Compare validators
Section titled “Compare validators”- Explorer (live public lab devnet): check status, blocks, scheduled slots, and recorded votes.
- Validator portal: read the proposal and contribution history.
Look for:
- The validator’s operating approach and availability.
- Concrete tools, infrastructure, documentation, or community work.
- A clear reward policy, where one is offered.
- The consistency between the proposal and published work.
Reward policies in the portal are supplied by the validator. They are not a network guarantee. The draft protocol adds on-chain declarations, which the indexer compares with actual payouts, described below.
Vote in a wallet
Section titled “Vote in a wallet”The screenshots and sample walkthroughs use simulated data. The unreleased desktop development build also connects to a local classical devnet for balances, history, sending and four automatic vote-selection modes. Browser and mobile integration is still in progress. No mainnet funds or released wallet downloads are available.
In the sample walkthrough below, a vote only updates the sample session: nothing is signed or sent, and no validator is elected.
- Choose the wallet whose vote you want to manage.
- Open Validators or Governance.
- Select the validators you want to support, 20 to 53 of them, and read their details.
- Choose the vote action, review it, and continue to the result.
Removing a vote follows the same review flow. The wallet’s activity list records the outcome for the selected environment.
Proposed voting rules
Section titled “Proposed voting rules”The draft protocol sets these limits from the IceRoot genesis:
| Rule | Draft value |
|---|---|
| Who can vote | Any account except a validator account |
| Validators named in a vote | 20 to 53; an empty vote withdraws the current vote |
| Share for one validator | At most 5% of the voting account’s weight |
| Total allocation | A nonempty vote totals 10,000 basis points (100%) |
| Vote weight | The account’s liquid ROOT balance; nothing is locked or bonded |
| Accounts with liquid ROOT above 5% of ROOT’s supply | Zero vote weight at that round’s snapshot; the vote counts again once the balance no longer exceeds the threshold |
| Vote contents | At most 1,280 bytes, so a vote naming all 53 validators always fits |
Every node enforces these rules. They limit how vote weight can be concentrated; they do not determine whether several accounts or validators belong to the same person or organization.
The threshold is 5% of ROOT’s supply at each round’s snapshot, rounded down to whole base units. Supply here is issued minus burned ROOT, and it includes ROOT held in hash time-locked transfers and time-locked entries. An account exactly at the threshold keeps its vote weight. A validator account that resigns permanently can vote again; a temporary resignation keeps the restriction. A temporary resignation immediately removes eligibility to win a seat. A seated validator remains in the set and is expected to keep producing blocks until the next finality-gated set change that replaces it, one seat per change, as for jailing. A revoke restores eligibility from the next election check without guaranteeing a seat.
- Zero weight above 5% of supply keeps a large custodial or omnibus balance, such as the ROOT an exchange holds for its customers, from automatically becoming election power. A holder can still split ROOT across smaller accounts, but the resulting vote weight then comes from a deliberate restructuring, not passively from custody.
- At most 5% per validator keeps one holder’s large vote weight from collapsing behind one validator identity, and splitting ROOT across accounts does not change that proportion. A holder with 20% of all eligible vote weight can give any one validator at most 1% of all eligible vote weight from its own holdings. The rule cannot tell whether one organization runs several validators, so such an organization could still spread its weight across them. The team’s one validator per operator policy applies to selection, not to consensus.
- Validator accounts cannot vote, so block rewards credited to a validator account never turn into votes directly. An operator can still move ROOT to another account and vote from there. The rule stops direct voting by the validator account and makes simple reward recycling easier to see; it does not establish that a validator and its voters are separate.
These rules add friction for concentrated holders without getting in the way of ordinary holders, who are very unlikely to hold 5% of the supply. Together with the limit of one seat change per election check, they make concentrated influence slower, more cumbersome, and easier to observe; they do not make coordinated capture impossible.
Because each vote names at least 20 validators, wallets can propose a selection for you. Every IceRoot wallet uses one shared, open-source scoring library that works from public data, so anyone can reproduce a selection:
- Diversity, the recommended mode, spreads the vote across different declared operators, hosting providers, regions, and rank bands.
- Reliability favors validators with a strong recent record, computed from chain data over a rolling 30-day window: slots forged against slots assigned, with no jailing or equivocation. A validator needs at least 7 days of seated history to count.
- Maximum Rewards favors the highest measured payouts per unit of vote weight, taken from actual payouts rather than declared rates, and capped per operator. Past payouts are not a promise.
- Support Newcomers favors healthy validators near or below the cutoff for the 53 seats: registered for at least 7 days, with complete declarations and no penalties.
- Manual leaves every choice to you.
Each mode samples its picks from its eligible validators separately for each account, so holders who choose the same mode do not all vote for the same validators. If a mode has too few eligible validators for a full vote, it tops up from Diversity and says so. The review screen shows why each validator was picked, and you can change any pick before signing. No vote ever moves without your signature: when a selection no longer meets its mode’s criteria, the wallet tells you and proposes a new one for you to review.
The genesis block carries no votes, so every genesis validator starts with zero vote weight. The IceRoot team selects the 53 genesis validators from operators on the public testnet, and each applicant confirms the validator independence statement, once it is published. That selection is a launch policy, not a consensus rule, and it cannot prove that operators are unrelated. From the first election check on, seats follow vote weight, at most one seat per check.
The team account and the genesis pool accounts may vote under the team voting policy, which is not published yet, within the same rules. A pool account holding 10,000,000 ROOT or more starts above 5% of the supply, so it carries no vote weight as one account; the 5,000,000 ROOT Community and ambassadors pool sits exactly at that threshold, so it can vote as one account. Participation allocations go directly to participants. See ROOT supply and distribution.
Proposed validator rules
Section titled “Proposed validator rules”- Registration: a validator registration pays a 250 ROOT surcharge on top of the size-based fee. It records the validator’s name and its consensus, node, and migration attestation keys, each with proof of possession. An account that already has a name registers under it. Registration is refused while the account has an active vote.
- Reward sharing: a validator declares a share from 0 to 10,000 basis points, a payout interval of one or seven days, and a payout address with
SHARE_DECLARE. Every declaration pays a 25 ROOT surcharge on top of the size-based fee. Consensus stores the terms and pays nobody. The indexer applies a change 24 hours after its block, or at the start of the next interval if that is later. It computes each interval’s pool as the validator’s forger payouts after donations, multiplied by the declared share. A voter’s expected share is the pool times that voter’s time-weighted share of the validator’s vote weight over the interval. A voter’s credit is what it received from the payout address, capped at its expected share, so paying one voter extra never covers another voter’s shortfall. The explorer and wallets show owed and received amounts. Nothing enforces payment. - Transparency: outside consensus, validators declare their operator, hosting provider, and country in a standard memo that the indexer reads. The explorer shows seats and vote weight per declared operator and per hosting provider, with an alert when one reaches 6 seats and again at 18 seats. It also shows how much of each validator’s vote weight comes from addresses its validator account funded directly, an observed funding relationship. Declarations are self-reported. These views expose declared and observable relationships to inform votes; they cannot prove that validators are independent or reveal ownership that nobody discloses.
- Source-chain access: each validator reads Ethereum through its own node or a publicly declared provider. The limit of 17 validators per provider is a declared policy, applied during onboarding and shown on the explorer, not a consensus rule.
- Hosts: a validator keeps its account key off every server and can keep the relay that presents its registered node key private behind optional sentry relays. Validator hardening covers keys, sentries, ports, and firewall rules.
Surcharges are fees: like every fee, 90% is burned and 10% goes to the forging validator.
In the draft, any account can hold one name, and validators and other accounts share one namespace. A name is 1 to 20 lowercase letters from a to z, with no digits, capitals, or symbols. Consensus refuses:
- Names that contain
icerootorheartwood, except the IceRoot team’s own names in the genesis block. - Names on a short reserved list, such as
admin,support, andofficial. - Names that contain a word from the published banned-words list.
| Action | Draft rule |
|---|---|
| Register | NAME_REGISTER gives the sending account its name for a 125 ROOT surcharge. A name has no renewal or expiry. |
| Transfer | The holder signs an authorization off-chain. The recipient must be a fresh account and submits it with NAME_CLAIM as its first transaction, for a 125 ROOT surcharge. |
| Validator names | The name of an account that is or ever was a validator never moves. |
A name is a label, not proof of identity. Wallets and the explorer always show the address next to it, with the name’s age and how often and when it last changed hands.
Understand Candidate status
Section titled “Understand Candidate status”A signed portal account proves control of a key. It does not prove on-chain registration, rank, or uptime. The portal presents new signed identities as Candidates until network registration can be verified.
Running a validator and publishing a proposal are separate steps. Start with your proposal to describe the service you provide, and read Validator hardening before you prepare your hosts.