US verified accounts at Bitfinex are frozen and withdrawals are not possible

Reports from yesterday seem to suggest that US verified accounts are frozen and unable to withdraw.

There are suggestions that Bitfinex doing this as a punishment for Synapse Pay not allowing their theft

US verified. All my remaining BitFinex balances are frozen. I can't buy/sell or withdraw anything. They're using SynapsePay as their excuse, but I don't see why they can't quickly (it's been days since everyone else got to resume trading) do one of two things:

1) Reduce our BitFinex balances by the amount Synapse sent us (as of the last settlement 16 hours before the exchange shutdown), even if that makes our USD balances negative. Then allow us to trade but not withdraw until we bring the USD balance out of the red. They're already manually approving all withdrawals, so it shouldn't be hard to check for negative balances

2) Just take from our BTC or other coin balances whatever is necessary to achieve the haircut. This wouldn't be sufficient for customers with only USD, but would enable at least some of us to resume trading.

I am a verified US customer and am not allowed to withdraw with the following notice

Your account is currently restricted from withdrawing because your BitGo wallet is frozen and accurate accounting can not be determined for your balances.

However, I only have $5 in my BitGo wallet (which is not frozen by the way) and mannny more BTC stuck in Bitfinex due to this. Support seems to be ignoring requests about this issue so far and there has been no ETA on a fix.

I was able to withdraw (US custom). No clue if I am verified. Heck, don't even know very well what Bitgo is. Opened an account in 2013, shoved some bitcoin in, and left it until now.

This is why you should not keep your cryptocurrency on exchanges. Make small transactions, less than amount you can afford to lose.

American. Verified. I can't even attempt to withdraw. I instead get this message.

Is anyone else getting this particular message instead of the BitGo message?

I'm also unable to move anything between wallets, and they put all my funds in my margin wallet, which is still disabled for US customers. Guess I'll just hodl this BFXCoin . . .

Comments

Post a Comment

Popular posts from this blog

Do not use (only) flash memory (SSD drives, hardware wallets, USB flash drives) for your precious private keys!

Image
Flash memory is not a reliable medium for archives. Especially when there is no regular power. I have personal experience with usb flash drive not powered for weeks - one file became corrupted . (Read more here: Archiving private keys - TLDR version. ) You should always back up on paper and other mediums. Flash memory is prone to failure if it is not powered for weeks or more and if there are ionizing radiation When you write your precious private keys you should use technologies like Parchive and ZFS . And make several copies of your files. It's OK if you use your USB flash drive for another backup, but don't rely on it! Always back up on DVDs (even small files!), paper and online (after encryption with CPU and RAM intensive key derivative function like scrypt). Here is example of using the scrypt utility: $ sudo apt-get install scrypt $ scrypt enc -M 1073741824 -t 200 secret.txt encrypted.scrypt Do not use default values of "-M" and "-t", they...
Read more

Archiving private keys - TLDR version

0. Make multiple encrypted copies. On DVDs (they are better than CDs and Blu-Ray discs; DVD+R are better than DVD-R), paper, cloud services like DropBox, OneDrive, Google Drive, e-mail it to yourself and to your friends, use P2P storage services like MaidSafe, Storj and Sia , etc. 1. Use proper font when printing PGP encrypted keys on paper. 2. Flash memory (SSD, USB flash drives, hardware wallets) is less reliable when not powered regularly (i.e. every week). 3. Use error correction methods like Parchive and ZFS. 4. Print on paper or store on digital media only encrypted data. 5. Your encryption software should use CPU/RAM-intensive KDF (i.e. scrypt with secure options - do not use defaults! ). First, encrypt with scrypt and then encrypt it again with PGP (using different password!) in ASCII armor mode before print it (other methods like QR codes may not be reliable as multiple copies of the PGP ASCII armor). Do not use the same password for the PGP because it's easy to brute...
Read more
[ad removed]