I think he ment if someone "found" the private key then Bitcoin is doomed as that could possibly conclude that sha256 mechinism is flawed which in turn means the banks are teh sucks and Bitcoin two!

I've changed my mind, I'll just do it myself and pay people to verify the information. That might work better.

BWUAHAH what a video to wake up to.

I dont know much about areagance except what i remember from my child hood, what would you recommend?

1Ass8PJDPPYpsCYN8fpVeXegVpb2kXsr21
hehe

What if we made an ad that depecited the 'dream' currency and the reader isnt allowed to use it. The reader /viewer of the ad will be so ticked off they cant have it they search up bitcoins

The first person to submit the first report will get 1BTC more then usual. so that’s 2 Bitcoins total.

Here is the main page: http://xenland.github.com/Bitcoin-Pseudocode-Client/index.html
and I fixed the verify bitcoin address page (but still needs some worked to be finished with) http://xenland.github.com/Bitcoin-Pseudocode-Client/index.html

Also forgot to mention publicly I shipped out the last winners prize.

Excellent!

 

What about combining the image idea along with the highlighted areas?

Or if you absolutly had to use text you could colorize the bitcoin address with 10 different colors and then in an image tell the user what color selected. No bot could solve that! Okay the bot could guess but it would only be correct once out of every ten tries(more times if your lucky)

Whats if the amount is in an image format

Oh i get it : pay this tiny amount to signup and to prove your not a bot

I could see this working if it required a scan of a qr code and then typing it in but i guess that wouldnt work becuase a bot could read qr codes... Idk

Looking at php decode encode base58 scripts i guess it isnt just removal of letters i overlooked it none the less dont have time to desrcibe the procceses for the next week or so

Thanks for the input, I'll be sure to look into that when I have time. If memory serves, I concluded base58 is really just alphanumerical string with out the 4 letters. I couldn't find any detailed information on the check sums to conclude it was required(or added any significance) to validate an address. Maybe if you could explain the processes of decoding that is required to validate. (As my examples shows you may not have to display how a SHA256() hash operation works that’s a little TOO detailed)

If you want the BTC just take what I started with for the incomplete subject and rewrite/append to it. and post it here.

Rules Are
The details should include at a minimum of two first formats.
1st format is a general description of the steps necessary to achieve the subject mechanism
2nd format is a pseudo code example of how the mechanism is performed.

That might be why nobody wants to contribute; the incentive is unknown.

What about 1BTC (+Tachikomas' rate)  for every mechanism written in detail.
The details should include at a minimum of two first formats.
1st format is a general description of the steps necessary to achieve the subject mechanism
2nd format is a pseudo code example of how the mechanism is performed.
(Pseudo code Standard: http://users.csc.calpoly.edu/~jdalbey/SWE/pdl_std.html )
3rd format(optional): Example how to do it in a applicable programming language(PHP, Java, JS Actionscript, LOLCODE)

Sources are required.
Pseudo code is required. (Styling is optional)

The topics need to be written are:
*Create a Bitcoin address (Already started but I don't have time to finish it yet someone could get easy BTC with this.)
*Query for a list of public Bitcoin nodes.
*Requesting information from other nodes (Should include instructions with all available current commands the official Bitcoin client accepts)
*Verifying the Block chain and individual blocks (Should include instructions on how to download/request blocks from other nodes)

---

I hope i didn't forget anything

I have thought of a quite a few ways but I haven't quite decided yet. I'm open to suggestions. There will almost more then liekly BTC in the future to give to more contributors, I just wanted to attract others to help contribute knowledge first before I decided.

The less work I have to do the better they will be compensated.

I noticed the bitcoin client information on how its mechanisms is scattered around and is almost always describing it at all different angles(Gets boring quick when attempting to research or develop).
For instance the description of a Bitcoin address not only involved the mechanisms on generating an address but also described the benefits and pitfalls of it in real world applications saying things like "Bitcoin address is like an email address", or "Bitcoin addresses are small enough to fit on QR codes"; You know things that are not developer related.

So my aim here is to acknowledge that the developer reading about Bitcoin client mechanism is already sold on using it now they just need to get to work on developing it and not spend so much "research hours" memorizing everything.

Basically: My vision for this documentation project is so a developer can click on the subject like "Create a Bitcoin address" and learn how to create a Bitcoin address just by reading one page. The developer then can do all the work in converted the pseudo code mechanisms to their selected programming language. (I sound like a broken record i know but I feel it helps get my point across)

Almost done with the documentation on creating a Bitcoin address
http://xenland.github.com/Bitcoin-Pseudocode-Client/

Updated documentation (Almost finished with writing on how to generate a bitcoin address with pseudo code)
http://xenland.github.com/Bitcoin-Pseudocode-Client/