CPUShare is temporarily freezed because of changing business condition in my real job.

All accounts have been successful withdrawn and some sellers made some real money. For the time being no more money is allowed into the system as I can't legally emit invoices anymore.

A few sellers accounts didn't withdraw yet despite they were asked to while my VAT was still open. If you didn't withdraw through the site yet, contact me and I'll manually send you whatever money you had in your account with paypal even if I won't be able to tax-offset it as a business cost anymore, that's not a problem.

My spare time has been very limited this year and it won't change much for the next 3 years. As time permits I'll try to release the CPUShare server code under the AGPL so anybody will be able to run a CPUShare server on its own paypal account.

Your private data in the CPUShare servers will remain secure, any clone site running the CPUShare software will have to register its own users.

This is great news for CPUShare, the more cores the more inexpensive excess CPU power in each workstation out there that can be sold to the ones that truly need it.

The old livecd stopped working because wget refused to download with https with the cacert private key. The new livecd is able to verify the cacert CA on www.cpushare.com as well as all other CA authorities. So hopefully this breakage won't happen again even if the CA of www.cpushare.com will change. I also upgraded the whole livecd, with all new versions of packages, including a new 2.6.24 based kernel. Please let me know if there's any problem with the new livecd. You can simply download the iso of your orders to test it.

A new CPUShare release is available that allows the buyers to submit bytecode without a .data section, fix submitted by the libcaca project.

In the last months CPUShare was fully maintained as usual but no new development happend because after joining Qumranet I've been working 100% of my work time on KVM development and related issues, so my time to dedicate to CPUShare diminished dramatically as I'm having so much fun at Qumranet with KVM.

The positive side is that my huge delay in switching to the KVM model, has allowed one project to start using seccomp actively, and this allows greater security for the sellers, and maximum performance and lowest overhead to the buyers. The other nice thing is that working on KVM as my real-life job, gives me greater confidence in adding the KVM computation model later.

I also plan to release the CPUShare server under the AGPLv3. I wasn't aware of the Affero General Public License until FSF released the AGPLv3 a copule of months ago. That has been one of the primary reasons of why it was mandatory for the server code to remain proprietary. If you read this far, it should be crystal clear that relasing the CPUShare server code under GPL or LGPL would be like releasing it under BSD (because it would allow anyone to fork and profit from a proprietary version of it without having to contribute their modifications back to the mainline version). The new GNU AGPLv3 should prevent the BSD behavior triggered by the ASP loophole. This however isn't a final licensing decision and I welcome any positive/negative feedback on it!

http://libcaca.zoy.org/wiki/CPUShare

As a side note, as long as this project will remain active, the seccomp API will be fully maintained. The only reason the seccomp API was being obsoleted by KVM in the CPUShare roadmap is that nobody used it for their own project yet, but this changed now.

The roadmap still includes the KVM support but it won't obsolete seccomp anymore unless all seccomp projects prefers to switch to KVM for whatever reason later. Seccomp still provides substantial advantages to the buyers (most important is the low overhead to distribute the executables) even if it's a lot harder to program with.