Category: Siacoin (SC)

Troubleshooting the recent hardfork

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 135,000 or more.

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 synch with the network.

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. Cick close on the system try 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>appdataroamingSia-UIsiaconsensusconsensus.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>appdataroamingSia-UIsiatransactionpooltransactionpool.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>appdataroamingSia-UIsiaconsensusconsensus.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

[email protected]

@steve on Discord


Troubleshooting the recent hardfork was originally published in Sia Blog on Medium, where people are continuing the conversation by highlighting and responding to this story.

<div class="infobox"><span class="appendinfo">This article was originally published on: <a href="https://blog.sia.tech/" target="_blank">The Siacoin Blog</a> on </span></div>