Going great! This weekend I'm finalizing the code for Merkle signatures (including the certificates used for folding mintage), and hopefully wrapping up the specs of the transaction formatting. The Curecoin 2.0 transaction system is fairly basic at this point.

On the in-progress list:
Blockchain database (need to optimize for performance and storage space)
Certificate formatting (this is more of just a final approval on the existing specifications we discussed months ago)
P2P Networking (a fair amount to do here)
GUI

Then the upcoming list (all of which are non-essential items which can be added later, but would be nice at launch):
-Light merchant 'scripting? not even.' language: Can tell daemon to perform job x upon completion of condition y
->Example 1: Send "x8cmeob" to 192.168.0.12 when <address> receives 8 CUR
->Example 2: Append "x8cmeob" to file "transactions.txt" when <address> receives 8 CUR
-Basic accounting features built-into GUI wallet (group addresses into an account, produce transaction records for a given account,  etc.)
-Some indication/measure of network health and connection quality

Curecoin 2.0 will be cross-platform at launch, with a compiled binary available for Windows, Linux, and Mac OS X.

For anyone interested in the practicality of Merkle signatures for a cryptocurrency network, an address capable of signing 8192 transactions takes around 3 seconds to generate on modern hardware using one core. People will be able to choose what capacity address they would like to use. More capacious (more possible transaction signatures) take longer to generate. Lowest possible will likely be 4096 transactions, with the highest being either 32768 or 65535. 4096 will be far more than 99.99% of use cases. Signature verification takes a trivial amount of time. Signatures are small enough in size to not produce blockchain bloat. Private keys require less than a megabyte each.