Stake Issues
Common Stake Issues and Solutions​
Here are the most common Stake issues that you might encounter while using the app. Click on the issue to find the suggested solution.
Staking Transaction Failed​
Issue:
Sometimes, staking transactions may fail to process, resulting in an error message or failed transaction status.
Solution:
Ensure you have enough balance to cover transaction fees.
Verify your wallet address and staking details before confirming the transaction.
If using a third-party validator, check if they’re operational and confirm any minimum staking requirements.
Rewards Not Received​
Issue:
You’ve successfully staked your assets, but the expected rewards have not appeared in your wallet.
Solution:
Confirm the reward cycle and payment frequency specific to the blockchain you’re staking on.
Check if the staking provider has a delay in reward distribution, which can vary by network.
Make sure you haven’t accidentally un-staked your assets, as this could interrupt reward distribution.
Unable to Unstake Assets​
Issue:
You want to un-stake your assets but encounter errors or restrictions.
Solution:
Check if there’s a required lock-up period before you can un-stake.
Verify if the staking contract allows partial un-staking or if it requires you to un-stake the entire amount.
Contact support if the transaction fails despite meeting the network’s lock-up requirements.
Incorrect Staking Balance Displayed​
Issue:
The staking balance in your wallet or on the staking platform doesn’t match your expected staked amount.
Solution:
Refresh your wallet or app to see the updated balance.
Check if network confirmations are required for recent staking transactions to reflect.
If discrepancies persist, contact support with a screenshot and transaction details.
Other Issues or Need Further Assistance?​
If you’re still facing challenges after trying these solutions or your issue is not listed above, contact Gem Wallet Support with details of your issue, including error messages, transaction IDs, and any troubleshooting steps you’ve already tried.