Is anyone has the same problem with me?

I withdrew 295400 Siacoin, but status is unconfirmed forever.
I've been waiting for 5 hours.
I already synchronized full node successful.
I used the latest version of Sia wallet.

TL;DR

• Successful v1.0.3 release - very stable.
• v1.0.4-LTS announced
• v1.1.0 wallet upgrades, including instant wallet unlock, slated for mid-December 2016
• v1.2.0 host upgrades, including pricing support, slated for early January 2017
• v1.3.0 renter upgrades, including speed and scalability boosts, slated for late January 2017
• File sharing added back to the medium-term roadmap, estimated March - June 2017.
• Sia now has an active social media + messaging team
• The infographic bounty remains live
• Sia is now actively doing joint-events with other communities in the blockchain and data storage space

Core Development

The previous month saw the release of v1.0.3, the most stable and usable release we've had to date, by a long shot. Despite this, a few bugs were discovered after release by our users. Within the next week or so we'll be releasing another version, v1.0.4 with minor fixes to some small-and-rare problems that occur in v1.0.3.

Our primary focus however has shifted from testing + bugfixing to feature development. We're entering a 3-6 month cycle of upgrades, including instant wallet unlocking, host performance improvements, Sybil attack resistance, and renter performance improvements.

LTS Releases

We're dividing our releases into two major categories. There's the standard line of releases, and then there's the LTS line of releases. The standard line of releases will match what we've already been doing, frequent versions with new features, bug fixes, and security upgrades all rolled together. The LTS line of releases will not have any of the new features, but will have as many of the bugfixes and security patches as possible. This can be attractive for stability, as new features can introduce new bugs, and frequent upgrades can cause frequent headaches.

v1.0.4 is going to be our first LTS release, and we promise to support it until the next LTS release is available. This means that sometimes we could end up releasing a v1.0.5 and a v1.1.0 at the same time, if we discovered bugs in v1.0.4 that we felt needed to be addressed. v1.0.5 would have the most important bugfixes, but none of the new features.

Wallet Upgrades

v1.1.0 is slated to have major wallet upgrades, and is targeted for mid-December. We've got a github project open explaining everything that we are hoping to achieve, you can check it out here: https://github.com/NebulousLabs/Sia/projects/1

The most significant change is that the wallet will now unlock in under a second. This can be compared to the multi-minute unlock times of the current wallet.

Today, when you load a seed into the wallet, it does not always find all of your money. Many users have run into this problem, and while we've been able to resolve the issues for everyone, it really should find all of your money on the first try. The new wallet does exactly that - it's more thorough and complete when it scans the blockchain, meaning that it's not going to miss money anymore.

Today, when you load a seed or a key into the wallet, you have to restart Sia and then re-unlock your wallet for it to be able to find the new money. This is also no longer the case. Loading seeds + keys will take some time, as a blockchain rescan has to be performed, however you do not need to restart Sia.

Currently if you want to back up your whole wallet, you have to open up a file browser and navigate to the wallet folder. The new wallet will have a simple 'create encrypted backup' process/button that allows you to do it without needing to know where Sia puts the actual data. This will be accompanied by a 'restore encrypted backup' process/button that will allow you to restore your wallet using a backup.

You will no longer need to create a new wallet to load a seed you've previously used. You'll be able to create the new wallet using the seed, meaning you don't have to add another seed to the list of seeds you are keeping.

You will also be able to 'sweep' keys and seeds, meaning that it's much easier to consolidate all of your funds into a single seed. You will also be able to sweep keys and seeds individually, meaning you can clean out one set of seeds (perhaps your hot wallet) without cleaning up your other set (perhaps the cold wallet).

There are few other upgrades to the wallet coming as well. @nemo is the primary developer on this project.

Host Upgrades

v1.2.0 is slated to have major host upgrades, and is targeted for early-January, just 2-3 weeks after v1.1.0. We're able to have a tight turnaround on the releases because we will be working on the host upgrades and wallet upgrades in parallel. Wallet upgrades are slated to be released first, followed by the host upgrades.

The host right now can realistically only handle a few hundred GBs of data. After that, performance starts to degrade and the host begins to put a heavy burden on your filesystem. It's actually dangerous for renters to store more than a few hundred GBs on a single host, because file contract renew operations will begin taking longer than the timeout allows, putting the renter at high risk of losing files when a renew happens. Additionally, you currently need to run the host as admin on Windows if you want to be able to add storage folders, which is a bit of a silly requirement. Furthermore, the fundamental design of the host means that small amounts of data occasionally get lost, and small amounts of data occasionally get added accidentally, in a way that can never be removed. Hosts running for years under the current code would eventually fill up with 'useless' data, noticably hurting overall profitability.

