Topic: [ANN] Sia - Decentralized Storage - page 380. (Read 1382227 times)

I love this new wallet and it looks pretty cool too  neat little logo

Slowly rebuilding my file contracts on 4.4. So far so good..

It's partially our fault for not having the process be more intuitive. We're trying to improve the UX more with each release. Thanks for putting up with everything!

In my situation, the lack of the wallet.json file looks to be completely my fault.

1.) During initial setup I put Sia inside a subfolder with my other cryptos.
2.) After Realizing that I could only host files from the location of the Sia folder, I moved Sia to its own drive.
3.) Not thinking about the two different crypto locations I now have, I was looking for my wallet in the folder location listed in step 1, not the   folder in location 2.


So, sorry about that, my bad.

I closed down the UI 0.4.4, and checked my task manager, siad was still running and I'm guessing it was left over from when I tried 0.4.3.  So, I killed siad using the task manager (terminate).  Now siad will not load, it just gives me a database inconsistency error, this happens when I run the UI, or siad directly.

Is there a siad command I can manually use to fix this inconsistency?  I assume consensus.db is the block chain database and if I delete than siad will then download the chain again, hopefully fixing the problem, correct?

Forgive me if these issues have already been addressed, this is my first week with Sia.

Thank You

*edit

./siac -stop appears to be a nicer way of shutting down siad.  Apparently siad does not like being "Terminated"  The U.I. doe not appear to be sending the -stop command to siad once it is shut down, but I can see how this can be a positive feature.  A button on the UI for complete shutdown or just a UI shutdown might help clear things up.

Good-Luck

