on a side note, its way to easy to fake a creation date on a key (just mess with the clock), so being "the first one" means nothing
Thanks very much for this reminder. Someone else informed me of this (and in fact 'spoofed' a creation date and email on the MIT registry to prove it, oi!) so since then I've revised my instructions to refer to my fingerprint as published on my personal website and elsewhere. In the meantime I'll also work on getting my web of trust extended.
My new instructions are as follows:
After downloading the ZIP package for this generator, you should find a file named generate-wallet.html.sig which you can use to:
1) verify that generate-wallet.html hasn't been tampered with, and
2) get proof that it really was authored by Canton Becker (
canton@gmail.com) whose public key and fingerprint can be confirmed at cantonbecker.com, bitcointalk.org, etc.
For example, if you have GPG installed, just open the terminal, change directory (cd) to where this generate-wallet.html lives, and type:
gpg --verify --with-fingerprint generate-wallet.html.sig generate-wallet.html
I appreciate what you say about providing instructions for GUI front ends, but that seems like a lot of work on shifting ground. My own GUI front-end on OS X in fact won't easily show the fingerprint, it only shows the email address associated with the signature.
![Sad](https://bitcointalk.org/Smileys/default/sad.gif)