I know there's an old post in this forum that explains clearly how to make that genesis block

Pywallet can import 10000 addresses but yeah you'll have to wait a bit

Je pourrai pas être là 
Par ailleurs, j'enlèverai mon numéro à ta place, ou les bots de spam sms vont s'en régaler

Parallel importing means parallel wallet.dat modifying
I think that is the problem

Bitcoin-qt -> help -> about bitcoin -> console tab

He meant 0.3.25
BTW pywallet now works with last wallet versions

If it doesn't show up in blockchain.info you should delete it from your wallet (see pywallet.tk)

https://bitcointalk.org/index.php?topic=174388
Maybe the solution is an exchange made by trustable people that then create one
Not a 'trustable' exchange that then makes its creators known

Oh wow

Yeah of course!
And I forgot I coded the update page that way... That's kinda stupid actually
I'll change that to the ajax way...

Yup good idea I'll put that soon


That would work too right?

Lol

Great, so that works
It's true I should add a little message to say everything happened as expected

Thanks!  


To everybody: I pushed the new version, can you check that pywallet tells you there's an update? and that auto-update works?

What language?
Why not BTC?

Back up your wallet first
You can try to dump your wallet with pywallet to see if the addresses are still there

I think this is a good idea
I'm a web+bitcoin developer if this idea takes off and help is needed
About invites black market, the identities could(should?) be linked to this forum username, thanks to signing with addresses in signatures for example

Nope, during a rescan the client reads all the blockchain and repopulate the wallet.
The "issue" is that you lose your unbroadcasted transactions. But it can be used when you made a transaction that won't never be include in a block for example.

Oh yeah I forgot to test that

I just looked at the code and... erm... before importing a private key in an encrypted wallet I don't check if it's the right one (-> todo list'd)
So it makes things easier to test:

• create a dummy encrypted wallet
• pywallet.py --importhex --importprivkey 0123456789012345678901234567890123456789012345678901234567890123 --passphrase anything_that_is_not_the_correct_passphrase

That should import the address corresponding to 01234... but with the bad encrypted private key
See what then happens (I can't test right now)