Topic: [ANN] Sia - Decentralized Storage - page 348. (Read 1382228 times)

I see the network is currently ~16 TB of data, but is there any graph of this over time? (to see how fast it is growing)

Its mine and should be taken with a (large) grain of salt. It is a bold assumption that total network storage will hit 1 Exabyte by year end. I think the potential is there, but a lot hinges on development of the protocol itself which is by far a done job.

The estimate further takes into account payment for storage alone, and not speculative elements that may drive the coin price much higher of course.

But lets just all guess for fun and don't take my estimate as any advice to invest etc etc :-)

(not my) price forecast 0.00000089 SC/BTC
http://forum.sia.tech/topic/100/what-will-the-price-of-siacoin-be-year-end

I try to check into this forum regularly, but it's a lot easier to follow the conversation on our private forum, because everything is broken up into multiple topics. I come here and see 3 threads of conversation that are all interwoven and sometimes overlapping, and it's more effort than I want to put forward to unravel it =/. And frequently, I'll completely overlook an important question that's buried.


At this point, Sia is more of a meta-organism. Nebulous is like the queen bee (eh, kinda). We write all the code and make all the important decisions, but the community has to agree to go along with them and other people are free to write as much or as little code as they want. 'siad', which is Nebulous's maintained client, actually does support removal of contracts. But, I do think you can ask 'what will Sia do', and in asking that you are wondering which direction the decentralized ecosystem will move. At this point, Nebulous has an enormous amount of sway over the direction of the ecosystem, but that's only because you guys like us and trust us. Already we're seeing people who refuse to upgrade, we're seeing alternate clients come out for the miner, alternate graphical clients and desktop plugins being released, which means people are exclusively restricted to the software we produce.

Full programmability of the redundancy is planned. Already you can do this by forking the client and changing the hardcoded numbers. In doing so, you will not fork yourself from the network (well... not from changing the redundancy constants. There are other constants you really shouldn't change). In the future, the API will allow you to change these number per-file, rather than requiring you to fork the codebase to make the changes (one step at a time).


Yeah, the real protection against censorship comes from the fact that all of the data is encrypted, and nobody can tell which files are bad or which are good because every upload uses a different encryption key. You can't even make a file blacklist for Sia, only a one-time-use 'ban this guy' list. And that only works for files that are being shared. It would be easy for someone to upload a file multiple times (therefore upload it using multiple keys), and then only one copy. When it gets deleted, they upload it another time, and share another copy. It's a whac-a-mole game that won't end.

well, Sia does not provide anonymity at the moment. So a host needs only record your IP address when you upload something to be able to ban you altogether. If whatever enforcement agency decided to be iron fisted, there are probably some pretty draconian things they could do to keep illegal files off of Sia. But again, only if the uploader ever shares them. If you upload a file and never share it with anybody, it's going to be essentially impossible to accuse you of wrongdoing.

Unnecessary to assume that anyone would have to bully Sia hosts to remove chunks/block uploaders by IP etc etc. Many hosts, especially those running a business based on Sia would willingly and enthusiastically remove content that has been blacklisted by a "reputable" source (read: copyright protection agency etc). Now, there is a problem and that's that not even hosts know what is stored in the encrypted chunks uploaded to them. Blacklists would have to operate on uploaders, i.e. hosts would have to block certain IPs from uploading to them.

"Sia", by the way, does not refer to an entity of any kind. There is Nebulous Labs, which develops and releases Sia code under an open source license. Thus, the question "what will Sia do?" is non-sensical. If the question was "Does Sia implement blacklisting / retroactive removal of files/peers?" then the answer is "Currently, no". I hope the Sia code-base never gets to this point. I don't see why it has to.

Sia is not under any country's jurisdiction. Still, it is entirely probable that hosts in some jurisdictions will have to comply with local laws that prohibits distribution of some kinds of content, under any circumstance eventually perhaps even when the host cannot reasonably know what they are distributing (i.e. cannot claim innocence for any reason). In those cases, the hosts themselves can readily implement their own peer black/whitelists if they so must. This would result in pseudo-private storage network within the global Sia network, where some hosts trusts only a very few other hosts, some hosts trust most except a few, and most hosts don't give a damn.

Oh, and in Edit this comment to Wolf0's answer:
A censor would not have to force ALL hosts to drop disputed content. If a censor knows about a particular file it doesn't like, then it may be in possession of a .sia file which allows the file to be downloaded from the network. That .sia file contains the IP addresses of all hosts that store chunks of the disputed file. This list is only a *subset* of all Sia hosts globally. It would be enough to target these (~20) hosts to make the file inaccessible. As these hosts may be someone's unhardened personal computer, that may not be such a resource intensive task compared to, say, bringing Amazon S3 to its knees. So, in effect, censorship by denial of service would be quite straight forward. For this reason, it would be nice if in the future an uploader can choose its own redundancy (currently hard coded) to make such an attack more difficult (at the price of also resulting in more expensive uploads).

Private forums are good, but don't desert this thread.

It's nothing wrong on your part, just inefficient gateway code. Will be fixed in the next release. Until then you can either wait it out or download a consensus.db from another user to bootstrap your node.

I downloaded SIA wallet and tried to sync.

But my wallet stuck @ 31200 Block Height. Peers show 8. But not syncing for a couple of hours.

Guide me to sync the SIA wallet.

I am using Sia UI version: v0.5.1-beta

I heard rumors that March will be good for Siacoin, Hope it does. By the way Sia is gaining volume at Poloniex.com

There is no IPO for Siacoins. I think devs premined the first 100 blocks which are about 30 millions of coins and almost nothing comparing to the overall numbers of the coins.

Can Sia censor files stored in it.  If I am a political dissident, and a country orders Sia to remove files I have stored there, what will Sia do? 
 
Also, were there any premines or IPOs with this coin?  Are files private, or can anyone see all files stored in it?

I think it could come any day now. Maybe tomorrow.

any news for pump? 

Doesn't matter if it's good or not.. If it's mined with GPU it's only a matter of time until someone make one..

not sure pool is a good thing for SIA!

https://bitcointalksearch.org/topic/poll-best-altcoin-for-a-dev-to-donate-effort-to-1377121

this is interesting.

 sorry, mine worked too - I seem to have confused two slack accounts

Just checked, the invite was working for me.

Can you try again with a gmail or check your spam folder?