Paxum is no longer an option, and the reason is well known to everyone here.

The paxum add funds option was made visible again by error on the page, and is hidden again now (and will be fully removed soon to avoid this from ever happening again). Sorry for the misunderstanding.


Mark

Actually the old one was disabled because it was causing too much strain on the system. We are working on a viable solution (socket.io seemed to be used by some big players, but after testing this ourselves we found out it's far from being stable at all).

Anyway we got another option currently on planning stage that may go live by end of may if socket.io do not fix their thing by then.

Actually... no.


I guess then the only option is to download the kml and load it in google earth. It used to work when the db was not that big (currently over 100k known bitcoin nodes).

Some time ago, I created a bitcoin network analyzer that would collect information on all the available bitcoin nodes.

The system hasn't been updated for a long time, however it was recently updated to process connection attempts much faster, while giving nodes more time to accept the connection attempts.

The database was erased and re-created today, and the next dump will include a new info, "Last_Error", which is a small string giving details on the last error we had ("timeout", "connection_refused", etc).

The main interest of these database dumps is of course historical, as it shows the progression of the bitcoin network over time. It is free to download to anyone, directly from http://dump.bitcoin.it/misc/

The next file (20120223) will restart from an empty database, with the new field, and the new scanning method. It is possible to have a realtime overview of the database from this API: https://mtgox.com/api/stats/accepting (and people writing bitcoin clients can use the bootstrap api to collect initial bitcoin addresses to connect to: https://mtgox.com/api/stats/bootstrap )


Anyway, this thread has two goals:

• If you have any suggestion regarding this system (extra data we could collect), let me know. I'm planning on adding a passive node too that would collect data from nodes which are not available from outside (firewalled).
• If you make anything out of the historical data available, post it here

And a last nifty thing that can be done with this: http://maps.google.com/?q=https://mtgox.com/api/stats/bitcoin.kml

UPDATE: The next database version will also include a User_Agent field containing the user agent transmitted by the bitcoin client (see BIP#0014 for details).

The documents you sent us have no value as identification document. They show you have a request in progress, however it is not acceptable as an ID proof for us (ie. via Internet).

Any ID document submitted to us has to be a valid ID document, including picture, date of expiration, document number, etc. and must be submitted in color with a good enough scan. The documents you have submitted do not fit into "valid ID document".

Anyway our legal department confirms your request is not receivable as such, until you can submit a valid ID document.

Your account was flagged as "AML data required" on Sun 25 Sep 2011 (JST) and we haven't received any valid document from you since then. Considering the risks involved we will get in touch with the payment processor to confirm your identity.

Your account has been deemed suspicious since you have been accessing your account from various countries (which I won't list for privacy reasons). This is an issue most people living outside their home country have. Being myself an expat, I have been often frustrated at being unable to use my credit card or seeing my order delayed.

Guidelines for AML/AT/KYC say that if the payment method cannot be linked to the country of the user, check is required, no matter how small the amount is.

This is usually resolved by providing a valid ID, which can be a national ID (if written in a language we understand) or a passport, driver's license, etc.


Now, as soon as you submit a valid ID I'll be happy to have your account active again, however until then there is unfortunately nothing we can legally do (You could ask your bank to reverse the funds sent through Dwolla, however).

Oops, we'll fix this right now, thanks for the report.

Sorry, I guess we forgot some info while putting this document together.

We'll include this information for the next time. Note also that unlike bank operations, bitcoins are handled in realtime and there are many more operations in one month. Also, since people may send bitcoins to themselves, as many times as they want, this data may not be really useful.

I'm not sure lots of people would want to pay for a script as simple as detecting any occurrence of a string starting with MTGOX- with the right length (and if you went far enough, with the SHA256 matching) and just calling our API to try to redeem it, plus if this becomes widespread we may add a throttle on failed attempts here too.

Hi,

For any wire inquiry for transfers sent to us, please ask your bank to provide a copy of the SWIFT transaction (or if not possible, a receipt showing all the data including transaction ID, intermediate bank, target bank, etc).

Wire transfers are usually credited instantly, however US holidays have a global impact on SWIFT transfers (the Martin Luther King holiday caused almost all bank transfers on that period to be delayed) and local holidays may too depending on which of our banks you sent to.


Mark

Unfortunately I cannot give much details on this part, however I can confirm the risk of false positive is really low.
One of the common points between all the blocked accounts so far is that when we contact the owner of the account by email, we never get any reply.

Just for information, we have until now shut down only a couple of accounts for stolen bitcoins, after confirming whoever stole the coins was indeed the owner of those accounts and confirming with law enforcement agencies in charge. There have been no suspended accounts for stolen bitcoins in the past 3 months.

I cannot give much details on the "tainting" process, however before coins are marked tainted, we need an official police report, and we need access to proof the coins were stolen. A simple government decision (let's say, to take something likely, "hey, let's taint wikileaks") would not be enough to cause the coins to be considered stolen, even if it comes from a Japanese court (we can refuse if no proof is given to us that there is indeed an illegal acquisition of coins).

There have been recently, however, moves of stolen coins we were tracking. It caused a few accounts to be temporarily suspended, and after investigation all those accounts were unblocked.


With time, the Bitcoin community is becoming better at protecting itself, with reports of stolen coins being less numerous each month. This is a good thing, and maybe means there won't be a need for this kind of system much longer.


There are two reasons why we do this. One is because it seems wrong to us to be allowing bad guys to steal from new bitcoin users who are not expert enough to protect their own computers. The other reason is because we are a legal entity, and we cannot ignore the law. While we can challenge requests for tracking as being unlawful (if, for example, we were ever required to follow coins for - say - wikileaks), refusing all requests would mean we are encouraging theft and become active part of a crime.


Now, if you could give us a ticket number with your inquiry if your account is "still blocked", we can look it up and confirm with you, however if you lose access to your account recently, there are no chances it would be because of tainted coins.

I would guess your server or access location do not have enough bandwidth to download this whole array in 15 seconds.

Change this line:


To:

Btw why is that page loading fine in browsers ?

Come on everyone, you know about http://www.google.com/safebrowsing/report_phish/ right ?

Any document that proves you live at the address listed. A recent utility bill usually does the trick. A bank statement wouldn't as banks are not required to check you live where you get those sent. The registered address on an ID card wouldn't do either as most countries do not require you to update it if you move to somewhere else.

Being the biggest and top bitcoin exchange does not give us the privilege to go against the law, either. We are trying our best to have bitcoin recognized legally in various parts of the world, and this can only happen by staying in line with the law.

Now, the only case in which we block an account again after an ID has been submitted is when that ID comes back negative from the verification team. This could be either due to the fact the scan was of too low quality, or other reasons. In that case a police investigation is opened to allow a check against the actual ID database of the issuing country or state. This takes time (depending on the country) and submitting a notarized ID can help make things faster.

Anyway posting on the forums without any way to identify you makes it difficult to know exactly what the case is.

It seems that based on your explanation you have installed some kind of spyware or virus.

I would recommend you to install an antivirus software (a real one) on your computer as soon as possible.

Our website requires no soft of extra software. A simple web browser should do.

Due to an ongoing criminal investigation directly related to your account, we are unable to provide any details at this point. You'll receive an update once more information are required or if the investigation ends.

Just let me know how long it takes for you to get an answer from us, when you email info@mtgox.com.

As for Paxum, I've talked a couple of time with Ruth, who said maybe we'd be able to get a different account to send wires to, but we never had any update since then.

1. We already do the Base58 checksum. The only issue - I guess - is the fact we fall back to SHA256 if the checksum does not verify. For your "mini private key format" checksum I'll have to check the doc and see how it works.

2. That shouldn't be an issue, could you show me a couple of those (you got my email) with the required computation and we'll implement it.