# Publish your proposal

> Introduce your validator and explain what you commit to the IceRoot network.

Source: https://docs.iceroot.com/validators/proposal/

A proposal explains who runs your validator, how it operates, and what you commit to contribute.

Heartwood Core, the production Rust node, is still being built. A public lab devnet runs now, with no value and possible resets at any time; the public testnet and mainnet have not launched. The Heartwood Core repository is public. [Run a devnet node](https://docs.iceroot.com/network/run-a-node/index.md) to follow the lab; validators apply separately. These docs are a working specification: parameters, economics, and validator rules may change. Start with [Operating a validator](https://docs.iceroot.com/network/validators/index.md#operating-a-validator) for the intended duties and the details still open, and follow [Network status](https://docs.iceroot.com/network/status/index.md) for updates.

## Before you start

Applications go to the team, not through the portal: see [How to apply](https://docs.iceroot.com/network/validators/index.md#how-to-apply). Applicants prove that they have fully synced a node, by a [check the team makes on the running node](https://docs.iceroot.com/network/validators/index.md#sync-proof), and accepted applicants receive testnet tokens for registration and a validator role. The team selects validators 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.

The [validator portal](https://validators.iceroot.com/) records your proposal; publishing it does not apply for or reserve a seat.

[Sign in with your wallet](https://docs.iceroot.com/wallets/sign-messages/index.md), then open **My validator**. Your signing identity owns the profile and its drafts.

A new signed identity begins as an unpublished Candidate. Signing proves account control; network registration is verified separately.

## Write the proposal

1. Add a name and short tagline.
2. Add your location or website, if useful.
3. Write the proposal in Markdown.

A simple structure works well:

```markdown
## About us
Who runs the validator and how to reach us.


## Operations
How we maintain the service and communicate changes.


## Contributions
The work we commit to, with links to results.


## Reward policy
Any sharing policy, schedule, and conditions.
```

Use the dedicated reward fields for a sharing percentage, payout schedule, and minimum payout. Leave a field empty when it does not apply. Policies are presented as your own statements.

Portal fields do not register an on-chain declaration. In the draft, a validator declares a share, a one-day or seven-day payout interval, and a payout address with `SHARE_DECLARE`, which pays a 25 ROOT surcharge on every declaration. The on-chain declaration has no minimum-payout field, and nothing enforces payment. See [Proposed validator rules](https://docs.iceroot.com/network/validators/index.md#proposed-validator-rules).

## Preview and publish

Use **Preview** to check formatting, then choose the action you need:

| Action          | Result                                    |
| --------------- | ----------------------------------------- |
| Save draft      | Keep an unpublished profile private       |
| Publish profile | Make the profile visible in the directory |
| Save changes    | Update an already published profile       |

Review edits to a published profile before saving: they update public content.

Keep dated progress in [contributions](https://docs.iceroot.com/validators/contributions/index.md), so the proposal remains easy to scan.
