Skip to main content

Staking

Chromia relies on staking to secure clusters, compensate providers, and let token holders participate without running infrastructure. Providers lock CHR directly on the network, while users can delegate native, ERC-20, or BEP-20 CHR through the staking portal to share in rewards.

Provider staking at a glance​

  • Stake requirements — System providers must maintain 600,000 CHR per node (with at least 60,000 CHR self-staked), while node providers must hold 300,000 CHR per node (30,000 CHR self-staked). Delegations can cover the remainder.
  • Self vs. delegated stake — Self-stake always lives on Chromia Mainnet and signals the operator's commitment. Delegated stake can arrive as native, ERC-20, or BEP-20 CHR and helps providers satisfy the total requirement.
  • Operational keys — Providers manage a provider key pair for voting/signing proposals plus individual node key pairs for block production and identification.
  • Rewards and tooling — Rewards come from hosting fees paid by dapps and depend on compute supplied, uptime, role, and total stake. Providers configure staking accounts and reward shares via PMC CLI commands such as pmc economy set-provider-staking-account and pmc economy update-provider-staking-reward-share.

Read more

User delegation flow​

  1. Visit https://staking.chromia.com/ and connect a wallet that holds native, ERC-20, or BEP-20 CHR.
  2. Evaluate providers by uptime, commission, reputation, and total stake, then delegate the desired amount.
  3. Rewards accrue daily: the base APR is 3% in governance rewards, with additional provider-specific distributions.
  4. When unstaking, initiate an undelegation and wait through the 14-day (336-hour) unbonding period—tokens are locked and stop earning during that window.

Read more

Why staking matters​

  • For users — Earn passive income, back reputable providers, and contribute to Chromia's decentralization without operating hardware.
  • For the network — Delegations help providers meet stake targets, increase the cost of attacks, and ensure clusters remain performant enough to host new dapps.

For detailed procedures, troubleshooting, and governance updates, continue to the Staking section in Fundamentals.