# ROOT supply and distribution

> ROOT's genesis supply, the seven genesis pools, the team lock, fee grants, and block rewards in the draft protocol. IceRoot holds no token sale.

Source: https://docs.iceroot.com/network/root/

ROOT is not live. This page describes the intended mainnet in a working specification whose parameters, economics, and validator rules may change. The production Rust node is still being built, a reference devnet runs now, and the public testnet has not launched. See [Network status](https://docs.iceroot.com/network/status/index.md) and [Protocol design](https://docs.iceroot.com/core/protocol-design/index.md).

ROOT is IceRoot’s native asset. It pays every transaction fee, carries the vote weight in validator elections, and pays validator rewards. It has 18 decimals, so 1 ROOT is 10^18 base units.

## No token sale

IceRoot sells no ROOT. There is no public sale, no presale, and no private round, before or after launch, and neither the team nor any genesis pool sells ROOT. ROOT enters circulation through contribution, participation, and validator rewards.

The rule binds the project and its pool accounts. ROOT paid from the team allocation to individuals as compensation belongs to them.

## Genesis supply

The genesis block issues 100,000,000 ROOT, which is 10^26 base units, through an explicit issuance record. No account ever holds a negative balance, genesis included. The supply is divided into seven labeled pools:

| Pool                             | ROOT            | Base units                              | Share    |
| -------------------------------- | --------------- | --------------------------------------- | -------- |
| Security and bug bounty          | 30,000,000      | 30,000,000,000,000,000,000,000,000      | 30%      |
| Team                             | 20,000,000      | 20,000,000,000,000,000,000,000,000      | 20%      |
| Developer ecosystem              | 15,000,000      | 15,000,000,000,000,000,000,000,000      | 15%      |
| Testnet and launch participation | 10,000,000      | 10,000,000,000,000,000,000,000,000      | 10%      |
| Ecosystem campaigns              | 10,000,000      | 10,000,000,000,000,000,000,000,000      | 10%      |
| Long-term reserve                | 10,000,000      | 10,000,000,000,000,000,000,000,000      | 10%      |
| Community and ambassadors        | 5,000,000       | 5,000,000,000,000,000,000,000,000       | 5%       |
| **Total**                        | **100,000,000** | **100,000,000,000,000,000,000,000,000** | **100%** |

Every pool except the participation pool is held in its own account. Each pool account is a 2-of-3 native multisig account, so any two of its three keys must sign, and the explorer labels it with a name that contains the word “pool”.

The Development fund and the Ecosystem fund, which receive part of every block reward, are separate accounts. They are not genesis pools and receive no genesis allocation.

## Team allocation

The team account holds the Team pool’s 20,000,000 ROOT. In the first blocks after genesis, it locks 18,000,000 ROOT on chain in 16 quarterly tranches of 1,125,000 ROOT each, using non-revocable [time-locked transfers](https://docs.iceroot.com/network/assets/index.md#proposed-swaps-and-time-locks) payable to itself. The first tranche unlocks three months after genesis and the last four years after genesis. The other 2,000,000 ROOT stay liquid.

No one can revoke the locked entries, the team included. Locked ROOT carries no vote weight, and anyone can see every entry, its amount, and its unlock time.

## Testnet and launch participation

Validators, testers, and builders earn shares of the 10,000,000 ROOT participation pool on the relaunched public testnet. The team handles participation case by case. How the pool is split between those groups, the caps per participant, and the detailed earning rules are not decided yet, and no publication date is set. The public testnet has not launched.

1. **Take part.** Join the relaunched public testnet. Validators apply as described in [How to apply](https://docs.iceroot.com/network/validators/index.md#how-to-apply); the team selects them by availability, contribution, and participation, with no published points formula or minimum bar. Anyone who runs more than one validator loses their mainnet seat, with no exception.
2. **Bind.** From your testnet account, send a binding transaction whose memo names your mainnet address. Your testnet key signs it, and it names where your share goes.
3. **Receive.** The mainnet genesis block credits each bound share directly to its address, so the ROOT is liquid from block 1 and needs no claim transaction.

Shares that are not earned or not bound go to the Long-term reserve, whose genesis balance is therefore at least 10,000,000 ROOT. Testnet balances never carry over to mainnet.

## Programs and payouts

Five pool accounts follow the [program list](https://docs.iceroot.com/programs/index.md): Security and bug bounty, Developer ecosystem, Ecosystem campaigns, Long-term reserve, and Community and ambassadors. They pay out over time; earned bounties from before mainnet are credited directly at genesis from the relevant allocation. The Team account and the Development and Ecosystem funds show balances and transfers on the explorer without program entries. Participation shares are direct genesis allocations, with no participation pool account.

- **Program list.** [iceroot-network/programs](https://github.com/iceroot-network/programs) is the public repository for the list, bounty record, monthly statements, and bindings. Each entry has one file and one id, checked on every pull request.
- **Approval.** An entry must be listed before payment, and the payment must match it. Two of the pool account’s three keys approve the payout. There is no waiting period after listing.
- **Memo.** Every payout transaction from these five pools carries `iceroot:pay:v1 <entry id> <fingerprint>`, where the fingerprint is 64 characters and identifies the entry’s payment details. Consensus never reads the memo; the indexer and explorer use it to link the payout to its entry.
- **Security and bug bounty.** The Security and bug bounty pool funds bug bounties, security audits and reviews, and security research, under the same program list and approval rules as the other pools.
- **Contribution rewards.** Accepted code, documentation, and tests are paid from the Developer ecosystem pool. The [bounty program](https://docs.iceroot.com/programs/bounties/index.md) describes the provisional ROOT table, eligibility, address binding, and monthly payments after mainnet.
- **Related parties.** A payout or grant to a person or project related to the IceRoot team, Monolythium and LYTH included, is marked as related-party on the program list and on the genesis distribution page, with the relationship stated. The same rules and amounts apply as for anyone else. See [About IceRoot](https://docs.iceroot.com/getting-started/about/index.md#monolythium-and-lyth).
- **Genesis distribution page.** The explorer reads the pool accounts live and shows, for each pool, its allocation, the ROOT that is locked, unlocked, and distributed, and every payout with its program entry. See [Use the explorer](https://docs.iceroot.com/network/explorer/index.md#follow-the-genesis-distribution).

The protocol does not enforce how the pools are spent. These measures make every payout visible, so anyone can compare the spending with the published programs. The explorer page also states that IceRoot has sold no ROOT. That is a commitment, not something the chain can prove, because a private sale would look like an ordinary transfer.

## Fee grants

Every fee is paid in ROOT, and IceRoot sells none. A project that launches or migrates an asset can therefore receive a fee grant from the Ecosystem campaigns pool, under published rules. A grant can cover registration surcharges, account names, and small amounts of ROOT for the project’s migrated holders, so they can pay their fees.

See [Launch a native asset](https://docs.iceroot.com/projects/launch-native-asset/index.md) and the [migration guide](https://docs.iceroot.com/projects/migration/index.md).

## Voting by team and pool accounts

The team account and the pool accounts may vote under the team voting policy, which is not published yet. The [voting rules](https://docs.iceroot.com/network/validators/index.md#proposed-voting-rules) apply to them like any other account:

- A pool account holding 10,000,000 ROOT or more starts above 5% of ROOT’s supply, and an account above that threshold carries no vote weight. Participation shares go directly to participants, rather than to one pool account.
- The Community and ambassadors pool’s 5,000,000 ROOT sits exactly at the 5% threshold rather than above it, so the rule does not remove its vote weight, and it can vote as one account under the team voting policy.
- ROOT in time-locked entries carries no vote weight, so the team account votes only with its liquid ROOT: 2,000,000 ROOT until the first tranche is claimed, which is below the threshold.
- Splitting a pool across smaller accounts in order to vote takes deliberate transfers, which the chain and the explorer show.

## Block rewards and issuance

After genesis, ROOT’s supply grows only through block rewards. Each block pays a reward that depends on the forging validator’s seated rank:

| Seated rank | ROOT per block |
| ----------- | -------------- |
| 1 to 10     | 1.8            |
| 11 to 21    | 1.9            |
| 22 to 32    | 2.0            |
| 33 to 43    | 2.1            |
| 44 to 53    | 2.2            |

The mean reward is 2.0 ROOT per block. Each reward pays 5% to the Development fund and 5% to the Ecosystem fund, both 2-of-3 multisig accounts labeled on the explorer, and the rest to the forging validator.

At full production, with a block in every 8-second slot, block rewards issue 7,884,000 ROOT a year, 7.88% of the genesis supply in the first year. About 7,095,600 ROOT of it goes to validators and 788,400 ROOT to the two funds. The reward table is flat, so the rate falls as the supply grows, to about 4.61% in year 10. Missed slots only lower these figures. No maximum supply is coded, and the table changes only through a protocol upgrade at an activation height.

## Fees and burns

Every fee, surcharges included, is 90% burned, rounded down to whole base units, with the remainder paid to the forging validator. No part of a fee goes to the donation funds. The base fee rate is not fixed yet; the [whitepaper’s fee table](https://docs.iceroot.com/reference/whitepaper/index.md#fees) shows which surcharges are set and which are still open.

Holders can burn their own ROOT at zero fee, at least 0.02 ROOT at a time. Burning another asset pays the ordinary size-based fee in ROOT and has no minimum amount. Rewards withheld from jailed validators are burned instead of being paid, so they never add to the supply. The issuance figures above count block rewards before any burn.

[Native assets →](https://docs.iceroot.com/network/assets/index.md) · [Validators and voting →](https://docs.iceroot.com/network/validators/index.md) · [Use the explorer →](https://docs.iceroot.com/network/explorer/index.md)