Topic: Bitoption Status Thread - page 2. (Read 7906 times)
THe expired option are now correctly gone from the "my contracts" section, but my funds are still in escrow. I have an extra 4 BTC and $10 being held in escrow compared to what I should, all from freshly expired options.
The expired options aren't gone again.
ah there we go, working now
Hunter, we're back up now; Our register function wasn't smart enough to get past the anti-CSRF stuff we put in.
Sorry about that! Try again.
Sorry about that! Try again.
it won't allow me to register...
"there was some sort of problem. Try again."
sadface.
"there was some sort of problem. Try again."
sadface.
We're back up; our provider seems to have things under control; no notification though. I'm probably on the hunt for better hosting. We'll see.
Makes it hard to trade, all this security / DDOS-ing type stuff! Bad for business..
Makes it hard to trade, all this security / DDOS-ing type stuff! Bad for business..
Update: there's a DDOS attack against our provider and node. Could be due to us, could be something else. More as I get it.
Aww, that sucks. I bet you're the target, I hope it gets solved easily.
Update: there's a DDOS attack against our provider and node. Could be due to us, could be something else. More as I get it.
Yep. We went down 10 minutes ago; I just got notified.
There is some sort of problem with our hosting provider; I've filed a critical level ticket, updates here shortly.
There is some sort of problem with our hosting provider; I've filed a critical level ticket, updates here shortly.
The site is down for me right now, getting a server timeout.
For discussion, I repost our top of thread status here:
Update:
There is an attempt at a CSRF in the wild right now aimed at bitoption.org. It tries to send 20 BTC to an address starting with: 1GEwYPX6..
I reviewed our balance sheets and transaction log; nobody has been hit by this or any other CSRF to my knowledge; I manually reviewed back four days of transaction, and scanned the rest for repeated withdrawal requests to confirm.
That said, someone has clearly posted an image link, likely in these forums, which directs to sendBTC?etc.etc. This image link will not function, and has not been successful against bitoption.
The site is down right this second, I am putting in a few layers of protection against this, and will update when it's in place.
In the interim, if you would like to exercise your contracts, please email me at [email protected] FROM your account email, and I'll manually fill your requests, including withdrawals if you need.
I anticipate a few hours to get this sorted out; there will be a slight impact on API developers as well.
Sorry, this is my bad; I thought about XSS but not CSRF when I implemented the API. My hope is that the damage is limited to a little downtime for you all. More here and in the status thread as it comes!
Update:
There is an attempt at a CSRF in the wild right now aimed at bitoption.org. It tries to send 20 BTC to an address starting with: 1GEwYPX6..
I reviewed our balance sheets and transaction log; nobody has been hit by this or any other CSRF to my knowledge; I manually reviewed back four days of transaction, and scanned the rest for repeated withdrawal requests to confirm.
That said, someone has clearly posted an image link, likely in these forums, which directs to sendBTC?etc.etc. This image link will not function, and has not been successful against bitoption.
The site is down right this second, I am putting in a few layers of protection against this, and will update when it's in place.
In the interim, if you would like to exercise your contracts, please email me at [email protected] FROM your account email, and I'll manually fill your requests, including withdrawals if you need.
I anticipate a few hours to get this sorted out; there will be a slight impact on API developers as well.
Sorry, this is my bad; I thought about XSS but not CSRF when I implemented the API. My hope is that the damage is limited to a little downtime for you all. More here and in the status thread as it comes!
Back up.
Our Site is down while Gox gets back on its feet post-DDOS.
Normally we can function in 'reduced functionality' mode, but the error checking isn't quite good enough to catch the current circumstance.
Updates here as it comes.
Normally we can function in 'reduced functionality' mode, but the error checking isn't quite good enough to catch the current circumstance.
Updates here as it comes.
Ok thanks. I'll keep that in mind as I trade.
Hi Damien,
Welcome!
You need the right currency to exercise, but you could rinse/repeat/cycle if you only have enough to do one at a time; so, exercise one, sell BTC, exercise one (or two), repeat.
We may eventually allow netting, but I need to make sure that the exchange doesn't take on exchange risk doing that.
Enjoy, and happy trading!
Welcome!
You need the right currency to exercise, but you could rinse/repeat/cycle if you only have enough to do one at a time; so, exercise one, sell BTC, exercise one (or two), repeat.
We may eventually allow netting, but I need to make sure that the exchange doesn't take on exchange risk doing that.
Enjoy, and happy trading!
Hello, I sent in 2 btc, and they haven't shown up yet even though there are 8 conformation. I'm not really that worried, but I wanted to report a bug. When I click "balance" I just get a box that says
{"obligations": {"msg": "Obligations includes all written unexercised contracts", "usd": "0", "btc": "0"}, "balances": [["BTC", "0.000000"], ["USD", "0.000000"]]}
I was also wondering, when I exercise a call, do I have to have the USD to buy in my balance or do I get a chance to immediately liquidate the BTC and pay out of that?
EDIT: The bitcoins showed up, thanks. But I could still use an answer about liquidation.
{"obligations": {"msg": "Obligations includes all written unexercised contracts", "usd": "0", "btc": "0"}, "balances": [["BTC", "0.000000"], ["USD", "0.000000"]]}
I was also wondering, when I exercise a call, do I have to have the USD to buy in my balance or do I get a chance to immediately liquidate the BTC and pay out of that?
EDIT: The bitcoins showed up, thanks. But I could still use an answer about liquidation.
Thanks for the update. Yes, we rely on Gox, and should have better error messages there. Sorry if it was an untimely difficulty. Kind of a crazy trading day today!
Works now, I figured out that MtGox was down, that's all. Still it should mention the failure. I didn't know if it was no go or slow go or what.
Canceling and Exercising is up and running; login and click "My Contracts."
(Did I really sell $45 july 28 calls a couple days ago? Wow!)
(Did I really sell $45 july 28 calls a couple days ago? Wow!)
Exchanging to USD seems to fail without giving any message.
Canceling and Exercising is up and running; login and click "My Contracts."
(Did I really sell $45 july 28 calls a couple days ago? Wow!)
(Did I really sell $45 july 28 calls a couple days ago? Wow!)
Jump to: