Good work dooglus!

No, I wasn't, sorry if it was unclear

Britcoin order matching system is a bit broken (imo). It doesn't match the best order price, but seems to match exactly what you ask for. See the big britcoin thread for details, it's being discussed there.

I'm gonna need to start going to Ponzi's Anonymous at this rate...

1BTC in and 2.224BTC out, thanks

Simple - generate a new receiving address for every transaction and give the new one to each new person you deal with.

If you lose the wallet.dat that is associated with an address, the coins and any future coins sent to that address are lost. Morale of the story: keep wallet.dat safe and backed up.

(wallet.dat being the file the bitcoin client generates and stores on your filesystem)

Yes, you can generate and use as many receiving bitcoin addresses as you like. There is a list of all you've generated in the menu option "Your Receiving Addresses"

As to the passwords, bitcoin itself does not require one, no - you're probably seeing threads about mtgox, a trading exchange which was recently hacked.

Ah, ok, thanks for the clarification dooglus. Hope this is improved upon soon then.

genjix, ok, then it's not working.

I realise you have a lot on your plate at the moment with the bank situation, but if you or someone (is there a support address to email that might be better suited?) could take a look at why order 9314 was completed at £5 and not the £9+ that was on offer at the time, I would be most grateful.

I don't care about the lost £4, I do care about the same thing happening when I put in a larger order.

genjix, I assume the process you've detailed above is not currently implemented for the live britcoin?

A day or two ago while there were BTC buy orders for £9 and up, I put in a test sell at £5, and it sold for exactly £5, not the £9 or so I would have expected; ie, I was setting a minimum price of £5 that I'd accept, not £5 I wanted and ignore the better buy offers.

If this is fixed in the new exchange then great, that's how it should work.

Only a bit more difficult. The main problem is getting the secondary ATX PSU to turn on, since the motherboard won't be connected to it. You can use something like this:

http://www.techpowerup.com/articles/other/22

You'll want the secondary one to turn on before the system starts booting up too.

Are you going to update this Benjie?

2.23 into the pot.

Where does it say the database was stored on their computer? It doesn't, it says they had read only access - so the attacker presumably used their system to read from the live database.

As for which tables were leaked - the user table is the most interesting/damaging? Who cares about the order table?

They didn't. My details are in there and I reproduced the hash for my password with the following perl:

#! /usr/bin/perl
$salt = '$1$SALT$'; # this is the at the start of the salted password in the accounts.csv, it's 8 alphanumeric characters
$pw = 'MY_PLAIN_PASSWORD'; # do this on a secure box, you're entering your password into a text editor.
$encpw = crypt($pw, $salt);
print "Encrypted password: $encpw\n";

Observe how the printed hash equals the bit after the salt in the accounts.csv. Thus no hidden salt or trickery.

Not seeing a tenth as much action as the double trouble 3, shame

Go on then, in for 1.. What's the worst that could happen

Think it takes a while to catch up - my "reply" appeared about an hour after my 5th post.

Seems to have slowed down a bit.. reinvested my winnings from earlier, lets keep it going guys

Is your client caught up on the blockchain? What does it say for  blocks in the bottom right? Should be ~131411 right now.