Assuming SigmaX launch goes smoothly and no major issues present themselves with the larger network, then CC2.0 is just a matter of replacing the PoW algorithm with certificates, which won't be difficult at all. We'll probably just gather the Curecoin community's opinion on how long we should let SigmaX run to be confident that the network scales well, which I expect will be two or three weeks.

Hey everyone, sorry about the radio silence!

The 2.0 code is coming along nicely, but we need to do a larger-scale test of the mini-blockchain + merkle-signature scheme.

The Curecoin developers are planning to launch a beta of "SigmaX," which will be a PoW-only quantum-computer-resistant cryptocurrency, based on the refactored 2.0 code I'm polishing up. We want to stress that
Curecoin is still our primary project, but SigmaX will serve four purposes:
-Non-ghosttown blockchain to test our ideas for 2.0 before launch (primarily looking at scalability of our mini-blockchain implementation)
-Give a quantum-computer-resistant blockchain to people concerned about the centralization of Curecoin 2.0 certificates
-After launch of cc2.0, serve as a production test for updates
-Get exposure for the Curecoin project

SigmaX will have a small (<1% of the first year of mintage) premine, which will be paid to current holders of Curecoin (we'll do a "snapshot" of the Curecoin blockchain at a certain block, and people will sign a message with their curecoin address to redeem their portion of the SigmaX). No dev funds, no IPO/ICO/crowdsale, and any unclaimed part of the premine will be provably burned after a few months.
We'll launch the beta for SigmaX in the next week (testnet), and the full network launch will come a few weeks later.

SigmaX will also use what we call a 'narrowing' hashing function which could make scalable treechains possible in the future. The algorithm will be CPU/GPU mineable, with an OpenCL and CUDA miner available on launch.

Hey everyone, 2.0's still chugging along, a tad behind schedule. I'm rolling the plans for the next two public betas (2.0.0a7 and 2.0.0a9) together, because when significantly overhauling the code, I realized it didn't make sense to re-write and optimize things that are going to be removed (such as the static difficulty calculations, some PoW/PoS code chunks, the dead weight of a lot of the block parsing code introduced from bolting PoS onto 2.0.0a3, etc.) so 2.0.0a7 is going to be cleanup + variable difficulty/block timing/peer seeking.

Life is extremely busy, but I'm hoping to have something in public hands in the next few weeks.

Drug development is a fairly slow process, so there's certainly nothing on the market you can buy today that was the direct result of Folding@Home research.

A few years ago, F@H found several drug candidates which appear promising for Alzheimers, and in 2010 tests were performed on tissue samples. 2011 saw Folding@Home simulate several mutations of the amyloid beta peptide, and is now researching interactions between enzymes and misfolding of Aβ. http://pubs.acs.org/doi/abs/10.1021/jm201332p

A tumor suppressor, p53, responsible for about half of all researched types of cancer, has been researched extensively in the past decade by F@H. Mutations/misfolds of p53 cause the "cancer kill switch" of cells to malfunction, allowing abnormal cells to develop and reproduce. A promising protein which marks cancer cells for the immune system to attack, Interleukin 2, has been researched by the Folding@Home project recently.  Big pharma have previously expressed interest in the compound, but the side effects have been too extreme. Recent findings from Folding@Home of an alternate form of Interleukin 2 which is orders of magnitude more effective and with fewer side effects, has sparked laboratory research from the NIH, who are currently testing it in a variety of tumors, with an end goal of a deliverable medicine. http://www.ncbi.nlm.nih.gov/pubmed/22446627

They've also made significant contributions to the field by designing, testing, and refining computational approaches to a variety of problems including potential mechanisms for disabling RNase H (an enzyme responsible for helping HIV transcribe genetic information) and designing drugs which modify or disable only targeted cells, enzymes, proteins, etc. https://folding.stanford.edu/home/faq/faq-diseases/

If you'd like to browse through all 129 papers produced by researchers in conjunction with Folding@Home, see here: https://folding.stanford.edu/home/papers/#ntoc100

That's quite a few blocks! Looks like suprnova sees (currently) 6 blocks from you https://ar2.suprnova.cc/index.php?page=statistics&action=blockfinder. Are you sure you're reading the correct stuff? At any rate, pool mining is certainly a good idea at this point in time.

In the last few days, Google reported that its D-Wave X2 outperforms single-core classical computers by a factor of more than 10⁸ for some traditional optimization problems.

Researchers believe that cracking ECDSA is possible with a modified version of Shor's algorithm. Bitcoin uses 256-bit ECDSA (Secp256k1) for signing transactions, which researchers estimate to require somewhere around 2000 qubits to successfully attack. Google's D-Wave X2 has around 1000 qubits. It's also extremely important to note that this isn't a general-purpose quantum computing, but rather built specifically for quantum annealing, so it isn't capable of implementing Shor's algorithm (or Grover's, for people concerned about mining). Also important to note is that far more qubits may be required for error checking, where tens of physical qubits might be required for each logical qubit.

Of course there's no proof yet that a quantum computer can attack these problems in real life at such a scale, although rudimentary quantum computers have successfully run Shor's algorithm to factor small numbers (which applies directly to RSA, which uses the difficulty of factorization to derive security from).

At any rate, it's great to investigate solutions (like Merkle Trees) that we believe to be impossible for quantum computers to compromise given the pace of development in that field.

Yeah, those aren't mined by you though, they're just new blocks on the network.

That's the network mining blocks, not you. It's updating to the latest block.

Where are you seeing the 30 blocks you solo mined?

What's the output of

What blocks does it show generated?

30 blocks in an hour is pretty hard to believe--you might not be synced up with the network, which means you're mining at the difficulty of the network at the first block. How many connections do you have?

For anyone wanting to run testz's miner on Linux, WINE worked fine for me.

On Ubuntu 14.04:

Then you can just run the cpuminer:


If you have a high-core-count system, I'd recommend running multiple different instances of cpuminer, each restricted to several cores, as I've found I can get 50%+ more performance running several smaller instances each restricetd to a small number of cores:

And so-on and so-forth. Screen is useful here.

Also renting mining power for 0.000017 BTC/kH/hour if anyone's interested.

Thanks! Sent some coins

Didn't notice your post count/activity when I first commented, hence a bit more paranoia. Miner's working extremely well!

Works wonderfully, getting about 3.7x the speed of the previous miner. Donation address?

Also, for anyone curious, I ran wireshark for five minutes in the background with nothing but the miner running, and nothing looked suspicious. That being said, that's no guarantee that it's safe--maybe it didn't find what it was looking for, maybe it waits for a longer time, who knows. But based on 5 minutes of network recording, everything looks vanilla. As always, VMs are a great way to protect yourself.

Renting hashing power at 0.000065 BTC/kH/hour (about $0.028).

Thanks to testz's (way) faster miner, I'm renting hashing power at 0.000017 BTC/kH/hour.

What OS are you on?

There's no GPU miner at the moment, but you can use the CPU miner floating around

What error(s) are you getting?


Of course, you can change the above stratum+tcp://... to 127.0.0.1:5555 for local solomining if you have RPC set up correctly, and the username, password, and thread count need to be set.

As usual, I'd recommend putting it in a screen session so it doesn't die if you close your SSH window:

If the above doesn't work, install screen:

This works fine on Ubuntu 14.04 fresh from an ISO.

Received, cheers! Yup, a few days of folding for me too, but on the plus side it's also a room heater.

Sent the CURE, here's an AR2 address: 4oEvG1hJQmbSZjHrGs2iTtta7b1MpKAzWk

TxID for CURE: 1324c496fe2e30a7dbc9f244ab49b00f9d6b166ef8ef447a92457f301bf56b82