Ö÷²¥´óÐã

« Previous | Main | Next »

Prime Number Challenge: Second Milestone

Comments

Share this page

Post categories:

Matt Wieteska - Code Master Matt Wieteska - Code Master | 12:49 UK time, Tuesday, 26 July 2011

79 ducks posted by Mari-Clare Bonner

Ìý

They said it couldn’t be done. They said it couldn’t be true. They said the second milestone in the Prime Number Challenge couldn’t have been broken a mere four days after the first. They have been proven wrong.

Congratulations are once again in order to all the Prime Hunters out there. A massively impressive organisational effort has led to the second milestone being smashed days before the first show has aired. Incredible work.

Without further ado, here is your second community challenge clue:

GAUSS

This should be entered in using the sixth hand on the codebreaker for week two. Bear in mind that this codebreaker will not be released until the week episode two airs, so you may have to wait a few days to use it.

So here we are. One day to the show. 100 primes to go. Show us what you’re made of.

Share this page

Comments

Be the first to comment

Jump to more content from this blog

About this blog

This blog was to support people playing The Code online treasure hunt. The final was won by Pete Ryland of London in September 2011 and as such the blog is now closed to further comments. However, you can still find handy hints and updates if you are playing for fun!

For the latest updates across Ö÷²¥´óÐã blogs,
visit the Blogs homepage.

Subscribe to The Code

You can stay up to date with The Code via these feeds.

The Code Feed(RSS)

The Code Feed(ATOM)

If you aren't sure what RSS is you'll find useful.

Ö÷²¥´óÐã iD

Ö÷²¥´óÐã navigation

Ö÷²¥´óÐã © 2014 The Ö÷²¥´óÐã is not responsible for the content of external sites. Read more.

This page is best viewed in an up-to-date web browser with style sheets (CSS) enabled. While you will be able to view the content of this page in your current browser, you will not be able to get the full visual experience. Please consider upgrading your browser software or enabling style sheets (CSS) if you are able to do so.