hmm, ive escalated this issue already. could you upgrade your node? wipe all data off and reinstall and sync up? we are still trying to troubleshoot your issue, but it could be that some of your old data was not completely cleared. so i would suggest removing all data and removing the entire cloned repo and start afresh. i’ve added the new snapshot file in the gitbook so you can use that. at the time of writing, snapshot data will be from block height 1830604 while the current block height is 1831985.
PLEASE take a look at the “validator recovery section” to see how you can recover your validator after upgrading your node
yes rm -d the data directory and make sure you stop your node. i have updated the snapshot guide a more detailed explanation and also how to set up via the “DAEMON” method. You may also take a look at “Validator Recovery” to see how the directory tree structure would look like.
Additionally, I believe you will be doing quite a bit of testing on your end so could you provide me with your token holding address so i send some more test FX over to you
Hi guys, initially we encourage upcoming validators to be able to at least self stake 100,000 FX to become competitive. This will be supplanted by a much lower requirement. The new requirement will allow more flexibility for would-be community validators.
Also, to encourage community validators to get more delegation, company hosted validators will gradually (weeks) increase our commission rate to increase incentive to move to community validators.
I’m ready to do a codeless Validator, I have more then enough to be an active Node, are the Codeless nodes like what we did in testnet 1,2 & 3 going to be available to set up Matie; I don’t have the brain power to do a coded node
@ClaudioxBarros just now you asked about what the unbonding_height is the height of the last time you were unbonded. it could be due to you running the unbonding command or it could be that you were jailed/slashed
After you’ve recovered and resynced your node, because you didn’t resync within a block time, your validator will be jailed (too long down time) try using the unjail command (in the “setting up validtor” or “f(x)cored commands” section. That should do the trick. If it doesn’t, ping here again.
Did you follow the tutorial on how to recover your validator?