The new host has been designed from the ground up with performance and stability in mind. It's already about 50% complete, and it's fast, and it scales. You aren't likely to notice unless you're storing hundreds of GBs of data, but where the current host seems to top out below 1 TB, the new host can in theory support well above 100 TiB per machine. We have limited testing in place already to simulate loads that high, and so far it's held up just fine.

In addition to speed and scale, the new host features a more robust ACID architecture, meaning it's much less likely that data gets lost or gets stuck.

The host is also (finally) going to have tools that allow you to inspect the contracts that you have, so you can see how big each are, how much money is coming in, how close they are to finalizing on the blockchain, etc.

We're also hoping to release tools that will help hosts set the price more intelligently. We recognize that it's currently a process of stubmling around in the dark until you find money, and these tools will provide stronger feedback about how the host is doing and what steps can be taken to boost visibility + revenue. This is doubly important now because renters no longer only look at the storage price of the host. They also look at uptime, version (more recent versions are favored), download price, and a few other metrics that affect your host.

Shortly following the v1.2.0 release will be guide explaining how to use the new host most effectively.

Renter Upgrades

The next round of renter upgrades is slated for late January 2017, shortly following the host upgrades. Changes to the host will allow us to make significant improvements to the renter, including substantial speed and scale upgrades. The major focus is going to be on getting the speed to a point where it can properly saturate your home connection for both uploads and downloads. A secondary focus will be on boosting the total file size supported by the renter. Currently the renter will start to struggle beyond about 100 GB, and we're hoping to jump the new renter to be able to support about 10 TB of data. Early designs are being discussed, however the substantial work has not started. This can be contrasted with the host and wallet, where most of the heavy lifting is already complete. At this point in time, we predict that it will be safe to reduce the default redundancy in the renter from 6x to 4x, meaning uploads will be faster (less total data to upload), and storage will be cheaper (less data to store).

