It should be noted that those "green" transactions are usually simple, they always contain only one input, and two outputs. They should be easy enough to integrate the blockchain without too much delay, and if we can get pools and/or big individual miners to mine those in priority, things would be even better.

I don't think the client currently considers a fee on a transaction as a reason to give higher priority to "parent" transactions. It does sound awesome however, and I like the idea.


We are using a custom client to do that, I do not think the bitcoin client would let you do that at this point.

Actually if you look at : http://blockexplorer.com/address/1LNWw6yCxkUmkhArb2Nf2MPw6vG7u5WG7q

Look at transactions 597d00408b... and 557c87f205....

597d00408b... is "A to B"
557c87f205... is "B to C"

Both happened in the same block, which is the expected behaviour.


Previous tests did not always end in the same block, so I believe some miners may consider the second transaction lower priority as it involves not yet confirmed coins. In the case of those two transactions it was as fast as a normal transaction, but it cannot be guaranteed in 100% of the cases.

If we look at the previous transactions we can see it was sometimes coming out with a difference of 1 block, or even more. If pools could put priority on green addresses it'd (mostly) solve this issue.

The kernel went panic, and when the VPS was back, the database was not happy. We had the same issue a while ago because there was not enough ram, and I did configure the VPS with more ram. I guess it needs a bit more now.

Actually, no. We produce both transactions instantly, and send the second one without waiting for confirmations.

Following the thread from Instawallet about green address, we have decided to give it a try on MtGox.

When withdrawing on MtGox, you can check the option "Use green address" to cause your coins to be sent through the address 1LNWw6yCxkUmkhArb2Nf2MPw6vG7u5WG7q (or pass the option green=1 to the withdraw.php API).

We have however used a slightly different implementation than Instawallet here, ensuring there is never any coin remaining on this address, reducing the interest for "bad people" to guess its private key.

Each time a transaction is sent via our "green address", a first transaction is generated to send a random amount of bitcoins (larger than the total amount of coins withdrawn) to the address, then a second transaction is generated to get the coins "out". Transactions are always sent by pair and are broadcasted together.

This, however, causes transactions sent via the "green address" option to normal targets to take longer, as two transactions needs to be confirmed. Bitcoin services recognizing our green address will, however, be able to process those deposits in real time instead of waiting for confirmations.


We are thinking of rotating the MtGox green address once in a while, with new green address announced ~1 month in advance.


Any comment on this is welcome.

The issue of someone trading with himself is a complex issue.


If we just avoid executing the trade, we'll end with weird looking spread (overlapping buy/sell).

If we execute the orders without fees, we create an easy way for anyone to increase their trading volume and get lower trade fees without any actual trade.

One third solution would be to have both trades execute, but not record trade history. That's a bit more complex and is an issue as it wouldn't result in any traceable record for us, so it's not much of an option either.


So the last option is here, just execute orders normally. We expect people playing with stop orders have some understanding of the orders they have placed, and will know better than sell bitcoins for lower than they are trying to buy at.

We do pass the ID in the SEPA transaction. If your bank is not showing it, there's not much we can do. It is however useful if you want to contact us to inquire on the transfer status.


Make sure to include your transfer reference so we can look it up.

Actually we had to implement tighter checks on accounts to reduce fraud in Australia. However due to past deposits continuing to be reverted by the remote banks, Technocash decided to block our account, probably resulting in more reversals.

On the other side, in France, our french bank suddenly started to think that bitcoin is a virtual currency, and because of this believes we are doing something illegal as we are not registered as a bank, and therefore can't handle virtual currencies. We have explained that bitcoin did not fall within the definition of "virtual currency" under french laws, but they closed our account anyway in an illegal way, no wonder we already won 3 times against them in court.

We do understand the risks involved when accepting payments for goods we send we cannot recall. We are not a financial service provider, but we are required to implement the same kind of protections because of the context (instant delivery of bitcoin and no way to call back).

As a remainder, we only accept SEPA transfers in France.

Some European banks claim to be sending SEPA transfers but actually send wire transfers, which may be subject to fees and delays because it goes through the USA.

The issue here is our bank in France only provides us detail on the fees a few days after the transaction. Because of this such deposits are usually delayed. We are trying to contact other banks to tell them to send SEPA, but most do not want as they do not have the proper implementations to send SEPA from all their branches.

