Begun, the clone wars have.

Our thoughts exactly. With the entire 20 seconds of attention I gave to reading about that project, it appears someone could fold on the curecoin team with their Couterparty address, kindof a 'merged folding' system. Don't quote me on that working though.

Ah, alright. So their system works much like Curecoin, currently. Disregard above mention of merged folding...

Cheers, folding anywhere still has the same scientific benefit, even if crypto isn't involved

That is a great movie that explains what Curecoin are, good job!
//Aboy68

They are purely ideas that we are tweaking and researching, but some points of mention:
-Quantum-computing-resistant signing algorithm (thinking Lamport)
-Peer-to-peer layered-encrypted traffic
-Multisignature and round-signature addresses
-Wallet ease of use for merchants (rather than continually pining the client "Did I get a transaction on <address?>" you can tell the client "When you get a transaction larger than <amount> on address <address> do <something>"
-Certificate-based blockchain (universities or other entities providing meaningful distributed computing projects issue certificates to users for work done, which are valid for creating blocks on the curecoin network, and could be used to do distributed folding "pools")
-Wallet which enables the locking/unlocking of specific addresses or address pools
-Distributed blockchain storage (where clients, using a simple AI, pool together, each holding certain parts of the blockchain, and redundantly querrying other peers for blocks that they don't have stored)
-A wallet in 'server' mode which would allow any simple 'thin client' to store only private/public keys, and to query a full wallet for txhistory, and to submit transactions signed client-side to the network
-A contract system with built-in software checksums (Two users want to make a contract for a service. One builds a program that verifies the service has been completed. The other verifies this external program is valid. The checksum of the program is taken and written into the contract. Upon either party invoking a completion request, the program is executed on both machines. If the results agree, the contract is finished. If not, then the contract can be contested and a third-party can step in and run the program and verify the result. Programs would be built in a custom scripting language built into the network. This idea is very rough, and very likely to never see prime time. It's an interesting concept though!

Anyhow, nothing above is guaranteed, but we're doing our research, writing test code, testing attack vectors, etc.

After the first day of the Conference, here's a bit of a recap: link

Less easily communicated in a coherent update is just how busy the team was making connections and talking to people about CureCoin generally. Today should be as busy as yesterday, so here's hoping the team has another big day!

short answer = 0