Received payment into my australian bank account yesterday.

Fast turn around. I received money into my bank account within 48 hours of selling bitcoins.

I created the order on Thursday morning, by Saturday morning the money was in my account.

You receive transaction status updates by email, you get an email confirming your order and another one when they send the money to your bank account.

Overall I had a good experience during this transaction so based on this I can recommend them.

I hope the site will be setup for 24/7 trading in near future. It will definitely be one of my favourite sites to trade with.

Get 10% Discount use my referral TH-R11014

Please

Pretty Please

I've put in a small 0.5BTC transaction to test things out, I will report on progress within 24-48 hours.

I am also considering trading with bitpiggy.

How did that 10BTC transaction go?

Hi,

Excuse the redundant post if backups are already in development.

Would it be possible to include the function in the client to create automatic (triggered on schedule or event such as receiving coin/generating id) and encrypted (eg. with AES) backup of wallet.dat?

The default settings, could be to keep 1 encrypted backup copy everytime something changes in wallet.dat.
The user could be asked for password and default save location on first run.

Even if users do not care about doing backups themselves, the software would at least protect them somewhat.

Also when I say encrypted, I mean encrypt the entire file, however if the private key encryption feature becomes standard then simply copying wallet.dat would suffice I guess.

The backup is essential imo, in order to protect oneself against catastrophic loss of all coins in the event of wallet.dat file being damaged due to the following:
a) sudden loss of power
b) hard drive failure in particular in the wallet.dat sectors
c) malicious software modifying/deleting wallet.dat
d) accidental/negligent erasure by user (ie. kids playing around with computer, reinstallation without backup etc)

Hi Guys,

I am not sure if this has already been discussed, or slated for implementation, if so please forgive my redundant post.

I have an idea about how we can secure wallet.dat somewhat against theft (ie. copy of the file).

Why not implement AES encryption of the private keys stored in there?
(no point protecting public keys, as balance information is public anyway)

a) Everytime a new ID is generated and everytime someone wants to send a transaction, why not have the client ask for a password to encrypt/decrypt the private key as appropriate?

b) During encryption/decryption, the supplied password is hashed and then the hash is used to encrypt/decrypt.

c) This way even if the wallet is stolen, no one can spend any of your money (which is the most important thing) which should discourage wallet.dat theft.

d) Furthermore, in the software it would be a good idea to make sure that once the id generation/send transaction process completes, all traces in memory of the unencrypted private key, password and password hash are zeroed out.

What do you guys think about this?

I think such a feature will help with mass adoption, because it would say to the average user, you can copy my wallet all you want, but you can't spend anything in it.