Oh there we go.  I knew the slippage goes to fees, but failed to see the matching order.  Thanks.  I figured there was something I was missing.

Quote from: svk on April 24, 2015, 09:08:09 AM
Actually I was wrong, it seems to be simply a question of "You get what you ask for".

I assume you're talking about this:

Code Select Expand

Buy 268.601 BTS/USD 9,224.01 BTS 34.341 USD 0.0000 USD Apr 24, 2015 7:05:10 AM
Short 247.000 BTS/USD 34.341 USD 9,224.01 BTS
Buy 268.601 BTS/USD 244.74 BTS 0.911 USD 0.0000 USD Apr 24, 2015 7:05:10 AM
Short 248.000 BTS/USD 0.911 USD 244.74 BTS

As you can see someone placed a buy order well above the lowest ask, and got matched with shorts at 247 and 248 BTS/USD.

So that buy order just got charged a massive fee of nearly 10%? I thought the system was meant to protect from front-runners, but is it worth the cost?

Actually I was wrong, it seems to be simply a question of "You get what you ask for".

I assume you're talking about this:

Buy 268.601 BTS/USD 9,224.01 BTS 34.341 USD 0.0000 USD Apr 24, 2015 7:05:10 AM
Short 247.000 BTS/USD 34.341 USD 9,224.01 BTS
Buy 268.601 BTS/USD 244.74 BTS 0.911 USD 0.0000 USD Apr 24, 2015 7:05:10 AM
Short 248.000 BTS/USD 0.911 USD 244.74 BTS

As you can see someone placed a buy order well above the lowest ask, and got matched with shorts at 247 and 248 BTS/USD.

"Invisible" cover orders in the old wallet version that happen at feed price + 10% and a bug that doesn't let shorts match cover orders. Fixed in 0.9.0

If you have a short order at 250 bts/usd for 1% and the blockchain order history shows an order just went thru at 268 bts/usd while yours still waits... how the hell does this behavior make sense and can someone explain it to me?