|
Elokane (OP)
|
 |
April 09, 2013, 01:03:55 PM |
|
I was trading yesterday during the short price decrease (from the 194.9 high to 170+), placing various orders and cancelling them over the course of an hour.
At one point I had a specific sell order placed that I later cancelled to continue trading at other prices.
After finishing trading, making sure there is no more trading lag (when things calmed down), making sure all of my sell orders are closed (I had purely BTC at the point), I closed the tab and left the computer.
I received an email about a transaction taking place about 10 minutes afterwards with a ridiculous sum that was irrelevant at that point, from an order that I had cancelled and that did not appear in my order book.
Now I woke up to find that I have dollars instead of BTC and they're worth much less compared to when they were sold.
Has this happened to anyone before on Mt.Gox? Cancelled orders that disappeared from the book being fulfilled?
I am a long time user and I know the issues it has with engine lag, which is why I make absolutely sure that all my orders are actually closed before leaving my computer.
|
|
|
|
|
|
|
|
|
|
|
|
|
It is a common myth that Bitcoin is ruled by a majority of miners. This is not true. Bitcoin miners "vote" on the ordering of transactions, but that's all they do. They can't vote to change the network rules.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
Luno
|
|
April 09, 2013, 01:15:04 PM |
|
Yep, well maybe not exactly like your situation but from personal experience, canceling an order while it executes makes coins go missing! Lost 6 around $7.80 during a crash to the void by canceling a buy order while it was being eaten through.
(Note to Gox: if they showed up as a difference on your daily balance, please return them or send me 1260 bux)
|
|
|
|
|
|
Elokane (OP)
|
|
April 09, 2013, 01:16:45 PM |
|
I cancelled mine long before it executed. More time than the peak engine lag ever experienced on Mt.Gox.
|
|
|
|
|
Elokane (OP)
|
|
April 24, 2013, 08:54:05 AM |
|
They refuse to even check their logs and see.
Sigh.
|
|
|
|
🏰 TradeFortress 🏰
Bitcoin Veteran
VIP
Legendary
 Offline
Activity: 1316
Merit: 1043
👻
|
|
April 24, 2013, 08:57:28 AM |
|
Mt Gox can handle 37 trades per second. Step 1: Create 38 0.01 trades per second Step 2:  Step 3: Gox lag! |
|
|
|
|
Phinnaeus Gage
Legendary
Offline
Activity: 1918
Merit: 1570
Bitcoin: An Idea Worth Spending
|
|
April 24, 2013, 09:12:37 AM |
|
Mt Gox can handle 37 trades per second. Step 1: Create 38 0.01 trades per second Step 2: Step 3: Gox lag! Now that's a new word: Goxlag. |
|
|
|
|
|
greyhawk
|
|
April 24, 2013, 10:33:56 AM |
|
I cancelled mine long before it executed. More time than the peak engine lag ever experienced on Mt.Gox.
Peak engine lag ever was at something like 4 hours, so... |
|
|
|
|
|
Elokane (OP)
|
|
April 24, 2013, 10:35:16 AM |
|
When was that?
Note that this happened before the latest crash.
|
|
|
|
|
greyhawk
|
|
April 24, 2013, 10:38:38 AM |
|
When was that?
Note that this happened before the latest crash.
2, 3 weeks ago or something. I'm losing track of time with all the goxcitement. |
|
|
|
|
|
