Quote from: Hakkane on December 16, 2017, 10:33:08 PM

Quote from: Mattei on December 16, 2017, 09:26:29 PM

Quote from: Hakkane on December 16, 2017, 04:47:20 PM

Quote from: Mattei on December 16, 2017, 04:04:33 PM

1600 contract and 50000 sia coin went to fork cause the new version will not load after I upgraded from 1.2.1 to 1.3.1 Says it encounters a fatal error and then hangs with error messages. \

Check this post for solving those issues: https://blog.sia.tech/troubleshooting-the-recent-hardfork-ca77e0b17f0f

BTW, coins are never lost because of a wallet issue. This is a blockchain: coins do not live in wallets, but in the blockchain, and as long as you keep the recovery seed, you'll have access to your funds

Thanks for the link!!
I was/am mostly concerned about the contracts I have built up, and the hosting service. It it took me forever to get up to volume of hosting contracts. Any idea what the time frame is before host defaults and looses the collateral due to server MIA.

NP! Yes, you are required an uptime of 97%. Even if you have 2-3 days of downtime every 3 months, you are still good.

I am concerned that as you have not updated your client since last week when the hardfork took place, you might have lost some storage proofs, and so some contracts might be failing... Nevertheless the reputation of your host as observed by the renters should be good as even if your host was outdated and forked out, your data was available.

But try to restart your host as soon as possible: delete the consensus and sync your client again. If you are using a HDD for the installation instead of an SSD, consider bootstrapping to save time: https://siawiki.tech/daemon/bootstrapping_the_blockchain

And if you find problems not being able to sync the last blocks, try this fix: http://siastats.info/nodes.html

so deleting the consensus got the wallet out of the error mode, it has been stuck on block 82960 for the last couple of hours. I added at least 10 gateway connect addresses from the link above... nothing... think I will look into the bootstrap above. I did see references to deleting the transactionpool.db, am considering adding that step, if delete consensus and then bootstrap doesn't work out. will see.