Moo! Wrapper

About Moo! Wrapper

Moo! Wrapper brings together BOINC volunteer computing network resources and the Distributed.net projects. It allows a BOINC Client to participate in the RC5-72 challenge.

If you want to learn more about Distributed.net Project and Client, please visit their website. Especially, detailed information about the RC5-72 challenge is available.

Note that we have intentionally left Distributed.net OGR-project out of scope since you can already join that project at Yoyo@Home.

Join Moo! Wrapper

Read our rules and policies
This project uses BOINC. If you're already running BOINC, select Attach to Project. If not, download BOINC.
When prompted, enter
http://moowrap.net/
If you're running a command-line or pre-5.0 version of BOINC, create an account first.
If you have any problems, get help here.

Current crunchers

Your account - view stats, modify preferences
Teams - create or join a team
Certificate - print contribution certificate
Applications - versions and supported platforms
Donations - help with our monthly operation costs

Statistics

Community

Other

Languages

News

Fresh subspaces ahead!
We have been processing key blocks from a fresh subspace for few days now. This should help with any problems caused by the previous more or less fragmented work units we've been sending out. Thanks for sticking with us through the bumpy times.

You can read the upstream announcement at http://blogs.distributed.net/2012/05/04/15/23/bovine/.

Let's keep our CPUs and GPUs hot with work! :)
12 May 2012 | 17:37:17 UTC · Comment

Domain expiration mishap
The Moo! Wrapper domain moowrap.net was inaccessible for few hours because the domain expired yesterday (30. Apr). I failed to renew it on time because of some miscommunication with my service provider representative and me been too busy with my day job to handle this correctly, on time.

Domain is now renewed for next three (3) years and should be accessible once again for everybody (or slowly getting there as DNS record updates make their way through the net). I'm sorry about this short hickup on the project availability.
1 May 2012 | 15:11:51 UTC · Comment

Hard drive failure on our primary database server
Our shiny new primary database server, that's been responsible for the nice performance lately, decided that things have been way too stable. So this Sunday morning at about 6:38 EET* the server killed it's primary hard drive bringing everything to a grinding halt. :(

I've switched to using our replicate DB until data center staff can replace our failed hard drive and/or server. I'm currently bringing the services back online slowly to catch things up. Note that things might be slower until the first onslaught of clients reconnecting is over.

Good news is that there shouldn't be more than few seconds of DB changes lost because our database is replicated to the secondary server. Please, do tell if you see something strange. Bad news is that there's going to be a maintenance break in the near future when I switch primary DB back to the resurrected server (maybe next weekend, if things run fine with only one DB server).

*=That's 5:38 CET or Sat 20:38 PST and for other timezones, please see http://www.timeanddate.com/worldclock/fixedtime.html?iso=20120212T0635&p1=101&sort=1.
12 Feb 2012 | 18:33:28 UTC · Comment

... more

News is available as an RSS feed RSS