shtylman, where physically are you for service of process?
https://bitfloor.com/aboutMailing Address Bitfloor Inc. 27-29 W 60th St. #21053 New York, NY 10023
Roman recently had traveled or moved possibly out of the country (London ?).
|
|
|
Unless you have gotten legal advice to the contrary (if you have please let us know), I would advise processing ACH withdrawals on a as needed basis.
If BitFloor is insolvent, unable to meet all withdrawal request of all customers, then disbursing even one penny is a criminal act.
|
|
|
I have put the website back online for users who have USD to request a withdrawal via ACH. If you choose to leave your USD funds in the account they will be available for trading once it resumes. I hope to resume trading later in the week.
If you had outstanding orders they have all been cancelled.
Once trading resumes, I hope to be able to start repaying BTC losses using the proceeds from fees. More information about this will be provided later.
Who will cooperate in filing an injunction? shtylman, where physically are you for service of process?
|
|
|
I give shtylman props for being upfront about the theft rather than dither about it as some places have.
He sent out an e-mail less than 24 hours ago about API keys being compromised, and asserted that "No accounts were compromised financially nor was there any access to coins or any funds." - http://bitcointalk.org/index.php?topic=105079.msg1159003#msg1159003That could have been an initial attempt to communicate based on a misunderstanding of the actual situation but there was no further communication until this announcement.
|
|
|
Disbursing funds to some customers and not others would be a criminal act under those.
I believe a court order (injunction) should be filed to help ensure the exchange operator proceeds as prescribed by law.
Bitcoins were stolen, not cash. That cash is not Bitfloors to distribute to other customers. It's mine. Doesn't work that way in the U.S. A quick search and I couldn't find the exact description about how customer funds are pooled (giving a net balance), regardless if the account had a balance of securities or cash, then disbursed. Here's from Canada, which is pretty much the same in the U.S. The customer pool fund includes all securities owned by a bankrupt securities firm, and all securities and cash held by or for the account of both the securities firm and every customer of the securities firm, other than customer name securities. The customer pool fund is allocated first to cover the costs of administering the bankrupt estate and then to cover customer claims in proportion to each customers net equity position. -- http://www.cipf.ca/Public/FAQ/Coverage/PartXII.aspx
|
|
|
You repay any USD-deposits, since they are all in tact.
You then re-pay what you can of the remaining BTC deposits.
Customer assets are customer assets. It doesn't matter if they are dollars, bitcoins or bananas. If BitFloor does not have reserves (and that was reported in OP) or any other way to make customers whole, then this is a bankruptcy case. This exchange is operating in the U.S., there are very specific laws as to how to proceed. Disbursing funds to some customers and not others would be a criminal act under those. I believe a court order (injunction) should be filed to help ensure the exchange operator proceeds as prescribed by law. [Edited, s/funds/assets/. and added.]
|
|
|
Apparently, that was not the truth. Now the operator of BitFloor claims the wallet has been compromised and all BTC funds stolen: No coins were kept in cold storage, and all coins from the hot wallet are now spent. As a last resort, I will be forced to fully shut BitFloor down and initiate account repayment using current available funds. I still have all of the logs for accounts, trades, transfers. I know exactly how much each user currently has in their account for both USD and BTC. No records were lost in this attack.
- http://bitcointalk.org/index.php?topic=105818.0 - http://bitcointalk.org/index.php?topic=105819.0
|
|
|
BitFloor has reported a security breach. No coins were kept in cold storage, and all coins from the hot wallet are now spent. As a last resort, I will be forced to fully shut BitFloor down and initiate account repayment using current available funds. I still have all of the logs for accounts, trades, transfers. I know exactly how much each user currently has in their account for both USD and BTC. No records were lost in this attack.
- http://bitcointalk.org/index.php?topic=105818.0 - http://bitcointalk.org/index.php?topic=105819.0
|
|
|
BitFloor has reported a security breach. No coins were kept in cold storage, and all coins from the hot wallet are now spent. As a last resort, I will be forced to fully shut BitFloor down and initiate account repayment using current available funds. I still have all of the logs for accounts, trades, transfers. I know exactly how much each user currently has in their account for both USD and BTC. No records were lost in this attack.
- http://bitcointalk.org/index.php?topic=105818.0 - http://bitcointalk.org/index.php?topic=105819.0
|
|
|
Any ideas what they want me to do?
That was not really an accurate status change, as it appears as there is not much you can do, Perhaps acknowledging it is all you can do. Perhaps also you can notify them that the URL in the e-mail for current status is invalid. It should be: - https://support.intersango.com/status
|
|
|
The way this scanner works is, if I point it at a QR code and squeeze the trigger, it types whatever's in that code on my computer by pretending to be a USB keyboard.
The Requirements on the site you linked to describes only Windows systems. Just to ensure that I am understanding this correctly. This works no different from a USB keyboard. So this should work from any computer, tablet, etc, that can handle a USB keyboard and this simply works like there is a second keyboard that is plugged in. There are no drivers necessary for nearly any operating system released in the past decade or so. All that is needed is an open USB port on the computing device (or port on a USB hub connected to the device). Does that accurately describe how this is used?
|
|
|
Some information would be nice shtylman! Especially given your recent email about potential compromise of the API.
Even if it is a quick one liner some communication would be reassuring for those of us with funds on your exchange.
I didn't get an e-mail but I hadn't been using the API so, I presume, then had no API keys assigned for my account. Having a separate status page for these notifications would be nice, and that need was acknowledged just a few days ago in a different thread: Going forward I will be looking at using multiple data center locations and/or a separate status page to indicate the current situation and not keep you (our users) in the dark about what is going on. Our goal is to be as fault tolerant with our systems as possible and I will be evaluating how to make that happen as we continue to grow.
|
|
|
I see it as a fee to get me together with potential traders. To build up my decentralized net of traders so to say. If I wanted to trade quickly I would put them all BCC and ask, who wants to trade.
GroupMe lets you have a group that an individual can opt-in and opt-out for receiving messages. As a mobile app or just straight SMS text. - https://groupme.comI've used it before and was thinking it would be perfect for a local group of Bitcoiners who trade.
|
|
|
If this is a double spend issue is it possible to get my coins back using pywallet,
If there are unspent funds for any addresses, you can transfer those keys to a new wallet, rescan, and the funds will show and can be spent. You don't need pywallet for doing this, standard bitcoind has everything you need. Step 1.) Make sure you have a good backup of your existing wallet. Step 2.) Extract keys from existing wallet. - http://bitcoin.stackexchange.com/a/3532/153 (first set of instructions) Step 3.) Close the client, move existing wallet out of the way, and relaunch which creates a new, empt wallet. Step 4.) Import keys - http://bitcoin.stackexchange.com/a/3532/153 (second set of instructions) I don't remember if you need to start the client with -rescan after. It doesn't hurt if you do.
|
|
|
|