Just for info, automatic update of these data is scheduled to start this week or next week

Actually, MtGox is more than just Japan.

Our head office is located in Tokyo (in Shibuya), and we have branches all around the world. For example for European deposits, we have a bank account in Poland held by MtGox Poland.

We comply as much as possible with local regulations in countries where we are present, and always look for opportunities to make our activity more compliant. In Japan we discussed with the FSA ( http://www.fsa.go.jp/ ) and were told that our activity is fine as it is now. We are also working with authorities in Europe and US to ensure our activity is in line with local regulations.

Hi,

The v0 getTrades is cached ~120 seconds, even with ?since=. The v1/v2 api is cached 15 seconds only if ?since= is passed.

However if you're looking for realtime activity, you should be using the realtime feeds.

As many of you may have noticed, price of Bitcoin increased.

The main impact we had here at MtGox before the price increased is an increase in number of accounts, which means more new accounts to verify everyday, and more support requests.

We are currently doubling the support staff at MtGox and should have new staff hired somewhere in April (hopefully), but I though it was worth sharing some numbers.



The satisfaction rate is usually with 90%~95%. See below graph.



I cannot give graphs for AML requests right now, but I can tell you that the rate of new requests increased in the same way, with around 1000 new requests on Friday. Three new staff will be starting Monday on the AML.

No change on the socketio url, however we are testing a new system that'll be much better to handle the load. Tests are currently being done.

Thank you for your message.

We are currently experiencing delays on EUR transfers of up to two weeks for larger transfers because of the daily limits imposed by our bank in Europe. We are currently negotiating larger limits with this bank and hope to be able to finally be back to regular delays by April.

In the meantime, you can track the status of your transfer from your wallet history. Status "confirmed" or "todo" means that the transfer is pending on our side. Status "pending" means the transfer has been submitted to the bank, and status "processed" means that we saw your transfer going out of our bank account.

Please contact info@mtgox.com should you have any question.

In the last 24 hours, data.mtgox.com has served 143513 requests for a total of 25.9 GB bandwidth.

That's just a fraction of what's being served on mtgox.com, but that helps already quite a lot.


If that's for uses such as development, then it's fine. Some websites actually hit our ticker backend once for every page load on their side.



None, but your suggestions are welcome on info@mtgox.com. I've read what you posted here and will use it. I'm not sure about user-defined order ids, as it's going to be using a lot of storage on our side, and all data is already gzipped if supported by the user agent. We'll be checking your other suggestions.

Actually a bitcoin address collision is very unlikely.

At MtGox we handle around 2.2 million active bitcoin addresses, and another 18 million addresses, and haven't had any collision with addresses already in the blockchain.

This said, collision on weak random generators are possible, and known to have happened with vanity address generators.

The limits are lifted, however spamming will still end in your IP getting blocked (not by us, but by CloudFlare, using their own method to choose to block you).

Either way getting the same data again and again will not result in new data being returned, remember this.

https://mtgox.com/api/1/BTCUSD/fulldepth is actually an alias to https://mtgox.com/api/1/BTCUSD/depth/full

Many people around here use our ticker to get the latest Bitcoin price, or other of our public data API (depth, etc).

Because of this, the strain on the system has been growing day after day, and has reached a level where we need absolutely to do something. We now have the ticker, depth and trade history available at a new url.

Because not everyone can afford to change their software to support our api v1/v2 ticker, we made this in a way that just replacing the hostname should work (mtgox.com => data.mtgox.com). Other API calls (ie. any api where you authenticate) should still be done as usual on mtgox.com. Please post on this thread or contact MtGox's support (info@mtgox.com) if you have any issue with this change.

Caching is slightly more aggressive for now, but we will reduce it once we confirm everything works the way we expect it to work. Please note that we added a "now" value to the ticker that will allow you to know how old the ticker is.

Ticker


Depth

Regular depth data


Full depth data


"Large" depth data (deprecated)


Trades



We will eventually replace the URLs on MtGox.com with Location redirects, however since this will most likely break many applications (follow location is not enabled by default on curl for example) and have a negative impact on performance of said applications, we start with a public announcement.

Please update your applications/software/etc by April 1st 2013.

Nope, only to user-imported addresses. For MtGox-generated addresses, we assume the private key is secure.

I believe if we add a 0.0005 BTC fee for any transfer below 0.01 BTC but > 0.0005 BTC, it should speed up things a lot.

We'll add a setting to enable this soon. Problem is this will be enabled account-wide, and not per address (because there is no way to modify an address afterward).

For transfers <= 0.0005 BTC, I guess the only solution is to wait for multiple ones to appear until sum > 0.0005

We could add the ability to have a fee added, but it means that you could end spending bitcoins without warning, which is a bad idea.

For information, sweep happens as soon as we see a non confirmed transaction for your bitcoin address.

Yubikey continue working the same as you still use MtGox.com.


CoinLab will only provide service to US and Canadian customers at this point. 0 balance accounts will be transferred too. The engine will still be MtGox's.

ISO 3166-1 defines "BC" prefix as free, if ISO 3166/MA was to assign "BC" to the Bitcoin Community, it could open other possibilites too (BCX?). It is however unheard that an ISO entity assigns a prefix to a community.

You have our support for BTC (if we can find someone to talk to in Bhutan) or XBT/XTC. Other names are not much representative of Bitcoin.

Why not all three?

Bitcoin is fully illegal in China, and our negotiations with the local government so far have been without success.

Either way let's be realistic here. Most of our customers are located in countries such as US, Europe and others. Running away to Vietnam or China would make it basically impossible for us to receive or send funds to anyone in those countries.


Japanese government is friendly to US, and also implements things such as FACTA. Also the US government can pressure any bank worldwide by threatening of cutting them off USD. A bank in any country that can not transfer USD anymore is of no use to anyone. US government has been doing this so far to get accounts held by "terrorists" (people linked to North Korea, mafia, actual terrorists, etc) and while Bitcoin is still too small to get this kind of response, it's a good idea to stay friendly with the US govt. at this point and let Bitcoin grow and gain in legitimacy.


Anyway none of this advice is actually applicable as it would shut us from our customers, makes us unable to hold any USD and potentially limit our transfer solutions to non-conventional methods (liberty reserve, webmoney, etc...).

We are doing our best to see Bitcoin grow as an actual alternative to the existing system, but until Bitcoin is large enough to stand on its own, we need the current system to accept and support us.

Actually people under CoinLab ToS will still be using mtgox.com and our system, just under a different contract.