2017/04/29 12:17:26.275305 errors.go:151: internal error: error with 188.8.131.52:42040: incoming RPCReviseContract failed: RPCRecentRevision failed: challenge failed: could not fetch 8fdc74ca91f4c26be1d459a4bb1e1c02c8dd41d0edae9fa3de7febb1c64b790d: storage obligation not found in database
2017/04/29 12:19:43.511659 errors.go:151: internal error: error with 184.108.40.206:42252: incoming RPCReviseContract failed: RPCRecentRevision failed: challenge failed: could not fetch 8fdc74ca91f4c26be1d459a4bb1e1c02c8dd41d0edae9fa3de7febb1c64b790d: storage obligation not found in database
2017/04/29 12:34:00.368061 errors.go:151: internal error: error with 220.127.116.11:42494: incoming RPCReviseContract failed: RPCRecentRevision failed: challenge failed: could not fetch 8fdc74ca91f4c26be1d459a4bb1e1c02c8dd41d0edae9fa3de7febb1c64b790d: storage obligation not found in database
@nemo thank you so much, I was finally able to restore my wallet with this.
Is there a way to set a custom password/passphrase when restoring a seed with init-seed?
Also why does Sia-UI corrupt so easily? Often it freezes and doesn't want to close and when I kill it it's as if the program damaged after that as the syncing doesn't appear in the top right corner and none of the buttons work. I have resorted to keeping a copy of all the files that I copy over if it corrupts haha.
Thanks again for the instructions, don't know what I would have done with your post.
Hey, sorry for taking three days to get to this. This is a fairly common error and unfortunately it's pretty damaging. When your machine has a hard poweroff while getting a new block, sometimes you can lose your data. In this case, your host files got corrupted :(
To fix it, you will have to go into the folders manually and delete the host. Unfortunately, this means that you will lose any contracts.
People running the current version can avoid the bug by not doing a hard-poweroff, especially Windows users are vulnerable.
A bad actor could not possibly buy up enough masternodes as the cost increases exponentially in the process
As the cost of masternodes go up, you're right this would be more difficult. And that's a good thing! We are going to have to agree to disagree on this point though. Maybe I'm just paranoid, lol.
I’m so glad I came to this forum. It’s made me realise how closed minded the devs are.
By the way, I'm not a Dev of Sia, so I hope you're not thinking I'm speaking for the team. Just my take on it.
I have to disagree with you about the developers here being closed minded. I have not had that impression at all.
I forgive you for getting that wrong, but Sia definitely aims to be decentralized in government. That's why we chose a PoW blockchain. Realistically, today, the Nebulous team has full control over Sia's future. But that's because the Sia network does not work very well yet, and any network without our ongoing development effort is going to fall apart. Once Sia is standing on its own two lets more solidly (it's getting closer every release), then the community will have a real ability to reject hardforks or protocol changes that we try to push onto the network.
Oops, my mistake! You're right, I was talking about how Sia appears now, and as you said, "today, the Nebulous team has full control over Sia's future." And I don't have a problem with that, I understand that's how things need to be while the network is being created. Good to know the goal is decentralized government.
You should use a dynamic dns, and then you should announce your host as your dns hostname.
It used to cost 15 SC. Then the coinprice went up so we reduced the announcement cost. But it seems that we forgot to update the message.
You do not need to re-announce every time you change the configuration. You need to announce so that people know you exist, but once they know you exist they will periodically ask you for updates on your configuration. No need to re-announce every time something changes.
The renter will handle monitoring hosts and repairing lost redundancy automatically. The user just needs to make sure they run Sia for a few hours every week. (and if you don't run Sia for more than 6 weeks in a row, you are at risk of losing all of your files)
No, currently if you make changes to the source file, Sia will not notice. In fact, I could see this causing problems with the current implementation. We will eventually support updating files, but currently Sia is best for static data (like movies, hard drive backups, etc.)
Worth noting that in v1.2.0, loading the transaction pool will only take a few minutes. The wallet can also take a few minutes, but as a tradeoff unlocking the wallet will be instant. (these delays only apply to who skip syncing by downloading a consensus database)