Crust Network Staking: How GPoS Works and What to Check Before Staking CRU

Quick decision guide: what to check before staking CRU

Before you stake CRU, you need to decide whether you want to run a validator, become a guarantor, or simply delegate to an existing validator. Each role has different requirements and risk profiles. Use this checklist to evaluate your options:

If you are building an application that needs to read staking data or submit staking transactions, you will need a reliable Crust RPC endpoint. OnFinality offers Crust RPC services that can support your staking workflow.

What is Crust Network staking?

Crust Network is a Substrate-based layer-1 blockchain that provides decentralized storage over IPFS. Its consensus mechanism, GPoS (Guaranteed Proof of Stake), is a proof-of-stake algorithm that defines staking power based on storage resources. In GPoS, validators and candidates are elected based on their effective stake, which is a combination of their own staked CRU and the CRU staked by guarantors. This design aligns economic incentives with the network's storage capacity.

Staking on Crust involves locking CRU tokens to support the network's security and, in return, earning rewards. There are two main roles:

• Validators: Run nodes that produce blocks and validate transactions. They need to provide storage resources and stake CRU. Validators earn authoring rewards (for block production) and staking rewards.
• Guarantors: Stake CRU to back a specific validator. They do not run nodes but share in the validator's staking rewards (minus commission). Guarantors are essential for increasing a validator's effective stake and helping them get elected.

How GPoS works: staking power tied to storage

GPoS is designed to bind staking quotas to storage resources. The network uses two layers:

1. MPoW (Meaningful Proof of Work): Storage nodes report their storage workload, which is verified using TEE (Trusted Execution Environment). This provides a verifiable measure of how much storage a node contributes.
2. GPoS: Based on the workload report, each node gets a staking quota. The quota determines how much CRU can be staked to that node and its influence in the consensus process.

In practice, this means that a validator's effective stake is not just the CRU they own but also the CRU that guarantors delegate to them. The more storage a node provides, the higher its staking quota, and the more CRU it can attract. This creates a market where validators compete for guarantors' CRU by offering competitive commissions and reliable performance.

Staking rewards and slashing: what to expect

Validators earn two types of rewards:

• Authoring rewards: Earned by validators who produce blocks. The amount depends on the number of blocks produced and the validator's points.
• Staking rewards: Earned by validators and candidates based on their effective stake. Guarantors receive a share of these rewards proportional to their stake, minus the validator's commission.

Rewards are distributed each era (approximately 6 hours on Crust mainnet). The total reward pool decreases over time according to the economic whitepaper.

Slashing is a risk in any PoS network. If a validator misbehaves (e.g., goes offline or acts maliciously), a portion of the staked CRU may be slashed. Guarantors should be aware that they share this risk with the validator they back. Always research a validator's track record before staking.

How to stake CRU: step-by-step

Staking on Crust can be done through the official Crust Apps UI or via the Substrate API. Here is a general workflow:

1. Get CRU tokens: You need CRU to stake. You can obtain it from exchanges or through other means.
2. Choose a validator: Evaluate validators based on commission, era points, and total stake. You can use the Crust Apps UI to browse validators.
3. Bond your CRU: Use the staking pallet to bond your CRU. This locks your tokens for staking.
4. Nominate or guarantee: If you are a guarantor, you need to select a validator to back. This is done by nominating a validator (in Substrate terms) or using the guarantee mechanism.
5. Monitor your rewards: Check your rewards regularly and adjust your strategy if needed.

For developers who want to automate staking operations, you can use the Substrate RPC API. Here is an example of how to query staking information using a Crust RPC endpoint:

curl -H "Content-Type: application/json" -d '{"id":1,"jsonrpc":"2.0","method":"state_getStorage","params":["0x..."]}' https://crust-rpc.onfinality.io

Replace the storage key with the appropriate key for the staking module. You can find the storage keys in the Crust chain metadata.

Monitoring your stake with RPC

To keep track of your staking rewards and validator performance, you can query the chain via RPC. Common RPC methods include:

• state_getStorage to read staking storage items
• chain_getBlock to inspect recent blocks
• system_health to check node health

For example, to get the current era and staking info, you might use:

curl -H "Content-Type: application/json" -d '{"id":1,"jsonrpc":"2.0","method":"state_getStorage","params":["0x..."]}' https://crust-rpc.onfinality.io

Using a reliable RPC provider like OnFinality ensures that your monitoring scripts have consistent access to the network. OnFinality provides Crust RPC endpoints that you can use for both mainnet and testnet.

Common pitfalls and troubleshooting

• Staking upper limit: Each validator has a staking upper limit (1000 CRU). If a validator reaches this limit, additional stake may not earn rewards. Check the validator's current stake before bonding.
• Unbonding period: When you unbond your CRU, there is a waiting period before you can withdraw. Plan accordingly.
• RPC endpoint reliability: Public RPC endpoints can be rate-limited or unavailable. For production applications, consider using a dedicated RPC service to avoid interruptions.
• Validator offline: If your validator goes offline, you may miss rewards. Monitor your validator's era points and consider switching if performance drops.

Key Takeaways

• Crust Network uses GPoS, a proof-of-stake mechanism that ties staking power to storage resources.
• Staking involves validators and guarantors; guarantors stake CRU to back validators and share rewards.
• Before staking, evaluate validator reputation, commission, and staking limits.
• Use a reliable RPC provider to monitor your stake and submit transactions.
• OnFinality offers Crust RPC services that can support your staking workflow.

Frequently Asked Questions

What is the minimum amount to stake on Crust?

The minimum stake can vary. Check the Crust Wiki or the staking UI for current requirements. Typically, you need enough CRU to cover the existential deposit and any minimum stake thresholds.

Can I stake CRU from an exchange?

Most exchanges do not support Crust staking directly. You will need to withdraw CRU to a wallet that supports staking, such as the Crust Wallet or a Substrate-based wallet.

What is the unbonding period on Crust?

The unbonding period is typically 7 days on Crust mainnet, but it can change. Check the network parameters for the exact duration.

How do I choose a good validator?

Look for validators with low commission, high era points, and a good track record. You can also check their total stake and whether they are close to the staking upper limit.

Can I use OnFinality's RPC for Crust staking?

Yes, OnFinality provides Crust RPC endpoints that you can use to interact with the Crust network, including staking operations. For production use, consider a dedicated node for higher reliability.

For more information about RPC providers and how to choose one, see our guide on choosing an RPC provider. You can also explore all supported networks and RPC pricing.