BitFloor bug?

[DannyHamilton]

How can there be a bid for 7.85897 BTC at $99.56 when there are asks at $99.09, $99.10, $99.11, $99.19, $99.20, and $99.40??



This $99.56 bid has been siting there for 10 minutes while bids below it have been getting filled.  What is going on here?  Is this normal behavior and I just don't understand how the market works, or is this a bug?


EDIT:

This was a UI/websocket display bug. At no point was the matching engine actually in a crossed state.

EDIT: As of 2013-04-17 BitFloor has ceased all operations.

[1714058904]

1714058904

[1714058904]

1714058904

[whatsgoingon]

Not enough to fill the order....but it should be buying in chunks though.

[DannyHamilton]

So since there isn't enough to fill the order, someone else who places an order at $99.15 gets their order filled?  And the $99.56 just sits there indefinitely?  That doesn't seem right.

I'd have thought that the $99.56 order should have been partially filled.

EDIT:

This was a UI/websocket display bug. At no point was the matching engine actually in a crossed state.

EDIT: As of 2013-04-17 BitFloor has ceased all operations.

[whatsgoingon]

I agree, it should have been partially filled.

[qxzn]

I believe this is a UI bug. Next time you see something like this, try querying the API for the order book and I don't believe you'll see the crossed order.

[shtylman]

This was a UI/websocket display bug. At no point was the matching engine actually in a crossed state.

[DannyHamilton]

This was a UI/websocket display bug. At no point was the matching engine actually in a crossed state.

Thanks for the update. I clarified the subject so as not to mislead others.

Is the display bug fixed?

EDIT: As of 2013-04-17 BitFloor has ceased all operations.

[johnblaze]

this seems to happen all the time, gotta be a visual bug

also happens on clarkmoody bitfloor data