May 15th Fork FAQ
What’s this fork all about? Aren’t forks bad?
This fork is about changing the mining algorithm from Blake2B to Blake2B-Sia (with 1009 nonce). More details can be found here.
When is the fork happening?
While the fork has been targeted for May 15th, the specific blockheight is 238650. This may happen on the 15th but could happen slightly later.
I’m a storage provider with a basic DIY rig, do I need to care about this?
Absolutely. Similar to the January 2023 fork, DIY providers will need to update their spd binary to the 1.8 version prior to the fork. Software is already available now here.
I have a full license DIY provider, what do I need to do to update?
Guides are available for full license software providers, you should follow the 3 steps for your OS of stopping the xa-miner container, delete spd binary, start xa-miner container. Running the installer is not the way to update spd, follow the Upgrading to a new SPD Release section of the relevant guide for your OS, Windows, Linux or Synology.
OK but I’m one of the cool kids and bought a hardware Xa-Miner, I can sit back and relax right?
Correct, hardware Xa-Miners will automatically be updated between now and the fork (assuming they are online). Resume your lazy posture.
I’m running a relayer, does this fork impact me?
No, relayers don’t use the blockchain directly so there’s no update required for relayer users.
Is there anything I need to do with my WebWallet?
Yes, you will need to update your WebWallet to be able to use it post-fork. While technically it’s not so important to update before the fork, you must not try to send or receive coins to your WebWallet after the fork if you haven’t updated it. An updated version will be released in the coming days before May 15th.
So what happens if I don’t update my DIY provider before the fork? Bad things will happen?
Yes, if you are still running < 1.8 spd after the fork then your storage contract(s) will fail and you will lose any data stored currently resulting in loss of earnings for you.
Oh man, that sounds bad. Just on the off chance I’m one of those guys, what do I need to do after the fork to get sorted out?
Firstly you’ll need to update to 1.8 (or the latest version if newer versions have been released). Then you will need to delete your consensus.db file and let your provider resync to the blockchain. For basic CLI providers this file is in your metadata folder, for full license providers simply click on the Redownload button on the Support page of the UI. The WebWallet 0.3.4 and greater has a Rebuild Consensus button in the UI which will remove the consensus.db and resync to the blockchain.