This is probably a UI issue. Try running siac from command line instead to see if the daemon is running and synched.

CAT keeps making pinging sounds when trading. What kind of events do these pings correspond do? Whenever a trade is made? Is there a way to disable them?

I did not mention mining. I meant that 500m SJCX were initially created, 50m sold/distributed so 450m remains under your control ("locked" as you say). If you want to, however, those funds *can* be "unlocked" at any time. Correct me if I am wrong.

The "buy $850-worth of SJCX to participate" beta? How do you justify that when you sit on 90% of the pre-generated SJCX?

Does CAT support any kind of scripting, or is this planned? i.e. "program your own bot rules" which then gets executed by CAT.

Looks nice! I'll definitely move some coins over and get trading started on some of the pairs on offer.

I'm trying figure out whether its worthwhile to mine MagiCoin with my 32 CPU core machine. I found this mining calculator:

https://bitmakler.net/MagiCoin___mining

but I can't find numbers for Difficulty and Block Reward. Can anyone point me to a more complete calculator, or help me fill in the blanks?
 

Some graphs here:
http://siapulse.com/page/market

Will do!


Woohoo! This is great. I love my PyBitmessage :-)

I've been ignorant about Boolberry until now. Heard about it, but was too pre-occupied with Monero development to pay any real attention to what was going on.

I've been reading up on Boolberry for the last couple of days, when time allows. A lot of work has gone into other CryptoNote implementations like Monero and others. Could you point out for me some of the unique innovations (whether first or not) of Boolberry over the CryptoNote reference implementation?

I'm just starting to look at Boolberry for some applications. It seems to be in a decent shape, barring the (reportedly) reduced involvement by the lead dev.

Could someone please point out to me some of the improvements in Boolberry, over the reference CryptoNote implementation? And, how does Boolberry distinguish itself, say from Monero and Aeon?

I'd like to build from source. Do these instructions also include the wallet GUI??
http://boolberry.com/howto.html#linuxbuild

EDIT #1: Found the instructions here: http://boolberry.com/howto.html#build_gui

EDIT #2: Are there any PHP/Node/etc bindings for Boolberry? (something suitable for web work)?

EDIT #3: Is there a Boolberry Slack channel?

Thanks!

Clarification: Renters pay 3.9% in fees to Siafund holders. There are 10,000 Siafunds. So, each individual Siafund entitles the holder to 0.00039% in "commission"  for each paid file contract. If you have 10 Siafunds, you therefore get 0.0039% of each paid file contract.

Greed is your worst enemy, so if you made a good profit you clearly did the right thing. Investing 101. Congrats on your success.

Like you are really, really nice to everyone here? You've been turd talking everyone here since you entered stage. Don't expect anyone to reciprocate an offer for a video hangout with you. Simple reason being that you're mean as hell.

We read and we follow your arguments. We also read, and follow taek's arguments. We appreciate your concerns, but we do not appreciate your attitude.

You are, sir, a real dick-head.

Sorry, but I don't think anyone here thinks you have. Your posts read like the rants of a lunatic, at least as seen by the eyes of us sub-humans.

But no worries, in a thousand years time someone will find your posts and declare you the 2nd Messiah.

Are you suggesting that multiple hosts operating as one would simply ignore new chunks that are identical to ones previously received? Thus, creating a mirage of redundancy yet receiving payment? Is that the specifics of the attack you have mind?

Clearly, any coin is prone to much hype and excitement. Sia has already been through 1 or 2 cycles of moderate hype. I personally think the big "pump" is yet to come. But, putting excitement beside, have you attempted estimating the future worth of Sia based on projected usage and so on?

And if you ignore the factors of hype and excitement altogether, where will Sia be in a few years time in terms of actual users, compared to other coins?

My own projection is that once Sia starts taking on actual users (in the hundreds and then perhaps in the thousands), the price is Sia will just explode and it will  

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).

Up, up and UP!

In the original xRadon thread there was a mention that the protocol would enable decentralized storage. Where does Radium stand on that? Is this something that will be / is implemented? If so, how?

Will there be a Linux client?

This:
> I will continue to develop it and provide support as my time and interest allows.

sucks. A successful project needs developer dedication.

Any uses-cases so far for Radium?

Pre-mine?