Topic: bitfloor needs your help! - page 14. (Read 177459 times)
This is perhaps irrelevant, I am 100% non techy, when I did try to log in the site seemed to want to connect to some port of mine which I denied, maybe it's just normal & harmless but I don't remember it trying to do this before, pse excuse my newbness of what that may be about or nothing , after it went to 504 timed out.
Using the API, I was able to cancel all of my outstanding orders and withdraw my entire BTC balance. The transaction shows up on BlockChain.info now, so I'd guess it'll confirm.
If this is another hack, they haven't emptied out the wallet yet.
EDIT: It has one confirmation now.
If this is another hack, they haven't emptied out the wallet yet.
EDIT: It has one confirmation now.
5 days ago I applied to enable ACH withdrawals for my account, I sent my bank details & ID, but so far have received no acknowledgement or response, I haven't deposited any funds as yet or started trading as I wanted this to be in place first - along with smooth running of the site & evidence that all would now be likely well to trust funds here, also site is down for me.
7:31 pm East Coast US
Can't login
If I ever get back in, all BTC coming out
Can't login
If I ever get back in, all BTC coming out
Bitfloor's web site is having gateway timeout errors now. Repeat attack? Seems similar to the symptoms last time. I'm going to pull out my BTC immediately if it comes back up, just to be safe. I had the opportunity to do that last time, but I didn't. If this actually is a second attack and it's successful, I'm finished with Bitfloor.
Interestingly, the Bitfloor API still appears to be functioning.
To be clear, this appears to be happening upon attempted login. Interestingly, the Bitfloor API still appears to be functioning.
Bitfloor's web site is having gateway timeout errors now. Repeat attack? Seems similar to the symptoms last time. I'm going to pull out my BTC immediately if it comes back up, just to be safe. I had the opportunity to do that last time, but I didn't. If this actually is a second attack and it's successful, I'm finished with Bitfloor.
Interestingly, the Bitfloor API still appears to be functioning.
Interestingly, the Bitfloor API still appears to be functioning.
Bitfloor has indeed resumed trading. My official statement on the matter is here:
https://plus.google.com/109620439233076225324/posts/bLJRDHApjSP
More generally https://blog.bitfloor.com will contain official updates.
If you have specific questions please contact [email protected] and I will gladly respond.
https://plus.google.com/109620439233076225324/posts/bLJRDHApjSP
More generally https://blog.bitfloor.com will contain official updates.
If you have specific questions please contact [email protected] and I will gladly respond.
Any reasonable way for you to prove these claims? Or someway for users to verify these claims themselves (this would be even better)
..."In reopening, a number of improvements to both the wallet storage and website have been made. Bitfloor aims to be safe and reliable platform and as a result have changed our fund storage policy to 100% offline storage for your funds. Daily transactions through out hot wallet will be backed by Bitfloor funds, never putting client funds at risk."...
..."Bitfloor is now running on dedicated servers in a PCI compliant data center based in the US. Bitfloor services are further isolated based on exposure. Testnet and development are not located in the same data center or hosting provider to ensure further isolation. Backups are encrypted and write only on all of the servers. Hot wallet files are encrypted even further and unavailable even with physical access to the disk."...
Bitfloor has indeed resumed trading. My official statement on the matter is here:
https://plus.google.com/109620439233076225324/posts/bLJRDHApjSP
https://plus.google.com/109620439233076225324/posts/bLJRDHApjSP
I have concerns about the new API, but this thread has enough traffic already:
https://bitcointalksearch.org/topic/m.1212462
I haven't used bitfloor as yet but once it is running smoothly & generating fees to help repay the stolen coins then I definitely plan on switching some business to there especially if/once there is outside investment & expertise being added.
I get this message trying to withdraw my BTC.
oops! something went wrong
We have been notified and will look into the issue.
oops! something went wrong
We have been notified and will look into the issue.
Given the fact that all customer deposits of BTC are now held in an offline (cold) wallet, and the online (hot) wallet contains only Roman's own funds with which to fulfill BTC withdrawals, it's likely that the online wallet has bottomed out. Perhaps a lot of users who had USD still sitting on the exchange when it reopened decided to buy BTC and withdraw it. That would have put a strain on the online wallet. Roman will have to refill it from the offline wallet.
The error message could be better.
oops! something went wrong
We have been notified and will look into the issue.
This was my fault 100%
Once I filled out the withdraw page correctly the withdraw was processed immediately.
+1 for TangibleCryptography dept repayment input.
While the TheBitman debt was a fraction of the current Bitfloor debt, TC's input and effort in arranging and handling payment for all the creditors equitably was instrumental in creating a successful result for all involved.
shtylman, while I'm not suggesting TC handl your dept, it would be wise to at lease consider TC's input. I think it also bodes well for us all when the community can work together to solve these problems.
While the TheBitman debt was a fraction of the current Bitfloor debt, TC's input and effort in arranging and handling payment for all the creditors equitably was instrumental in creating a successful result for all involved.
shtylman, while I'm not suggesting TC handl your dept, it would be wise to at lease consider TC's input. I think it also bodes well for us all when the community can work together to solve these problems.
My understanding from Roman prior statements is that debt repayment is being done on a share basis. i.e. if 24,000 BTC are owed and Bitfloor makes a repayment of 1,000 BTC then all creditors would be repaid 4.17% of their balance (1,000 / 24,000). Given that we are owed 200 of ~24,000 BTC our account should receive roughly 0.83% of each payments made. Roman it would be useful to know the exact amount owed all BTC creditors.
A shared repayment is the only equitable arrangement. Paying creditors in a preferential order would imply some debt is senior to others, and no such seniority exists. When TheBitMan asks our company to facilitate repayment of his creditors we repaid each creditor their % share of the total amount owed. It is the same method a court of law would use to handle repayment under say Chapter 13 bankruptcy.
A shared repayment is the only equitable arrangement. Paying creditors in a preferential order would imply some debt is senior to others, and no such seniority exists. When TheBitMan asks our company to facilitate repayment of his creditors we repaid each creditor their % share of the total amount owed. It is the same method a court of law would use to handle repayment under say Chapter 13 bankruptcy.
Sell bitfloor BTC debt to improve liquidity:
https://bitcointalksearch.org/topic/sold-wts-200-btc-debt-owed-by-bitfloor-inc-111918
https://bitcointalksearch.org/topic/sold-wts-200-btc-debt-owed-by-bitfloor-inc-111918
Just posted an offer in that thread.
Whether or not debt resale occurs, a recommendation:
An order of restitution should be clearly defined, e.g. "by account number of original debtholder, in numerical order" (random/fair) or "by account, sorted in descending order by size of debt" (big first, encouraging sale of this debt) or "smallest debt first" (help the little guy) or "by account creation time" (reward early adopters)
This is necessary and prudent if the debt repayment will occur over time, rather than all at once. Necessarily, reality dictates that some must wait longer than ones for repayment.
EDIT Nevermind, I see you posted something on G+ about this ("if 5% of the funds are available for repayment then 5% of your original pre-theft balance will be unheld")
Just wanted to say that I would absolutely pay for slightly discounted "on hold" btc if you can set up some kind of secondary exchange.
Me too...On a completely different topic the Bitfloor.com site is down again.
Sell bitfloor BTC debt to improve liquidity:
https://bitcointalksearch.org/topic/sold-wts-200-btc-debt-owed-by-bitfloor-inc-111918
https://bitcointalksearch.org/topic/sold-wts-200-btc-debt-owed-by-bitfloor-inc-111918
Just wanted to say that I would absolutely pay for slightly discounted "on hold" btc if you can set up some kind of secondary exchange.
Bitfloor has indeed resumed trading. My official statement on the matter is here:
https://plus.google.com/109620439233076225324/posts/bLJRDHApjSP
More generally https://blog.bitfloor.com will contain official updates.
If you have specific questions please contact [email protected] and I will gladly respond.
Shtylman,https://plus.google.com/109620439233076225324/posts/bLJRDHApjSP
More generally https://blog.bitfloor.com will contain official updates.
If you have specific questions please contact [email protected] and I will gladly respond.
Any thoughts on creating a secondary market where "on hold" BTC can be bought/sold? I'd be willing to purchase some "on hold" BTC from those who might be in a hurry to cash out if I could get them at an exchange rate that is slightly more favorable than the current rate for BTC that are not "on hold". If you could create a way for these BTC to be identified and traded, then you would allow those customers of yours who have fears or are in urgent need to cash out to transfer the BTC to those who are just hoarding and have no immediate need. This would significantly improve customer satisfaction.
I'd even guess that buyers of "on hold" BTC would be willing to pay a transaction fee to the exchange in the form of "on hold" BTC (which would remove those BTC from the pool of BTC that the exchange would need to repay).
(perhaps I should send this question in an email to ensure Shtylman sees it).
That is an excellent suggestion. Various forms of debt are sold, with varying risks as to whether or not that debt will be repaid. It has value.
Wanted to say that I appreciate the suggestion and have taken it under consideration as a way to handle the stolen fund balances. I think that if done correctly it can be a viable way to shift the burden.
Bitfloor has indeed resumed trading. My official statement on the matter is here:
https://plus.google.com/109620439233076225324/posts/bLJRDHApjSP
More generally https://blog.bitfloor.com will contain official updates.
If you have specific questions please contact [email protected] and I will gladly respond.
Shtylman,https://plus.google.com/109620439233076225324/posts/bLJRDHApjSP
More generally https://blog.bitfloor.com will contain official updates.
If you have specific questions please contact [email protected] and I will gladly respond.
Any thoughts on creating a secondary market where "on hold" BTC can be bought/sold? I'd be willing to purchase some "on hold" BTC from those who might be in a hurry to cash out if I could get them at an exchange rate that is slightly more favorable than the current rate for BTC that are not "on hold". If you could create a way for these BTC to be identified and traded, then you would allow those customers of yours who have fears or are in urgent need to cash out to transfer the BTC to those who are just hoarding and have no immediate need. This would significantly improve customer satisfaction.
I'd even guess that buyers of "on hold" BTC would be willing to pay a transaction fee to the exchange in the form of "on hold" BTC (which would remove those BTC from the pool of BTC that the exchange would need to repay).
(perhaps I should send this question in an email to ensure Shtylman sees it).
That is an excellent suggestion. Various forms of debt are sold, with varying risks as to whether or not that debt will be repaid. It has value.
Jump to: