Here's how 2.0's stacking up for anyone who wants a quick summary:
2.0.0a1 releasedWe released an alpha version of 2.0 with core features enabled. IT IS IN TESTNET MODE. NONE OF THE COINS ARE REAL.
We'd love for people to browse through the source code:
https://github.com/Vorksholk/CurecoinOr download compiled jars (Need Java 1.7 or 1.8 installed) and run them:
http://1.curecoinmirror.com/2.0.0a1/2.0.0a1.zipWorking in 2.0.0a1-> Transactions Users can send testnet coins back and forth.
-> Merkle Signatures Instead of using ECDSA like Bitcoin, 2.0 uses Merkle Signatures, which are simple enough for anyone with highschool-level math to understand on a technical level, and are resistant to quantum computers. If you want a brief summary of Merkle Trees and ECDSA, see here:
http://1.curecoinmirror.com/Curecoin%20Signatures%20Compressed.pdf-> Certificate blockchain The blockchain is based on validation of certificates issued by certificate authorities. On the testnet network, these certificates are signed for users based on pointless computational work. In the actual 2.0 release, certificates will be signed by research institutes.
There are some bugs and limitations of this super-early alpha. During abnormal network conditions (super-fast blocks, etc.), transactions occasionally get rejected, and the sent amount is refunded to the sender.
The RPC commands are abysmally limited. This is one of the main features of the upcoming 2.0.0a2--tons more RPC commands.
Difficulty is fixed at 150000.
The ledger system isn't fully implemented--so the full blockchain is required to participate on the network. Most of the code is there, but 2.0.0a1 is about testing the blockchain, signature technology, and transaction propagation/inclusion.
The miner was thrown together quickly, and has some issues handling network connectivity issues, generally disconnecting permanently. I'll fix this, but it isn't a major priority, as it won't even be a part of the final release. It's a testnet thing.
For debugging purposes, clients will, by default, only connect to one peer, which we run. This is so we can easily reset the testnet, and monitor all network traffic for debugging. Obviously in the final release (or more realistically during the beta phase) peers will freely connect to one another, and we won't have to maintain any infrastructure (and won't have control over the network).
Some words about 2.0 features: 2.0 will have a number of technical innovations that set it apart from other crypto currencies. The ledger system will allow clients to store only the last 14,400 blocks plus the ledger, making the Blockchain a manageable size, and making coins 100% fungible.
Multisig addresses will be identifiable on the network, and will be defined by rules specified on creation; 2 or more Curecoin addresses will be defined as subordinates of a multisig address, and the structure of the multisig address defines how many of the subordinate addresses are required to create a successful outbound transaction.
Proving documents to the 2.0 blockchain will be trivial, supported by a special transaction type that survives blockchain pruning.
Proof-of-stake won't consider the age of coins in payout or priority, and stake blocks must be interspersed between certificate blocks, making it impossible to fork the network more than one block using proof-of-stake blocks. Addresses can earn stake without mining a block--simply by submitting a stake-generating transaction to be included in a stake block. People wishing to earn the transaction fees can create actual stake blocks. An address must not send coins for 14,400 blocks (30 days, subject to change) to stake. Coins received within the last 14,400 days will receive a prorated payout.