The Guide to staking CRO on the Crypto.org Chain

Download the Chain Desktop Wallet

The desktop wallet provided by Crypto.com allows you to send, receive and delegate your CRO to your chosen validators.

You may download the latest version from Windows, Mac and Linux from the official repository:

https://github.com/crypto-com/chain-desktop-wallet/releases/latest

Choose the .dng for mac and .exe for windows

Download the app and install it.

Create an app password

In order to secure your desktop wallet, the application will ask you to set a password. It will be required to send transactions and delegate your funds.

If you have forgotten it, the only solution is to reset your desktop wallet (see the FAQ below).

Choose a secure password, and do not forget it !

Did you already stake your CRO in the mobile DeFi wallet ?

Staking is available in the Mobile Defi Wallet, but you cannot yet choose your validator.

If you have already delegated your funds in the Defi Mobile wallet, you will need to restore your wallet from the Crypto.com Defi Mobile App.
This will allow you to manage your wallet both from your mobile and your desktop wallets. Therefore you will be able to redelegate your previously delegated CRO to another validator.

Otherwise, you may jump to the section explaining how to delegate CRO to setup a new wallet

Restore your wallet from the mobile Defi app

Export your 12 words recovery phrase from your Mobile Defi Wallet

Obtain your 12 words passphrase from your Mobile Defi Wallet App

Open the Crypto.com Defi Mobile App

Click the Settings Icon in the top left corner of the screen

Select Recovery Phrase and input your password

Export your 12 words from there and write them down.

Restore your wallet by using your recovery phrase

Import them into your Desktop Wallet by clicking on your wallet > Restore

Choose a good validator to delegate your CRO

Choosing the right validator is important, therefore we always advise people to do their own research.

That being said, we would be extremely thankful if you delegate your CRO to our staking.cafe validator.

Doing so supports our work to help the crypto.org community grow, by providing an independent, secure and sustainable validator for the community.

👉 Get more information on what we stand for

Delegate your CRO to your chosen validator

Go to Staking

Open the Delegate Funds tab

Select your chosen validator

Confirm the delegation, and you are done !

Change validator by re-delegating your stake

Re-delegating is different from un-delegating

Un-delegating your stake will take 28 days, during which your CRO will not generate rewards. This is also known as unbonding.

Re-delegating is immediate, and you will not lose any rewards.

In the desktop wallet go to Home > Staking, click the green “Redelegate Stake” link

Increasing your CRO stake on a validator

Increasing your stake by delegating additional funds is exactly the same as delegating for the first time.
Go to Staking > Delegate Funds, input the validator address and the additional amount that you wish to delegate

Receive and withdraw your rewards

Your rewards will start to accumulate in the application

You can see your accumulated rewards in the "Staking" menu

In order to withdraw them, simply click on "Withdraw Rewards"

Staking > Withdraw Rewards

It's important to understand that the accumulated rewards do not themselves generate additional rewards.

To do so, you need to withdraw them, and delegate them to a validator.

Therefore, it's important to withdraw and restake them once in a while.

In order to estimate your rewards ahead of time, and calculate how often you need to withdraw and restake them, you may use our handy CRO staking calculator

Undelegate / Redelegate your CRO on the Crypto.org chain

Undelegating vs Redelegating vs Increasing and your CRO stake

  • Undelegating, which is also known as unbonding, means to stop delegating your CRO stake on a specific validator, so that you can spend/send them again.
  • Redelegating, means to change validator. You reallocate your already-delegated CRO, towards another validator.
  • Increasing stake should not be mistaken with redelegating. It means delegating additional CRO to a validator that you already delegate to.

The 28 days cooldown period for undelegating

In order to increase the security of the chain, as well as encouraging long term commitment, some operations are subject to a 28 days cooldown period:

Undelegating your stake is always subject to the 28 days cooldown period.

The Crypto.org chain desktop wallet warns you of the 28 day period when you request to undelegate CRO

When you delegate CRO, they are in the bonded state and accumulate rewards.

When you send an undelegation request, your CRO will transition from the bonded state, to the undelegating state. They will stay in this state for 28 days, not earning rewards. Once this period is up, they will be available again in your wallet to spend.

