Topic: [ANN] Sia - Decentralized Storage - page 232. (Read 1382194 times)
I didn't expect this currency to go up so much, but I still don't like the currency of the storage class. Do I have to pay for the hard disk space? Is not to make an unnecessary move?
I can't see any higher development in the near future, cuz there is yet no bigger rise in internet traffic which would explain such demand for decentralized cloud storage. Right now the business is in the hand of the big five, with alphabet having the resources to swallow any interesting competition.
Picked up a cool couple million SC this morning. Price seems as if it might have bottomed up after the recent spike. Lets see what happens 
Sia Bounties!!!
https://t.co/7bZVQo6v8r
Bounty for Minio Integration
https://github.com/NebulousLabs/Sia/issues/2155
https://t.co/7bZVQo6v8r
Bounty for Minio Integration
https://github.com/NebulousLabs/Sia/issues/2155
I have a couple of open questions regarding SIA and I would be grateful if someone could answer them.
Currently, there are round 28 billion coins in circulation. What will be the final number of Siacoins?
Is there an upload size limit for a single file? Let's say I have a single video file with a size of 20 GB, is it possible to store it distributed?
Currently, there are round 28 billion coins in circulation. What will be the final number of Siacoins?
Is there an upload size limit for a single file? Let's say I have a single video file with a size of 20 GB, is it possible to store it distributed?
As indicated in the link of justAgame, there is no final number: block reward decreases over time, but once it reaches 30.000SC in 2020, it will be that reward forever. Coins in circulation will not necessarily increase over time forever, as Proof-of-Burn mechanics will soon be implemented for fosts (so Sia might even be deflationary in the future).
About the limit of single files, the bigger the better! Actually, Sia handles more gracefully few huge files than a ton of small files. Very small files should be uploaded in a compressed folder, as anything bellow 40Mb is treated as a file of 40Mb. The current upper limit for renter's uploads is estimated to be 5Tb (more than that might result in instability of the client). However, updates in the next 6 months will increase that limit to 40Tb.
What file size can I upload?
I guess I answered you too with my previous paragraph ;-) I have a couple of open questions regarding SIA and I would be grateful if someone could answer them.
Currently, there are round 28 billion coins in circulation. What will be the final number of Siacoins?
Is there an upload size limit for a single file? Let's say I have a single video file with a size of 20 GB, is it possible to store it distributed?
Currently, there are round 28 billion coins in circulation. What will be the final number of Siacoins?
Is there an upload size limit for a single file? Let's say I have a single video file with a size of 20 GB, is it possible to store it distributed?
https://forum.sia.tech/topic/161/about-siacoins-calculation-and-supply
about file sizes i dunno..
I have a couple of open questions regarding SIA and I would be grateful if someone could answer them.
Currently, there are round 28 billion coins in circulation. What will be the final number of Siacoins?
Is there an upload size limit for a single file? Let's say I have a single video file with a size of 20 GB, is it possible to store it distributed?
Currently, there are round 28 billion coins in circulation. What will be the final number of Siacoins?
Is there an upload size limit for a single file? Let's say I have a single video file with a size of 20 GB, is it possible to store it distributed?
I've 34000 SC invested. Some I bought at BTC0.00000720 and some at BTC0.00000418. I've huge expectations from SC as out of all storage cryptos, SC has best team.
lmao @34000....peanuts.
Everyone has their own amount they can play with, eventually it can grow big!
I've 34000 SC invested. Some I bought at BTC0.00000720 and some at BTC0.00000418. I've huge expectations from SC as out of all storage cryptos, SC has best team.
lmao @34000....peanuts.
What file size can I upload?
I've 34000 SC invested. Some I bought at BTC0.00000720 and some at BTC0.00000418. I've huge expectations from SC as out of all storage cryptos, SC has best team.
I was still in the syncing process with my slow old hard drive and had to stop then restart the client.
When I was doing it the client automatically starting updating itself to v1.3.0
Everything went fine and it keep all the blocks I received previously before shutting down the client.
So all is good with the update and will let you know when it has fully synced.
Now I see why you would need a ssd to do this because I am on day eight now(on and off and not straight!
). 
When I was doing it the client automatically starting updating itself to v1.3.0
Everything went fine and it keep all the blocks I received previously before shutting down the client.
So all is good with the update and will let you know when it has fully synced.
Now I see why you would need a ssd to do this because I am on day eight now(on and off and not straight!
). If you didn't mistype something I would be very concerned if the client automatically updated to v1.3.0. That version is not even released yet (still at the RC stage). Also I wasn't aware the GUI client auto updated even when it is released (you can manually ask it to update and it will).
I will look at the auto update stuff when I get home to my mac but your description is a little concerning.
work fine for me
I was still in the syncing process with my slow old hard drive and had to stop then restart the client.
When I was doing it the client automatically starting updating itself to v1.3.0
Everything went fine and it keep all the blocks I received previously before shutting down the client.
So all is good with the update and will let you know when it has fully synced.
Now I see why you would need a ssd to do this because I am on day eight now(on and off and not straight!).
When I was doing it the client automatically starting updating itself to v1.3.0
Everything went fine and it keep all the blocks I received previously before shutting down the client.
So all is good with the update and will let you know when it has fully synced.
Now I see why you would need a ssd to do this because I am on day eight now(on and off and not straight!
). If you didn't mistype something I would be very concerned if the client automatically updated to v1.3.0. That version is not even released yet (still at the RC stage). Also I wasn't aware the GUI client auto updated even when it is released (you can manually ask it to update and it will).
I will look at the auto update stuff when I get home to my mac but your description is a little concerning.
Make no release before it is ready.
The RC5 candidate for Sia was posted last night on the slack contributors channel. Plan earlier this week was to release 1.3.0 on Friday if it is ready. Testing on the RC5 candidate will determine that.
The RC5 candidate for Sia was posted last night on the slack contributors channel. Plan earlier this week was to release 1.3.0 on Friday if it is ready. Testing on the RC5 candidate will determine that.
Testing has shown that it is not yet ready for general release. It will be a couple more days before 1.3.0 comes out.
darval where did you get this information?
As I mention in a the quote you used, the sia slack, the contributors channel in particular which is where taek posts the upcoming release candidates.
http://siatalk.slack.com
There is currently a RC6 candidate there. Because of the scope of 1.3.0 changes, they have found quite a bit of problems and are unwilling to release it until they get them all resolved. RC6 resolves the problems they have seen to date except one (that I am aware of). Because of the instability tho, I wouldn't update to them unless you are willing to deal with some of these issues and provide feedback. If you are, please do join us and help test the upcoming release.
When I was doing it the client automatically starting updating itself to v1.3.0
Everything went fine and it keep all the blocks I received previously before shutting down the client.
So all is good with the update and will let you know when it has fully synced.
Now I see why you would need a ssd to do this because I am on day eight now(on and off and not straight!
). Make no release before it is ready.
The RC5 candidate for Sia was posted last night on the slack contributors channel. Plan earlier this week was to release 1.3.0 on Friday if it is ready. Testing on the RC5 candidate will determine that.
The RC5 candidate for Sia was posted last night on the slack contributors channel. Plan earlier this week was to release 1.3.0 on Friday if it is ready. Testing on the RC5 candidate will determine that.
Testing has shown that it is not yet ready for general release. It will be a couple more days before 1.3.0 comes out.
darval where did you get this information?
As I mention in a the quote you used, the sia slack, the contributors channel in particular which is where taek posts the upcoming release candidates.
http://siatalk.slack.com
There is currently a RC6 candidate there. Because of the scope of 1.3.0 changes, they have found quite a bit of problems and are unwilling to release it until they get them all resolved. RC6 resolves the problems they have seen to date except one (that I am aware of). Because of the instability tho, I wouldn't update to them unless you are willing to deal with some of these issues and provide feedback. If you are, please do join us and help test the upcoming release.
Make no release before it is ready.
The RC5 candidate for Sia was posted last night on the slack contributors channel. Plan earlier this week was to release 1.3.0 on Friday if it is ready. Testing on the RC5 candidate will determine that.
The RC5 candidate for Sia was posted last night on the slack contributors channel. Plan earlier this week was to release 1.3.0 on Friday if it is ready. Testing on the RC5 candidate will determine that.
Testing has shown that it is not yet ready for general release. It will be a couple more days before 1.3.0 comes out.
darval where did you get this information?
The blockheight is currently 114301 so you still have a little ways to go.
Yes. Almost double.So I do have a little ways to go.
Thanks for letting me know.
Very well appreciated.
Cheers to you and the entire SiaCoin community!
I've read earlier, that it will sync much faster if you'll use an SSD. I had my ETH Myst blockchain on HDD and it was syncing really slow. I saw the difference, when I switched to SSD
The blockheight is currently 114301 so you still have a little ways to go.
Yes. Almost double.So I do have a little ways to go.
Thanks for letting me know.
Very well appreciated.
Cheers to you and the entire SiaCoin community!
hey sia devs I get this error all the time. keeps crashing. plz fix...
Loading...
(0/6) Loading siad...
(1/6) Loading gateway...
(2/6) Loading consensus...
(3/6) Loading transaction pool...
(4/6) Loading wallet...
(5/6) Loading host...
(6/6) Loading renter...
Finished loading in 0.9977487 seconds
panic: page 29027 already freed
goroutine 28 [running]:
github.com/NebulousLabs/bolt.(*freelist).free(0xc0422e60c0, 0x284, 0xa8d3000)
/home/jrh/go/src/github.com/NebulousLabs/bolt/freelist.go:121 +0x2a1
github.com/NebulousLabs/bolt.(*node).spill(0xc0434abe30, 0x0, 0x0)
/home/jrh/go/src/github.com/NebulousLabs/bolt/node.go:363 +0x1e7
github.com/NebulousLabs/bolt.(*node).spill(0xc042139f10, 0x0, 0x0)
/home/jrh/go/src/github.com/NebulousLabs/bolt/node.go:350 +0xbb
github.com/NebulousLabs/bolt.(*node).spill(0xc042139180, 0xc0422e6360, 0xc0422e5a30)
/home/jrh/go/src/github.com/NebulousLabs/bolt/node.go:350 +0xbb
github.com/NebulousLabs/bolt.(*Bucket).spill(0xc04216c6c0, 0xc0422e5b00, 0x15)
/home/jrh/go/src/github.com/NebulousLabs/bolt/bucket.go:570 +0x182
github.com/NebulousLabs/bolt.(*Bucket).spill(0xc042054b78, 0x372f001c, 0xea0a20)
/home/jrh/go/src/github.com/NebulousLabs/bolt/bucket.go:537 +0x8ff
github.com/NebulousLabs/bolt.(*Tx).Commit(0xc042054b60, 0xc0421ac340, 0xc0422e5e88)
/home/jrh/go/src/github.com/NebulousLabs/bolt/tx.go:163 +0x12c
github.com/NebulousLabs/Sia/modules/transactionpool.(*TransactionPool).syncDB(0xc0420739e0)
/home/jrh/go/src/github.com/NebulousLabs/Sia/modules/transactionpool/persist.go:58 +0x4b
github.com/NebulousLabs/Sia/modules/transactionpool.(*TransactionPool).threadedRegularSync(0xc0420739e0)
/home/jrh/go/src/github.com/NebulousLabs/Sia/modules/transactionpool/persist.go:48 +0x130
created by github.com/NebulousLabs/Sia/modules/transactionpool.(*TransactionPool).initPersist
/home/jrh/go/src/github.com/NebulousLabs/Sia/modules/transactionpool/persist.go:126 +0x3cf
Loading...
(0/6) Loading siad...
(1/6) Loading gateway...
(2/6) Loading consensus...
(3/6) Loading transaction pool...
(4/6) Loading wallet...
(5/6) Loading host...
(6/6) Loading renter...
Finished loading in 0.9977487 seconds
panic: page 29027 already freed
goroutine 28 [running]:
github.com/NebulousLabs/bolt.(*freelist).free(0xc0422e60c0, 0x284, 0xa8d3000)
/home/jrh/go/src/github.com/NebulousLabs/bolt/freelist.go:121 +0x2a1
github.com/NebulousLabs/bolt.(*node).spill(0xc0434abe30, 0x0, 0x0)
/home/jrh/go/src/github.com/NebulousLabs/bolt/node.go:363 +0x1e7
github.com/NebulousLabs/bolt.(*node).spill(0xc042139f10, 0x0, 0x0)
/home/jrh/go/src/github.com/NebulousLabs/bolt/node.go:350 +0xbb
github.com/NebulousLabs/bolt.(*node).spill(0xc042139180, 0xc0422e6360, 0xc0422e5a30)
/home/jrh/go/src/github.com/NebulousLabs/bolt/node.go:350 +0xbb
github.com/NebulousLabs/bolt.(*Bucket).spill(0xc04216c6c0, 0xc0422e5b00, 0x15)
/home/jrh/go/src/github.com/NebulousLabs/bolt/bucket.go:570 +0x182
github.com/NebulousLabs/bolt.(*Bucket).spill(0xc042054b78, 0x372f001c, 0xea0a20)
/home/jrh/go/src/github.com/NebulousLabs/bolt/bucket.go:537 +0x8ff
github.com/NebulousLabs/bolt.(*Tx).Commit(0xc042054b60, 0xc0421ac340, 0xc0422e5e88)
/home/jrh/go/src/github.com/NebulousLabs/bolt/tx.go:163 +0x12c
github.com/NebulousLabs/Sia/modules/transactionpool.(*TransactionPool).syncDB(0xc0420739e0)
/home/jrh/go/src/github.com/NebulousLabs/Sia/modules/transactionpool/persist.go:58 +0x4b
github.com/NebulousLabs/Sia/modules/transactionpool.(*TransactionPool).threadedRegularSync(0xc0420739e0)
/home/jrh/go/src/github.com/NebulousLabs/Sia/modules/transactionpool/persist.go:48 +0x130
created by github.com/NebulousLabs/Sia/modules/transactionpool.(*TransactionPool).initPersist
/home/jrh/go/src/github.com/NebulousLabs/Sia/modules/transactionpool/persist.go:126 +0x3cf
The blockheight is currently 114301 so you still have a little ways to go.
Jump to: