What kind of time-frame are we talking about here in terms of getting at least a "proof of concept" project going?
I think this schedule may be possible:
1. Two weeks: Prepare, agree and release three documents: an overview in non-technical language, a FAQ, and a technical but informal white paper which expounds the motivation and the design principles.
2. Three months: Demonstrate a "proof of concept" on a test network.
3. Six months: Release a basic but usable version 0.1.
(4. Generate some names while the difficulty is low.
5. Profit!)
Writing up a white paper? It would be nice and if you want to start that I would be willing to contribute to the content, but I would rather be programming right now at least to come up with a rough mock-up of the idea.
I will start on the documents. I would rather be programming too, but as kiba says: time is of the essence. This is an idea whose time has come. We can't get this done with just RHorning, kiba and me. We have to build a team. And a set of basic documents serves two important purposes: it attracts newcomers to the team, and it helps to keep the whole team working towards the same goal.
Here are some early tasks that fall on the "non-documentation" side, in case you or anyone else is interested.
* Set up the development environment. Are we going to use SourceForge? GitHub?
* Choose a project name. We've been using "BitDNS", but it's not really an accurate name because we're not reimplementing DNS, just domain name registration. Then register the ".org" domain.
* Set up a build process so that we can distribute for Windows, Linux and OS/X.
* Read, learn and understand the Bitcoin source code and its underlying principles.