Troubleshooting the recent hardfork
Update as of December 20th, 2017
The guidance for any issues found in this article is to now update to v.1.3.1 of Sia-UI, found here: https://sia.tech/apps/
If you have persistent Sia-UI issues that are not resolved by upgrading, continue through this document to find a resolution.
Sia is very happy to announce the release of v1.3.1! This update includes improvements for the stability and performance of the renter, overhauled uploading, and a better file repair process.
It also includes a fix for the hardfork-related issues that were recently introduced. While the other updates and improvements are immediate, the fork-related fix will activate at block 139,000. Read the full release notes here:
https://github.com/NebulousLabs/Sia/releases
This update consists of incredible contributions from both the Sia core team, as well as our wonderful community. We thank you, and we hope this release serves you well.
/end update
— — — — — — — — — — — — — — — — — — — — — — — — — — — — — —
Sia recently hardforked at block 135,000 in order to update the Difficulty Adjustment Algorithm. This has caused issues for some users of Sia-UI, our official app. Many users have reported a successful upgrade, but we wanted to use this space to identify potential problems and how to correct them.
Issue: Sia-UI is not synced
Check the status of Sia-UI’s blockchain synchronization. It should say Synchronized in green text in the upper right hand corner, with a block height of around 136971 as of 12:46 PM EST on December 12th.
If you see Synchronizing in yellow, that’s fine. Let it sit until it is finished syncing. If it says No peers or Not synchronizing, Sia-UI will not sync with the network.
Resolution
Go to this page and follow the instructions there.
Issue: Sia-UI says it is synced at block 135,019, but my transactions aren’t updating
The Sia network should have a block height of around 136971 as of 12:46 PM EST on December 12th. If you see Synchronized in green text but the block height is closer to 135,000 than 137,000, use the following steps.
Resolution
Go to this page and follow the instructions there.
Issue: Sia-UI won’t load after upgrading to v1.3
You may see the message ‘Loading can take a while after upgrading to a new version. Check the release notes for more details’. Or it may simply say ‘Loading’.
Resolution
As long as Sia-UI says it is loading, wait. The process normally takes less then 20 minutes, but can sometimes take up to an hour. It should load into Sia-UI when it is finished.
Be careful not to improperly disrupt Sia-UI while this is happening. On Windows, do not terminate Sia-UI’s processes in the Task Manager or restart the computer without properly exiting Sia-UI first. Click close on the system tray icon for Sia-UI.
On Mac, click on Sia-UI in the upper left hand corner and choose Quit Sia-UI.
On Linux, simply close the Sia-UI window.
If you see the error: Invalid argument
invalid argument is an issue caused by unclean shutdowns on Windows. We have not yet seen reports of this happening on Mac or Linux.
First, delete the consensus.db file. It is located in:
- Windows:
Users\<user>\appdata\roaming\Sia-UI\sia\consensus\consensus.db - OS X:
$HOME/Library/Application Support/Sia-UI/sia/consensus/consensus.db - Linux:
$HOME/.config/Sia-UI/sia/consensus/consensus.db
If this doesn’t resolve, delete the transactionpool.db file as well:
- Windows:
Users\<user>\appdata\roaming\Sia-UI\sia\transactionpool\transactionpool.db - OS X:
$HOME/Library/Application Support/Sia-UI/sia/transactionpool/transactionpool.db - Linux:
$HOME/.config/Sia-UI/sia/transactionpool/transactionpool.db
If you see the error: hardfork incompatibility detected
Delete the consensus.db file. It is located in:
- Windows:
Users\<user>\appdata\roaming\Sia-UI\sia\consensus\consensus.db - OS X:
$HOME/Library/Application Support/Sia-UI/sia/consensus/consensus.db - Linux:
$HOME/.config/Sia-UI/sia/consensus/consensus.db
Issue: Sia-UI did not receive a transaction sent from Bittrex
Bittrex seems to be having issues with some transactions that were sent around the time of and after the Sia hardfork. Just remember that transactions only show up in a synchronized 1.3.0 wallet.
Resolution
You need to contact Bittrex, but first you should give it about 6 hours to see if the transaction comes through. If it’s still not showing, open a support ticket with Bittrex as they need to re-broadcast the transaction to the Sia blockchain.
The wrap up
I’ll update this post as necessary. When version 1.3.1 ships, the answer to all of these issues will be simple — update. We’ll keep you posted.
Steve
steve@sia.tech
@steve on Discord