Currently the API only allows you to interact directly with the renter, meaning that if you want to make an app that automatically handles contracts, redundancy, etc., you have to write in golang and use our renter interfaces (which don't have any compatibility promises). The new renter will change this, providing API endpoints for working with the contractor, meaning you can pick your own hosts, decide your own contract parameters, and ultimately have a lot more freedom to customize Sia to your specific needs.

Long Term Upgrades

We have added file sharing back to the roadmap. Previously, we could not commit to supporting file sharing because we didn't know how to make the micropayments work. On Sia, all downloads cost money, and that includes downloading files that are shared with you. Typically, you can use the file contracts you have with a host to pay for the downloads, meaning you don't need to add any transactions to the blockchain or impact scalability in any way. You can (and do!) make thousands of tiny payments to your hosts for the data you download, and this is perfectly scalable. With file sharing however, you often don't have file contracts with the hosts storing the file. This is a problem, because it means you don't have an easy way to do micropayments to them. Either you pay an absurd amount in transaction fees + bloat the blockchain, or... ???... basically it was an unsolved problem.

We've since solved the problem. We will be able to set up a lightning-network style set of payment channels between the hosts. When you download a file from an unknown host, you can pay your host, then your host will pay the unknown host, and you can download the files without using micropayments, and without bloating the blockchain. We figured out a few tricks we can apply to Sia that makes this a much simpler problem to solve than building out an entire Bitcoin-style lightning network, meaning it should only take us a few weeks to get a prototype working (and then another few weeks to get it to production-grade).

We still need to finish the renter and host upgrades before we can start offering file sharing, so file sharing remains a ways off, but it no longer has unsolved problems preventing us from committing to it.

Community

Community Networking

For the past year or more, Sia has kept most everything internal, posting primarily to the Sia forum and hanging out primarily in the Sia slack. This is a good strategy when you are new and vulnerable, however Sia is now a more mature project, especially for the blockchain ecosystem. We're starting initiatives to get Sia integrated with other communities in the blockchain ecosystem, especially communities that already have membership overlap or otherwise share ideals with Sia.

We kicked this off with an AMA in the Cryptocopia slack, and are following up with participation in the BEN Gauntlet. We hope to continue this trend by participating in more events with other communities, and helping to add to the global decentralization movement that's been gaining traction over the past few years. If you have ideas, please don't hesitate to reach out.

Social Media

You may have noticed that we've revitalized some of our social media efforts. Our Twitter account is more active, the forum is more active, and our subreddit is more active. This is because we now have small team actively managing our social media and messaging.

Infographic Bounty

The infographic bounty is still live. We've thus far only had a few submissions, however we are still accepting submissions on a rolling basis and will be paying out bounties to all quality submissions.

Hi.

I just downloaded the SIA-UI v.1.0.2. When I try to create a wallet its not showing any Seed: and Password:. Any idea whats wrong?

I'm trying to load an old wallet I have. On Linux I'm using command:
wallet load 033x /home/computername/wallet.dat
And getting an error:
"Wallet password: stty: standard input: Inappropriate ioctl for device"
This is using the newest version of Sia-UI(v1.0.2) and siac(v1.0.1)

I decided to switch to Windows and try it from there, blockchain is still only at 55,500 while current block height is 70,000 ish

I tried loading it from there using: wallet load 033x C:\Projects\Sia\wallet\wallet.dat
And am getting error:
Wallet password:
Reading password failed: The handle is invalid.

Only 033x should not have a password attached to it, right?

Thank you in advance!

@droghio said in How to restore a wallet with seed words?:

I am having a hard time understanding what you are trying to do. What wallet load seed does is load all funds from an old wallet into your current wallet, but it doesn't change your current wallet's password. (You still need to keep both seeds too, ie keep a copy of the old seed, and the current one.)

Well, shame on me then, I thought it would allow me to use my old wallet again. Seems I've lost my coins then, as I don't have seed for the new wallet saved (RAMdisk). Good thing that was only 1,1$ worth of coins, IMO worth what I learned about SIA wallets.

Thanks for clarifying.

Hi, I have done exactly that, started "wallet load seed" command, entered current (empty) wallet seed, then I entered seed of the wallet I wish to restore. After that I got "Added Key" message. However when I try to unlock the wallet with my original seed I get an immidiate "error when calling /wallet/unlock: provided encryption key is incorrect" response. The new wallet's seed still works. That still happens after restarting Sia-Ui.

When I try to do "wallet load seed" command again, I get "error when calling /wallet/seed: seed is already known" response.

I've also tried removing Sia-Ui folder from Appdata, but it didn't help.

I've got a problem here, what do you guys suggest me to do?

Sia CLI v1.0.1: https://github.com/NebulousLabs/Sia/releases/tag/v1.0.1
Sia GUI v1.0.2: https://github.com/NebulousLabs/Sia-UI/releases/tag/v1.0.2

Today we have released Sia v1.0.1. It includes a large number of small bugfixes, and not very many overall changes. In total we have made about 120 commits to the Sia repository, and about 120 commits to the Sia-UI repository, each with a set of changes primarily aimed at making Sia run smoother.

There are security updates in this release in addition to bugfixes - some of the bugs were relevant to security, so it is recommended that everyone, especially hosts, update quickly.

Below I've made a brief list of highlights for the Sia repository, loosely sorted by importance:

• A large number of tests have been either introduced or improved, revealing bugs that are now fixed
• Host will no longer silently disable itself in the even of communication errors with the renter.
• siad now requires you to use basic authentication if you are exposing your control API (e.g. access to the wallet) over the internet
• siad now explicitly requires you to --disable-api-security before allowing you to expose your control API over the internet
• The renter and host occasionally desynchronize, this is inevitable due to the nature of networks - they are inherently unstable. The renter and host have a way to resynchronize, but there was a bug where the renter would save the wrong file hashes when trying to resynchronize, making it impossible to upload more files to the host. This has been fixed.
• A significant deadlock has been removed from the host. Though rare, it was seen multiple times that a host would freeze up, preventing it from communicating to renters, and even preventing the wallet from getting new blocks. This is now fixed.
• The host had a race condition where it would invalidate the file contracts of renters. Data could no longer be uploaded or downloaded, a significant issue. Great care was taken to improve threading safety in the host, especially with regards to file contracts. These problems have been fixed.
• the renter's database of hosts has had multiple bugfixes, including fixes for bugs that would make a host appear offline even if it was not
• the renter will now choose hosts based on collateral, upload price, download price, and storage price, instead of just using storage price. This eliminates security vulnerabilities where hosts could have a low storage price, but extremely high prices for everything else.
• When adding storage folders to the host, you must use an absolute path now. Previously relative paths had been allowed, and this had caused confusion for some users.
• Logging has been improved slightly, though a more substantial overhaul of the logging is on the way.
• Addresses are now required to have a checksum - this means all addresses are now 76 characters. Previously 64 character addresses were also allowed, but these were subject to typos that occasionally caused people to send their coins to the wrong address (making them unrecoverable)
• some typos have been fixed

Overall, there is still more work to do. We have fixed a lot of significant issues in this release, including security issues, and want to push it out to the community. Though things are running more smoothly than before, the renter and host still have troubles communicating occasionally. Throughout the next few weeks we will continue to dedicate ourselves to logging, testing, and improving the rough patches and slowdowns that still exist within the codebase. I will be focusing primarily on the renter, mostly around safety and speed. The host still has a few issues as well, and these will not be neglected.

We have also begun work on the wallet, which means the future should see superior backup and recovery tools, instant wallet unlocking, and other changes which will make your lives easier and safer with regards to the wallet. @nemo will be leading the changes in the wallet.

@johnathanhowell will be providing a more detailed update of changes to the UI. In this next cycle, he will continue to maintain the UI and fix bugs that come up, but his primary focus has been turned to the explorer. The explorer is going to be getting upgrades, including plugins to metrics like the number of github followers and stars we have, the number of nodes on the network, and some host-tracking features similar (but not identical) to those on siapulse.com.

@jordan is going to be spearheading business development within Sia, managing potential business partnerships, investor relationships, and many of the marketing efforts. His primary role within Sia today is to help the ecosystem grow, which includes providing better access to documentation and third party apps within the ecosystem.

@droghio and @mnsl are going to continue improving the testing within Sia, particularly as relates to the API and multi-node testing. Sometime in the next few weeks we should see a full testnet for Sia, something we should have released a long time ago.

I would also like to give a shoutout to everyone who has helped us in some form or another over the past few months. We have had help from many, and I am sure to miss more than a few of you, but below is a mashup of users that have either contributed bug reports, contributed graphics, written code, helped newbies, or somehow otherwise gone above the standard role of 'user' and took time out of their life to help improve Sia as a whole:

@david60, @aspect, @allejuppa, @betaboot, @icebear, @tobo, @in-cred-u-lous, @fornax, @ffmad, @wolf0, @mvolkov, @snappaz, @mtlynch, @redrockmining, @TacoByte, @Chehands, @Krakonos, @Mortal-Killer, @axu, @hosiawak, @phobosq, @wskeen, @irishsia, @veber, @johnstor, @smilesvua, and many more.

@jamiec79 To backup your wallet you just need to remember the seed. If anything happens you can re-import the wallet seed into a new wallet. You can also copy the wallet.json file and re-use that to keep the same wallet.

Glad to hear you found a work around, but this sounds like it might be a ui bug. If you have time to run a few quick tests that would be really helpful.

• What is your default OS language?
• Just to confirm the wallet unlock when you use the Terminal plugin built into the UI?
• If so could you open the Wallet plugin, hit "Cntrl+P" to open a dev window, try unlocking the wallet again, and send a screenshot of any console text you see in the dev window?

Thanks.

Actually i've discovered that if i paste the wallet unlock passphrase into the wallet unlocking screen i get the message...

error when calling /wallet/unlock: provided encryption key is incorrect

But if i use the terminal screen, and type wallet unlock and then enter my passphrase it works. It confirms wallet lock - success. When you type wallet lock it doesn't confirm anything, but if i go to main overview screen it shows locked.

So at least i've found a way to lock and unlock wallet. Hopefully when i move coins into the wallet i won't have any further problems.

Also i know this may be a newb question, to make a backup of wallet i just need the wallet file nothing else?

Thank you for your patience and support.

hi,

I've done as requested,

Version = Sia Client v1.0.0

consensus =

Synced: No
Height: 10144
Progress (estimated): 17%

I've managed to finally find the wallet key and delete it, but for some reason i had to run the following command in Mac terminal. When i did it suddenly built the file structure and wallet was one of those items.

~/Downloads/Sia-UI-darwin-x64/Sia-UI.app/Contents/Resources/app/Sia/siad

I was then able to delete the wallet key. When i reopened the SIA-UI it asked me to created a new wallet and the passphrase and seed were identified. I took a copy of them for safe keeping.

To ensure i had the right information i tried to lock/unlock the wallet. Even with the copied and pasted passphrase it kept failing saying....

error when calling /wallet/unlock: provided encryption key is incorrect

Which it shouldn't be as i've just copied and pasted the passphrase in exactly how it was shown to start with.

I've some how now managed to unlock the wallet, after it rejected the same copy and paste 4 time and on the 5th it works?? I really want to start using the wallet, but i have no confidence in the ability to lock and unlock the wallet consistently.

I can try completely deleting the whole thing again, but i'm struggling to see what else i can do but wait for the update you refer to.

Thank you

Jamie