Hello,
The nvidia cuda miner (https://github.com/KlausT/Sia-CUDA-Miner/) is not compatible with 0.4.3 (the miner can't connect properly to the wallet, it may use a deprecated method to get job), I don't know how to join KlausT, do someone from your team could contact him about this or fix it please ?
Thank you for your hard work.
Regards.

super nice to see this project achieve a big process!

How did you do the upgrade?

What you want to do is take all of the old folders + files and copy them into the new app/Sia/ folder in the UI. After a few minutes it should get unstuck from height 18237.

----

I think what's happening with the wallet.json file is that when you close the 0.4.3 UI, the old 'siad' is not actually getting shut down. When you start the 0.4.4 UI, it's probably still looking at the 0.4.3 'siad', which means that it's using a different wallet file.

We need a better upgrade process.

After shutting down Sia, rebooting, and re-starting 0.4.3 UI a Wallet.json file did appear.  My storage contracts are not showing up and the Block Height indicator started from 0 and stalled on 18237.

I shut down UI 0.4.3 and just started UI 0.4.4 (bother versions are in separate folders).  0.4.4 started up fine but the block height is stuck on 18237, its been stuck there for a couple hours now.  I will leave it over night and see what happens.

Any suggestions?

Linux System - Kubuntu 14.04
Sia 0.4.3

I was just looking into backing up my  Wallet.json file and I just noticed the same thing as posted above.  There is no Wallet.json file.  I have roughly 277 contracts, with ~4.77GB worth of hosting.  I am able to unlock my "wallet" with my 29 words but I do not have a wallet.json file.  I have created addresses and on a Sia restart, those addresses are no longer listed.  This is probably why my test withdrawal from Poloniex failed.

What specifically do I have to do to update to 0.4.4.  I would like to keep my hosting contracts and the block chain all intact for the upgrade.  I am using the U.I. version by the way

I am applying System updates and rebooting, maybe I will get a Wallet.json.  I have also done a system search and that file is no place on my computer.

Thank You

The Sia client on localhost is always online (I guess that otherwise it won't be able to fetch the server error ). It is the default configuration, no changes.

Congrats on the 0.4.4 release, looks fantastic!
As for the wallet.json file issue, I thought it might be resolved with the new release but the problem persists on my mac os x. The Sia app is not in a synchronized folder. really strange...

Happens automatically after 6-8 weeks.

=================

Sia 0.4.4 has been released!

https://github.com/NebulousLabs/Sia-UI/releases/tag/v0.4.4-beta

This release features a reskinned UI, an 'upload folder' button, and some significant improvements to the uploading algorithm. As with previous releases, we have also made a serious of bugfixes and minor usability improvements.

There's also a new miner, v1.0.3, that needs to be used with the new sia version. 0.4.4 should have a much lower stale rate than previous versions.

Please don't forget to upgrade from v0.3.3.3, the hardfork is just a few days away.

When does the amount "to be earned" that is now showing, become "earned"  What trips the switch to get paid... been a bit confused on this.. 

Can anyone else report similar problems? I'm not sure why the wallet.json file is being deleted. Do you have Sia in a synchronized folder? Is it possible that some background service is synchronizing the Sia folder to a previous state, which is wiping out the wallet.json (as well as some of the other folders)? As far as I'm aware, there is no code in Sia that would delete a wallet file.


We've spent quite a bit more than that on documentation, I don't think you give us enough credit. Do you have a specific question in this case?

If you have better ideas on how to handle port forwarding, you should let us know or do the implementations yourself. Port management is an incredibly difficult thing for developers, and beyond upnp there are very few applications (not even Bitcoin or more bit-torrent clients) that are able to do that for users. Most applications are okay if you don't forward your ports. Sia is okay too, unless you want to be a host. Being a host requires having forwarded ports and there's not much we can do about that besides what we've already done. Upnp is supported by Sia, which handles a lot of the users, but not all of them.

You should check out this blog post: http://blog.siacoin.com/2015/07/25/why-ipv4-inhibits-decentralization/

Sia supports


Do you feel that we are not targeting that community? Sia is a financial system, it's absolutely imperative that all the money details work well, that people aren't losing coins, that hackers can't steal files, that there's no way to cheat the system. The foundation is going to be under a lot of pressure, because exploiting a weak foundation in a financial system can be very profitable.

Also, giveaways tend not to work as well in byzantine systems.


 

We will continue working  


Long term, we want hosts to be above 95% uptime. That's a rough number, I'm not exactly sure what's going to be statistically the best. Higher is always better, but for our purposes 99% is almost indistinguishable from 99.99999% - the erasure coding and redundancy will bring a set of 99% uptime hosts very far, and allows hosts to focus on being cheap as opposed to being reliable. But something between 95% and 99.9% is probably going to end up being optimal for most people. For the record, 95% uptime means that you can be off for about an hour per day. Over the course of a month, you can spend an hour rebooting a few times and then still be able to survive an accidental prolonged outage (say you lose power or something) that lasts nearly a day.



  oh no!

Is your client configured differently than the defaults? The defaults should have been enough to protect you from that error. Also, stupid question, but was the internet working when you tried to fetch the file? If you try again, does it still fail? What version are you using?

File download error: 500 internal server error, insufficient hosts to recover. Should I change the configuration of my client?

Good question on the shutdown? I just checked and I have 62 contracts with .78 GB used. Earnings to earn 56.62 Sia woot! lol

And I only have had Sia hosting for a day and a half now...interesting 

It's good to see that there are still people in this thread helping to answer questions. That gives me hope for this coin in the future.

I've been watching the price on Polo since it was at 11 satoshis a little over a week ago. I finally decided to invest when I saw the price go from 14 satoshis to 19 in one day. It corrected back to 15 but I was able to get in before it went back up to 18 where it presently stands.

I just did a test withdraw from Poloniex into my own wallet.  I have hosting contracts working and the wallet seems to be working fine.  I made one new address and had Polo send my coins to that address.  However I end up with a Completed:Error status on my Polo Transaction list.  They are trying to fix it now.

Any ideas on why the transaction might not have worked, or anything I can do to verify the wallet can receive coins properly?


Also, how long can I shut down my wallet and not get penalized on my hosting contracts?  I'm assuming a quick restart will not hurt anything.


Thank You

Thanks!
I didn't notice and expect this at this stage.
Great!

Upnp support is already included and you can host on a dynamic ip if you use a service similar to dyndns or no-ip.org by announcing with