I bought into Curecoin when it was .00190000 BTC. I'm still holding, but its current value is 3.94% of the purchase price. Is Curecoin going to be completely abandoned for Curecoin 2, or whatever it is to be called? It feels like I've ridden this one pretty much to the bottom.
Sorry you bought high! Nope, all Curecoin 1.0 coins will transfer to Curecoin 2.0, though there may be a coin conversion step due to the major protocol changes.
Interesting developments! Regarding the certificates (Curecoin 2), does this mean there will be some collaboration with the F@H devs? I certainly hope that assuming there is some sort of quasi agreement there will be more interest in Curecoin.
As the system is imagined right now, there will have to be collaboration, in order for them to sign the certificates. However, if they are either not available or not ready for the signing at the beginning of the new coinbase, we can temporarily sign the certificates ourselves, while still protecting both ourselves and the folders by never actually touching the coins. By design, validation of a certificate as block-solving can only happen first on the side of the folder. Here's the general flow, for which I *hope* to put up a blog post explaining in greater detail in the next few days, but as the result of travel may be difficult:
-> User sends request to Stanford, giving them their curecoin address, filling an optional 'extra' field, putting in a secret hash of a fixed-length 'secret' key, and agreeing on a way of getting the certificates back (automatic negotiation, server might give client a URL the certificate will be available at upon completion, for example)
-> User receives a workunit associated with this information
-> User completes workunit, submits it back to University
-> University validates certificate
-> University signs certificate using their publicly-known signature
-> University makes certificate available to user by previously-negotiated method
-> User acquires certificate, tries entire nonce range (points awarded) to find a block, hashing together the certificate concatenated with the secret key (for which the hash is stored in the certificate)
-> If block-solving end hash is found, they can now submit it to the network.
As a result of the above method, there is no way for the university to tell whether a certificate they sign will solve or not solve a block, therefore they would be unable to selectively award certain users with better/worse certificates.
Of course, the best method is tons of collaboration with the F@H devs, but this might not be possible at the beginning of the new course.