[ANN] Sia - Decentralized Storage

[bitspill]

Is there a developer issued/approved 'fool proof' guide to upgrading the wallet to 0.5.2?

(I'm currently running 0.5.1.)

Thanks

Backup everything.
Download new version.
Drop new files over old files.

Profit.

Thanks - specifically, the renter, miner and wallet folders?

Or, given that I haven't been hosting or renting, would it be ok just to copy across the existing wallet folder to the new location?

Presumably, having copied over (at least) the old wallet folder, the new wallet will have the same password as before or will I be prompted to save a new password?

Apologies for asking basic questions and thanks for any further help.

If you have a wallet backup wallet folder
If you have uploaded anything backup your renter folder
If you have announced yourself has a host backup your host folder
If you don't want to resync from zero backup your consensus folder
The miner and gateway folders contain basic files which can/will be regenerated


If you copy over your old wallet then the password will be unchanged


Don't be afraid to ask questions, it's better safe than sorry.

[4emily]

Thanks @bitspill.

Based on your advice to date and what I've otherwise read/guessed, this should be the sequence of steps:

1. Back up old wallet folder

2. Back up old consensus folder

3. Download and install the new client

4. Open the new client and create new wallet (I'm assuming the same thing will happen on opening 0.5.2 as did for 0.5.1 – i.e. automatic generation of a new password/wallet)

5. Close the client

6. Replace the new wallet folder with the old wallet folder

7. Replace the new consensus folder with the old consensus folder

8. Open the new client again and old balance from previous wallet will appear.

Is that correct?

Thanks for your further help 

[M4z]

SIA is back guys! Now let's push it to the limit, put your saving on SIA, you'll not regret :')

[xiahui135]

decentralised storage is excellent!

can we make the storage for website? so we can sell the storage to let people establish websites on our cloud, it would be cheap and safe.

[bitspill]

Thanks @bitspill.

Based on your advice to date and what I've otherwise read/guessed, this should be the sequence of steps:

1. Back up old wallet folder

2. Back up old consensus folder

3. Download and install the new client

4. Open the new client and create new wallet (I'm assuming the same thing will happen on opening 0.5.2 as did for 0.5.1 – i.e. automatic generation of a new password/wallet)

5. Close the client

6. Replace the new wallet folder with the old wallet folder

7. Replace the new consensus folder with the old consensus folder

8. Open the new client again and old balance from previous wallet will appear.

Is that correct?

Thanks for your further help 

Yes, except you can skip step 4. since you're copying over the old wallet no need to create one just to throw it away

[fonzerrellie]

nice dip on Polo  I didn't think we'd get the chance to buy SC below 25 sats again... I'll try and find some btc to scoop some up

[mishax1]

Could someone explain why does Sia need a POW gpu mining model instead of pure storage sharing model like the others ?

[bitspill]

Could someone explain why does Sia need a POW gpu mining model instead of pure storage sharing model like the others ?

PoW provides the generation of coins for the purpose of renting storage as well as securing the advancement of the blockchain for the purpose of maintaining an accurate record of contracts and facilitating secure and verifiable payment


Which "others" and their "pure storage sharing model" are you referring to?

[xibeijan]

Tyring to sync wallet and get this error

with v0.52

./siad
Loading...
(1/7) Loading gateway...
(2/7) Loading consensus...
(3/7) Loading transaction pool...
unexpected fault address 0x30c5c040
fatal error: fault
[signal 0xb code=0x1 addr=0x30c5c040 pc=0x292e00]

goroutine 12 [running]:
runtime.throw(0x585f38, 0x5)
   /usr/local/go/src/runtime/panic.go:530 +0x79 fp=0x111ed16c sp=0x111ed160
runtime.sigpanic()
   /usr/local/go/src/runtime/sigpanic_unix.go:27 +0x27b fp=0x111ed198 sp=0x111ed16c
github.com/NebulousLabs/bolt.(*Tx).rollback(0x110ed700)
   /home/luke/go/src/github.com/NebulousLabs/bolt/tx.go:245 +0x60 fp=0x111ed1b8 sp=0x111ed198
github.com/NebulousLabs/bolt.(*Tx).Commit(0x110ed700, 0x0, 0x0)
   /home/luke/go/src/github.com/NebulousLabs/bolt/tx.go:163 +0x1ec fp=0x111ed274 sp=0x111ed1b8
github.com/NebulousLabs/bolt.(*DB).Update(0x10b837a0, 0x111ed2cc, 0x0, 0x0)
   /home/luke/go/src/github.com/NebulousLabs/bolt/db.go:580 +0xee fp=0x111ed2a0 sp=0x111ed274
github.com/NebulousLabs/Sia/modules/consensus.(*ConsensusSet).addBlockToTree(0x10b79080, 0x0, 0x9b640000, 0x787a362e, 0xb5d8458d, 0xb4bb180e, 0x727ff446, 0x21456bf3, 0xf6d20d7d, 0x144b571f, ...)
   /home/luke/go/src/github.com/NebulousLabs/Sia/modules/consensus/accept.go:183 +0xd8 fp=0x111ed328 sp=0x111ed2a0
github.com/NebulousLabs/Sia/modules/consensus.(*ConsensusSet).managedAcceptBlock(0x10b79080, 0x0, 0x9b640000, 0x787a362e, 0xb5d8458d, 0xb4bb180e, 0x727ff446, 0x21456bf3, 0xf6d20d7d, 0x144b571f, ...)
   /home/luke/go/src/github.com/NebulousLabs/Sia/modules/consensus/accept.go:259 +0x102 fp=0x111ed408 sp=0x111ed328
github.com/NebulousLabs/Sia/modules/consensus.(*ConsensusSet).threadedReceiveBlocks(0x10b79080, 0x30b9e2c0, 0x10c7e028, 0x0, 0x0)
   /home/luke/go/src/github.com/NebulousLabs/Sia/modules/consensus/synchronize.go:213 +0x6da fp=0x111edd98 sp=0x111ed408
github.com/NebulousLabs/Sia/modules/consensus.(*ConsensusSet).(github.com/NebulousLabs/Sia/modules/consensus.threadedReceiveBlocks)-fm(0x30b9e2c0, 0x10c7e028, 0x0, 0x0)
   /home/luke/go/src/github.com/NebulousLabs/Sia/modules/consensus/consensusset.go:134 +0x36 fp=0x111eddb0 sp=0x111edd98
github.com/NebulousLabs/Sia/modules/gateway.(*Gateway).RPC(0x10bd7b80, 0x10c2b880, 0x12, 0x5b5410, 0xa, 0x10c7e000, 0x0, 0x0)
   /home/luke/go/src/github.com/NebulousLabs/Sia/modules/gateway/rpc.go:53 +0x3cf fp=0x111ede58 sp=0x111eddb0
github.com/NebulousLabs/Sia/modules/consensus.(*ConsensusSet).threadedInitialBlockchainDownload(0x10b79080)
   /home/luke/go/src/github.com/NebulousLabs/Sia/modules/consensus/synchronize.go:475 +0x57a fp=0x111edfa0 sp=0x111ede58
github.com/NebulousLabs/Sia/modules/consensus.New.func1(0x10b79080, 0x30b607d8, 0x10bd7b80)
   /home/luke/go/src/github.com/NebulousLabs/Sia/modules/consensus/consensusset.go:126 +0x1f fp=0x111edfb8 sp=0x111edfa0
runtime.goexit()
   /usr/local/go/src/runtime/asm_386.s:1585 +0x1 fp=0x111edfbc sp=0x111edfb8
created by github.com/NebulousLabs/Sia/modules/consensus.New
   /home/luke/go/src/github.com/NebulousLabs/Sia/modules/consensus/consensusset.go:140 +0x611

[bitspill]

Tyring to sync wallet and get this error

with v0.52

./siad
Loading...
(1/7) Loading gateway...
(2/7) Loading consensus...
(3/7) Loading transaction pool...
unexpected fault address 0x30c5c040
fatal error: fault
[signal 0xb code=0x1 addr=0x30c5c040 pc=0x292e00]

goroutine 12 [running]:
runtime.throw(0x585f38, 0x5)
   /usr/local/go/src/runtime/panic.go:530 +0x79 fp=0x111ed16c sp=0x111ed160
runtime.sigpanic()
   /usr/local/go/src/runtime/sigpanic_unix.go:27 +0x27b fp=0x111ed198 sp=0x111ed16c
github.com/NebulousLabs/bolt.(*Tx).rollback(0x110ed700)
   /home/luke/go/src/github.com/NebulousLabs/bolt/tx.go:245 +0x60 fp=0x111ed1b8 sp=0x111ed198
github.com/NebulousLabs/bolt.(*Tx).Commit(0x110ed700, 0x0, 0x0)
   /home/luke/go/src/github.com/NebulousLabs/bolt/tx.go:163 +0x1ec fp=0x111ed274 sp=0x111ed1b8
github.com/NebulousLabs/bolt.(*DB).Update(0x10b837a0, 0x111ed2cc, 0x0, 0x0)
   /home/luke/go/src/github.com/NebulousLabs/bolt/db.go:580 +0xee fp=0x111ed2a0 sp=0x111ed274
github.com/NebulousLabs/Sia/modules/consensus.(*ConsensusSet).addBlockToTree(0x10b79080, 0x0, 0x9b640000, 0x787a362e, 0xb5d8458d, 0xb4bb180e, 0x727ff446, 0x21456bf3, 0xf6d20d7d, 0x144b571f, ...)
   /home/luke/go/src/github.com/NebulousLabs/Sia/modules/consensus/accept.go:183 +0xd8 fp=0x111ed328 sp=0x111ed2a0
github.com/NebulousLabs/Sia/modules/consensus.(*ConsensusSet).managedAcceptBlock(0x10b79080, 0x0, 0x9b640000, 0x787a362e, 0xb5d8458d, 0xb4bb180e, 0x727ff446, 0x21456bf3, 0xf6d20d7d, 0x144b571f, ...)
   /home/luke/go/src/github.com/NebulousLabs/Sia/modules/consensus/accept.go:259 +0x102 fp=0x111ed408 sp=0x111ed328
github.com/NebulousLabs/Sia/modules/consensus.(*ConsensusSet).threadedReceiveBlocks(0x10b79080, 0x30b9e2c0, 0x10c7e028, 0x0, 0x0)
   /home/luke/go/src/github.com/NebulousLabs/Sia/modules/consensus/synchronize.go:213 +0x6da fp=0x111edd98 sp=0x111ed408
github.com/NebulousLabs/Sia/modules/consensus.(*ConsensusSet).(github.com/NebulousLabs/Sia/modules/consensus.threadedReceiveBlocks)-fm(0x30b9e2c0, 0x10c7e028, 0x0, 0x0)
   /home/luke/go/src/github.com/NebulousLabs/Sia/modules/consensus/consensusset.go:134 +0x36 fp=0x111eddb0 sp=0x111edd98
github.com/NebulousLabs/Sia/modules/gateway.(*Gateway).RPC(0x10bd7b80, 0x10c2b880, 0x12, 0x5b5410, 0xa, 0x10c7e000, 0x0, 0x0)
   /home/luke/go/src/github.com/NebulousLabs/Sia/modules/gateway/rpc.go:53 +0x3cf fp=0x111ede58 sp=0x111eddb0
github.com/NebulousLabs/Sia/modules/consensus.(*ConsensusSet).threadedInitialBlockchainDownload(0x10b79080)
   /home/luke/go/src/github.com/NebulousLabs/Sia/modules/consensus/synchronize.go:475 +0x57a fp=0x111edfa0 sp=0x111ede58
github.com/NebulousLabs/Sia/modules/consensus.New.func1(0x10b79080, 0x30b607d8, 0x10bd7b80)
   /home/luke/go/src/github.com/NebulousLabs/Sia/modules/consensus/consensusset.go:126 +0x1f fp=0x111edfb8 sp=0x111edfa0
runtime.goexit()
   /usr/local/go/src/runtime/asm_386.s:1585 +0x1 fp=0x111edfbc sp=0x111edfb8
created by github.com/NebulousLabs/Sia/modules/consensus.New
   /home/luke/go/src/github.com/NebulousLabs/Sia/modules/consensus/consensusset.go:140 +0x611

Are you on a 32 bit OS, unfortunately 32 bit support had to be dropped due to a limitation of the database utilized in the consensus.db

[Riseman]

https://github.com/NebulousLabs/Sia-GPU-Miner/releases/tag/v1.0.5

Is this the latest public miner for AMD?

That is the latest one put out by Nebulous Labs, but here is another public release that is optimized for Sia 0.5.1:

https://github.com/robvanmieghem/gominer/releases/tag/v0.2


You may want to try both out.

Can it be compiled on Windows or is it Linux-only?

Finally got it to compile. It seems to be 15% slower on my card than the official one.

[devlin]

https://github.com/NebulousLabs/Sia-GPU-Miner/releases/tag/v1.0.5

Is this the latest public miner for AMD?

That is the latest one put out by Nebulous Labs, but here is another public release that is optimized for Sia 0.5.1:

https://github.com/robvanmieghem/gominer/releases/tag/v0.2


You may want to try both out.

Can it be compiled on Windows or is it Linux-only?

Finally got it to compile. It seems to be 15% slower on my card than the official one.

Advantage is to run only one instance for all cards.

[xibeijan]

Tyring to sync wallet and get this error

with v0.52

./siad
Loading...
(1/7) Loading gateway...
(2/7) Loading consensus...
(3/7) Loading transaction pool...
unexpected fault address 0x30c5c040
fatal error: fault
[signal 0xb code=0x1 addr=0x30c5c040 pc=0x292e00]

goroutine 12 [running]:
runtime.throw(0x585f38, 0x5)
   /usr/local/go/src/runtime/panic.go:530 +0x79 fp=0x111ed16c sp=0x111ed160
runtime.sigpanic()
   /usr/local/go/src/runtime/sigpanic_unix.go:27 +0x27b fp=0x111ed198 sp=0x111ed16c
github.com/NebulousLabs/bolt.(*Tx).rollback(0x110ed700)
   /home/luke/go/src/github.com/NebulousLabs/bolt/tx.go:245 +0x60 fp=0x111ed1b8 sp=0x111ed198
github.com/NebulousLabs/bolt.(*Tx).Commit(0x110ed700, 0x0, 0x0)
   /home/luke/go/src/github.com/NebulousLabs/bolt/tx.go:163 +0x1ec fp=0x111ed274 sp=0x111ed1b8
github.com/NebulousLabs/bolt.(*DB).Update(0x10b837a0, 0x111ed2cc, 0x0, 0x0)
   /home/luke/go/src/github.com/NebulousLabs/bolt/db.go:580 +0xee fp=0x111ed2a0 sp=0x111ed274
github.com/NebulousLabs/Sia/modules/consensus.(*ConsensusSet).addBlockToTree(0x10b79080, 0x0, 0x9b640000, 0x787a362e, 0xb5d8458d, 0xb4bb180e, 0x727ff446, 0x21456bf3, 0xf6d20d7d, 0x144b571f, ...)
   /home/luke/go/src/github.com/NebulousLabs/Sia/modules/consensus/accept.go:183 +0xd8 fp=0x111ed328 sp=0x111ed2a0
github.com/NebulousLabs/Sia/modules/consensus.(*ConsensusSet).managedAcceptBlock(0x10b79080, 0x0, 0x9b640000, 0x787a362e, 0xb5d8458d, 0xb4bb180e, 0x727ff446, 0x21456bf3, 0xf6d20d7d, 0x144b571f, ...)
   /home/luke/go/src/github.com/NebulousLabs/Sia/modules/consensus/accept.go:259 +0x102 fp=0x111ed408 sp=0x111ed328
github.com/NebulousLabs/Sia/modules/consensus.(*ConsensusSet).threadedReceiveBlocks(0x10b79080, 0x30b9e2c0, 0x10c7e028, 0x0, 0x0)
   /home/luke/go/src/github.com/NebulousLabs/Sia/modules/consensus/synchronize.go:213 +0x6da fp=0x111edd98 sp=0x111ed408
github.com/NebulousLabs/Sia/modules/consensus.(*ConsensusSet).(github.com/NebulousLabs/Sia/modules/consensus.threadedReceiveBlocks)-fm(0x30b9e2c0, 0x10c7e028, 0x0, 0x0)
   /home/luke/go/src/github.com/NebulousLabs/Sia/modules/consensus/consensusset.go:134 +0x36 fp=0x111eddb0 sp=0x111edd98
github.com/NebulousLabs/Sia/modules/gateway.(*Gateway).RPC(0x10bd7b80, 0x10c2b880, 0x12, 0x5b5410, 0xa, 0x10c7e000, 0x0, 0x0)
   /home/luke/go/src/github.com/NebulousLabs/Sia/modules/gateway/rpc.go:53 +0x3cf fp=0x111ede58 sp=0x111eddb0
github.com/NebulousLabs/Sia/modules/consensus.(*ConsensusSet).threadedInitialBlockchainDownload(0x10b79080)
   /home/luke/go/src/github.com/NebulousLabs/Sia/modules/consensus/synchronize.go:475 +0x57a fp=0x111edfa0 sp=0x111ede58
github.com/NebulousLabs/Sia/modules/consensus.New.func1(0x10b79080, 0x30b607d8, 0x10bd7b80)
   /home/luke/go/src/github.com/NebulousLabs/Sia/modules/consensus/consensusset.go:126 +0x1f fp=0x111edfb8 sp=0x111edfa0
runtime.goexit()
   /usr/local/go/src/runtime/asm_386.s:1585 +0x1 fp=0x111edfbc sp=0x111edfb8
created by github.com/NebulousLabs/Sia/modules/consensus.New
   /home/luke/go/src/github.com/NebulousLabs/Sia/modules/consensus/consensusset.go:140 +0x611

Are you on a 32 bit OS, unfortunately 32 bit support had to be dropped due to a limitation of the database utilized in the consensus.db

No - 64bit.

[tintumon]

nice dip on Polo  I didn't think we'd get the chance to buy SC below 25 sats again... I'll try and find some btc to scoop some up

How would the price rise, if there is an infinite amount of coin supply?
The inflation should bring it down in the long run.

[4emily]

Thanks @bitspill.

Based on your advice to date and what I've otherwise read/guessed, this should be the sequence of steps:

1. Back up old wallet folder

2. Back up old consensus folder

3. Download and install the new client

4. Open the new client and create new wallet (I'm assuming the same thing will happen on opening 0.5.2 as did for 0.5.1 – i.e. automatic generation of a new password/wallet)

5. Close the client

6. Replace the new wallet folder with the old wallet folder

7. Replace the new consensus folder with the old consensus folder

8. Open the new client again and old balance from previous wallet will appear.

Is that correct?

Thanks for your further help 

Yes, except you can skip step 4. since you're copying over the old wallet no need to create one just to throw it away

Thanks.

Last question (hopefully):

What's the difference between UI and CLI, as in:

These are the UI and CLI releases for v0.5.2, which is essentially a formal beta release of v0.5.2-rc3. Please report any bugs promptly.

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

https://forum.sia.tech/topic/137/v0-5-2

[Tobo]

How would the price rise, if there is an infinite amount of coin supply?
The inflation should bring it down in the long run.

I think the main reason to have an inflation is to secure the decentralized network for a very long period of time by using the mining and rewarding system before any better solutions can be found. A decentralized network needs to be secured by a rewarding system one way or the other. In this kind rewarding system, if you set up a limited amount of coins in the beginning, your network will have a limited life because when you run out of coins you run out of the security.

Siacoin's inflation is not high imo. In about 5 years, the inflation is about 3.4%. In 10 years, the inflation will be under 3%. And in the long run, the inflation will be about 2% for long time. So in the long run, the inflation will probably be lower than the Sia network growth rate besides the lost coins.

In return, Sia got a robust and secured network and Sia can focus on the long term growth of its business and ecosystem. Siacoins' value eventually will depend on people's expectation on the growth of the business and ecosystem on Sia network. So once the market figures out the proper marketcap of Sia, they will see the real price of the Siacoins.    

In addition, the small inflation can perform as a kind stabilizer to the fluctuation of the coin price in the growing period. As we know that the fluctuation of coin price is a big threat and hurdle for a cryptocurrency to get adopted and bootstrapped in the real business and industry. The ideal situation for Sia is that its price goes up only when its market share and business adoption go up but in the mean time its price is stable enough for the market and business users to adjust easily for their daily business. Sia is a very business oriented project and when it becomes a real player in a real industry, the Siacoins you are holding will worth a lot.

[Riseman]

nice dip on Polo   I didn't think we'd get the chance to buy SC below 25 sats again... I'll try and find some btc to scoop some up

How would the price rise, if there is an infinite amount of coin supply?
The inflation should bring it down in the long run.

If BTC makes another bull run, it can cause a new altcoin dumping season. So we may still see 4 sat price again after several months.

[peercoat]

All we could hope that dumping doesn't goes under atleast 20 sat i.e. huge buy support.

[Tobo]

If BTC makes another bull run, it can cause a new altcoin dumping season. So we may still see 4 sat price again after several months.

I highly doubt about it because Sia has been making a lot of progress and today Sia is not the same Sia as 3 months ago. I think siacoin's price will be going up in general even if BTC's price is picking up as long as Sia can keep making progress as the roadmap has indicated..

[tintumon]

How would the price rise, if there is an infinite amount of coin supply?
The inflation should bring it down in the long run.

I think the main reason to have an inflation is to secure the decentralized network for a very long period of time by using the mining and rewarding system before any better solutions can be found. A decentralized network needs to be secured by a rewarding system one way or the other. In this kind rewarding system, if you set up a limited amount of coins in the beginning, your network will have a limited life because when you run out of coins you run out of the security.

Siacoin's inflation is not high imo. In about 5 years, the inflation is about 3.4%. In 10 years, the inflation will be under 3%. And in the long run, the inflation will be about 2% for long time. So in the long run, the inflation will probably be lower than the Sia network growth rate besides the lost coins.

In return, Sia got a robust and secured network and Sia can focus on the long term growth of its business and ecosystem. Siacoins' value eventually will depend on people's expectation on the growth of the business and ecosystem on Sia network. So once the market figures out the proper marketcap of Sia, they will see the real price of the Siacoins.    

In addition, the small inflation can perform as a kind stabilizer to the fluctuation of the coin price in the growing period. As we know that the fluctuation of coin price is a big threat and hurdle for a cryptocurrency to get adopted and bootstrapped in the real business and industry. The ideal situation for Sia is that its price goes up only when its market share and business adoption go up but in the mean time its price is stable enough for the market and business users to adjust easily for their daily business. Sia is a very business oriented project and when it becomes a real player in a real industry, the Siacoins you are holding will worth a lot.

Thanks for the explanation. makes sense.