Steps if Blox recovery tool doesnt work
Blox is completely non-custodial and for that reason we do not have access to your files or personal details. The entire installation process is completed entirely on the user side. Although a very secure approach, this makes troubleshooting slightly more complicated.
In some edge-cases, the recovery process might not work the first try around. It’s rare but it can happen. Here’s what you do in case it happens to you.
Reach out to us on Discord
- Make sure that you’re talking to one of the [Bloxstaking.com] admins for further instructions.
- In case you are not answered right away, you can take further steps to try and resolve the issue on your own.
Check your Validator status on Beaconcha.in or Beaconscan.com
- By pasting your public validator key into one of the above explorers, you’ll be able to see all the past / present issues.
- It’s very important to check whether the missed duties are a result of a few missed events in a row, or if they are sporadic.
- In any case, keep us updated on your findings.
Have your logs ready
- We’ve added a built-in function to help you access your logs. Click on your avatar located on the upper right corner of Blox Live and follow the steps to retrieve them.
- In case you are unable to access Blox Live, you can access your logs directly through your local device using this guide.
Create new AWS keys*
- In case your recovery or update processes are halted during the AWS setup / configuration stage, you can try to create a new AWS key pair.
Access your Config Files and have them ready for us to assist you further.
Delete Blox Live and install the latest version.
Run the recovery process once again.
Contact us again with your logs and findings.
Removing testnet validators from my Blox Staking Dashboard.
How to import validators into Blox Staking.
In order to troubleshoot some issues, send Blox your error and debug logs.
Follow these steps if the recovery tool doesn’t work the first time.