This error can occur during various actions in the game, including but not limited to: Buying items from the shop, claiming the SPS airdrop for Hive or linking external wallet addresses.
There are three main reason for this error to show up:
- Your Hive account was not properly created.
- Your keys were changed and the website still has you old keys saved.
- A technical issue on the website is causing this problem.
Your Hive account was not properly created
You should check whether this is the cause of your problem before going through the other steps. You can easily verify if this is the reason for the above error by checking your account on one or both of these websites (insert your username instead of "yourusername"):
If the website shows an error like in the below pictures and not a history of transactions, it means there was a problem while creating your account.
In this case please open a ticket through our support system and tell us that your Hive account was not created: https://support.splinterlands.com/hc/en-us/requests/new
Your keys were changed and the website still has you old keys saved.
If you have changed your keys the website does not automatically know that and will throw this error. To solve this problem please follow the steps described in the solution for the next error reason.
Other technical issue
The error can also be caused by other local issues.
The most simple solution is to log in with your keys, however we recommend to use Hive Keychain to interact with the game, because you cannot make any errors and don't have to copy paste keys anymore. Using the correct keys or Hive Keychain will help you prevent this error from showing up.
We have a separate article explaining how to set up Hive Keychain and add your account to it: Hive Keychain Installation and Usage
(Make sure to include both the active and the posting key in Keychain)
When you have set up Hive Keychain with your account, logout from Splinterlands and login again using Hive Keychain. After that you can try to do the action that you tried to do before and it should no longer show this error.