Program list
iceroot-network/programs is the public repository designated for IceRoot’s program list, bounty record, monthly statements, and account bindings. Each entry has one file and one id. That repository is the shared source for the docs and explorer. This page describes the program scope and payment rules; individual entries are kept in the repository.
Every pull request is checked for unique ids, valid amounts, and spending within each program’s budget. Records of payouts to related parties are marked and state the relationship. Related parties receive the same rates and follow the same rules as everyone else.
Covered pool accounts
Section titled “Covered pool accounts”Only these five program pool accounts follow the list:
| Pool | Genesis allocation | Purpose |
|---|---|---|
| Security and bug bounty | 30,000,000 ROOT | Security and bug reports, audits, reviews, and security research |
| Developer ecosystem | 15,000,000 ROOT | Accepted contributions and developer programs |
| Ecosystem campaigns | 10,000,000 ROOT | Campaigns, including fee grants for launches and migrations |
| Long-term reserve | At least 10,000,000 ROOT | Later programs and allocations; also receives unearned or unbound participation shares at genesis |
| Community and ambassadors | 5,000,000 ROOT | Community and ambassador programs |
The bounty program has provisional reward tables and annual caps for the first two pools. Detailed rules for other programs and their application procedures are not published yet. Pool addresses are not published yet.
The Team account and the Development and Ecosystem funds show their balances and transfers on the explorer without program entries. The 10,000,000 ROOT participation allocation goes directly to participants at genesis and has no pool account. See ROOT supply and distribution.
Approval and payment
Section titled “Approval and payment”An entry must appear on the list before it is paid. The payment must match that entry, and two of the paying pool account’s three keys must approve it. There is no waiting period before payment after listing, including for large or related-party payments.
Bounty payments after mainnet follow the monthly schedule. Security rewards are listed and paid after the advisory is public. New or changed bounty account links have a separate seven-day wait. Those conditions do not create a notice period for program entries.
Payment memo
Section titled “Payment memo”Every payout transaction from a covered pool carries:
iceroot:pay:v1 <entry id> <64-character fingerprint of the entry's payment details>The angle-bracketed fields are placeholders. Use the entry’s actual id and fingerprint. The fingerprint ties the payment to the recorded payment details. The full fingerprint encoding specification is not published yet.
Each payout has its own transaction and memo. A monthly batch is a set of those transactions. Consensus does not interpret the memo; the indexer and explorer use it to connect payments to the public record. The list is a spending policy, not a consensus restriction.
Earned participation shares and pre-mainnet bounty rewards are credited directly in the mainnet genesis. These allocations have no separate payout transaction or payout memo. The explorer’s Genesis distribution page shows allocations and subsequent distributions.