Quote from: Ichthyo on December 30, 2013, 10:58:27 PM

Quote from: accord01 on December 27, 2013, 02:52:47 AM

Why didn't my stop order work? Had stop in place @ 21 for ltc/usd... it hit as low as 20.8 albeit very briefly, but my stop order never initiated...

Quote from: kitkat007 on December 27, 2013, 11:18:47 AM

It happend to me once or twice. The order book gets messy sometimes I don't know why but maybe because we can't trade and this is all too professional for us.

Kitkat007, please re-read this response again, and try to judge it as an outside observer.
Just a hint: talking this way is very telling about your mentality.

I'd like to add a note regarding that issue of stop orders seemingly not triggered. (I am a user, and not affiliated to Bitfinex in any way) I observed that behaviour multiple times too, and thought there might a be a bug or problem in the engine. But when watching carefully, I couldn't find anything actually to complain.

The point is, matters are far more complicated when you take a close look (as in e.g.: try to implement a trading engine or algorithm).
There is not just "IT" went down. Actually, there are several rates involved.

you can create a rate value function by connecting the price of each deal happening on the platform (and then making that into a continuous function of course)
you can do the same by connecting only the deals done on one of the connected platforms. This function looks entirely different
next, you can use some heuristics and combination with other data, to create for each of the above a bid rate and a ask rate function
and besides all that, you can create similar functions based on the offers currently in the system. The reasoning is that such would be the rate the next buy / sell would happen at
and last but not least, you can (and indeed should) use a heuristic formula to combine all those data into two functions, which could be titled "effective nominal current bid / ask rate".

Note, the last one, this "effective nominal current rate" is what drives the events of the engine. There is no canonical solution for this, and there can't be, since it is at the very core of the specifics of any trading algorithm or trading engine how to build those functions. Also there are somewhat non-deterministic effects involved, since every engine runs at a specific sampling/update interval and only captures data with a certain granularity.

If you look closely, you'll notice that the nominal rate, as displayed in the UI, is often slightly different than what is visible over the API functions as last trade, or what is visible e.g on Bitcoinwisdom (which, as I take it, also pulls the Bitfinex API)

If, after shaving away all those complexities, there remains a situation where the nominal rate is lower than the trigger point of a given stop sell for more than one update period, then this would actually be a bug and I'm sure Bitfinex stuff will be very interested in getting a full documentation of such an incident.

What are you trying to say?