Anyway we'll solve this issue soon by having our French bank provide us directly the SWIFT extracts in that case, which will tell us the fees. This won't be possible before the end of the current lawsuit.

This is a known bug in bitcoind. Sometimes when we send funds, the original funds are too fragmented, and cannot be used to actually send anything. In that case it's often possible to send smaller amounts until the fragmented transactions are spent.

I already talked about this on #bitcoin-dev as it is a major issue, but haven't got any response. Instead we'll just use a different way of sending coins to prevent that bug from happening (should be fine starting next week).

We have fixed the bug with the "sending code" message remaining.

Please also make sure you did not make any mistake when writing the private key (it'll show you any bitcoin that was swept).

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

We've recently had some of our support team signup for the
bitcointalk.org forums and there have been concerns raised as to the
authenticity of these accounts.

I would like to verify both "MtGox_Adam" and "Mt.Gox Support" are indeed
employee accounts of Tibanne (Mt.Gox) and that they speak with the
authority of our official support team.


Mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)

iQIcBAEBAgAGBQJOioaGAAoJEBx5fDE8icJfbKkP/3pUc6ae+vgP4M3CthJylJsI
cRWdsWCxD0XHWx05Q85fUDB0a2YUR2xR79WWbcoKBJxMu9Z7SxkOXoRvVFYMgTZM
6mlBXaQ+s9/cH4RIOohT6jP6vuCoch/mYoyu0KwY97g7uZraZrQpBhVrWjsg0qPA
aL+Py8HcqPeB4piubCJopnVoCX0mjrf3Vwf8lJfAN5IlO4Jq0oHNe/Acw6S1UwqM
6R5ybd4bnh1z+RRPvBhRREcuTTscmdXs9iSQydYjp38KWGXlSJbSjR+u9uwv8FOq
nLt7C8wyejXfE0BoNKDXDFOEc03clgFik/27gA5rFQ9xgB6/b1qPq+aSa0JsQQWM
ozHYtFtoXwfyBImO1gkkkZKuLTuS36AZzOSBesMjzTVWglcIfLVR1DZIRWlQUPCG
QmkhP1UtQYc7fUlK2lbIUlhV/Ry35WzPWE/mFVHSk1c6j7qhdsGCYTz/KPpL6bsg
PaAFzJzQOGF68INMLqCujTe+A4R1NMN1YAR21KB8z4ZWgWjgsXHOe+v7l1t1zSCs
zivMsTOuREERNHs2GQQWOfmNlMghvjAkFlnMzWGlTtodd/wV0dcTjebmk0amY9va
e29sB+MkyNmdRe97lVXp9ga64gYdZ9zNkhjEg6dZI08gYwgNR03CpS03r7jlu2zz
POPIRj1Z1Ewxg+6qhvqq
=rtYn
-----END PGP SIGNATURE-----

Même si notre banque ne nous aime pas, la loi est de notre côté, et nous n'avons pas de difficulté ici a continuer ce que l'on fait toujours.

Par contre j'ai entendu que du monde avait du mal avec bitcoin7, peut être lié?

You think people who fall for mtgax.tk would verify open PGP signatures?

We try to push yubikey usage a lot, to avoid this. That's why we offered more than 1000 free yubikeys so far, and hope people understand that security is not that simple.

We'll probably show again euro withdraw option in USD again, for a limited time (or may allow a one time 0% fee exchange, please contact me on admin@mtgox.com if you'd like that)

As a business we are already paying taxes on bitcoin, as acquisition of valued non-expirable goods.

Euro withdraw are only possible from EURO currency. We are currently evaluating options available for withdraws in other currencies, and trying to get currency exchange made possible.

If you are in Europe, you really should change your main currency for EUR.

As you may have seen we are fighting with our French bank and the French law.

In the meantime, the bank is currently forced to keep our account open until the status of bitcoin is defined, as a virtual currency or not. As there is a fair chance it won't be considered a virtual currency, we are announcing the new account number and accepting deposits.

We check the account once an hour, so same day deposits are credited instantly. Normal SEPA transfers take the normal 2~3 business days delay.

Remember that by creating an EURO balance on your account you can avoid losing on the exchange fees. If you live in the EURO zone, I highly recommend you to switch your main currency to EUR (see your settings page, more information on the multi currency announcement).