You may send as many un-delegation requests as you want, and select the exact amount of CRO that you wish to undelegate for each request.

CRO redelegation rules to change validators

Re-delegating is different from un-delegating. It is extremely useful because it allows you to change validators by re-delegating your stake towards another validator.


This operation is immediate. Unlike un-delegating, you do not have to wait the 28 days, and you continue to earn stake rewards normally.

Redelegating can only be done under certain conditions

The Crypto.org Desktop wallet explains the rules for redelegating your stake

Am I allowed to re-delegate ?

You have not done any redelegation in the past 28 days - Yes.

If you have not done any redelegation in the past 28 days (regular delegations or stake increases do not count, only re-delegation requests count) then you may do a redelegation request without restriction.

You want to re-delegate from a validator to which you have re-delegated in the past 28 days - No

Transitive redelegations are always subject to a 28 day cooldown.

If you delegate CRO to a Validator A, then redelegate some CRO to Validator B, you have to wait 28 days to be able to redelegate from Validator B to any other Validator.

You have done 7 redelegations with the same Source and Destination validators over the past 28 days - No

You may re-delegate CRO (unless in the case of serial delegation, see above) without waiting, up to seven times in a 28 day period, and for a given Source and Destination validator.

What should you do if your validator has been jailed ?

What does jailing mean ?

Validators are servers who process the transactions happening on the Crypto.org chain, by signing the blocks storing those transactions. It's their duty to do so once they join the network.
Because of failing hardware or internet connection, validators may go offline. In order to keep the network running, validators who fail to sign more than 2500 blocks out of the 5000 last blocks are jailed.
This means that the validator stops signing, and therefore the funds delegated to it no longer earn staking rewards.

When a validator is jailed, it is for a duration of 24 hours. Then, the owner must unjail its validator manually for it to become online again.

What should you do if your validator becomes jailed ?

1. Confirm that your validator is jailed

Search for your validator by its name in the Official Crypto.org explorer. If your validator is jailed, then the header will read "jailed" :

This validator has been temporarily jailed for being offline for too long.

2. Wait 24 hours for the validator to resume operations

Sometimes things go bad, even for good, reputable validators. Having your validator jailed, even if it makes you lose precious rewards, is only temporary.

If you are delegating with a reliable validator, chances are good that it will become online very soon. When it does so, there is no action required on your part to resume earning your rewards.

Those are positive signals that your validator will become online soon :

  • Your validator has never been jailed before
  • Your validator uptime is > 99.9%
  • The owner of the validator has communicated an ETA on their website, Twitter or Telegram groups

In this case, it's usually better to wait it out.

3. Redelegate your funds to another validator

Some validators, however, are poorly maintained, and some are plain scams. In this case, it's better for you to redelegate to another validator. Note that re-delegation follows strict rules, and is not always possible.

To do so, you will need to choose another, better validator. The good news is that you have a wide selection of validators to choose from.

We constantly monitor validator activity and display the results in our validator leaderboard. It's a fantastic resource to identify validators who have a track record of securing the network without issues.

Alternatively, you may stake with us ! 🤗 (we' ve never been jailed !)

FAQ about the chain desktop wallet

How can I reset the desktop wallet app password?

Reinstalling the app will not reset the password, to do so, you will need to clear your account data.

⚠ Be careful, you will need to restore your wallet after the procedure. Make sure that you have previously saved the 12 words mnemonic passphrase that was generated when you first created your wallet.

If the wallet is open

If your desktop wallet application is open, all you have to do is to go to "Settings" > "Clear Storage", and click "Clear storage"

If your wallet is not open, and you are on Mac

Go to this folder :

/Users/{username}/Library/Application\ Support/chain-desktop-wallet/IndexedDB

You should see a folder ending with : .indexeddb.leveldb

Delete it and restart the app

If your wallet is not open, and you are on Windows

Go to this folder :

C:\Users\{username}\AppData\Roaming\chain-desktop-wallet\IndexedDB

You should see a folder ending with : .indexeddb.leveldb

Delete it and restart the app

You may now choose a new app password.

Kindly provided by staking.cafe ☕

A community validator on the Crypto.org Chain

logo validateur staking.cafe crypto.org

13% APY
Reward Rate

5 %
Validator Commission

99%
Block signature rate