DTC Protocol Discussion Forum
- DTC Protocol Discussion Forum |
- Search Board |
- Control Panel |
- View My Posts / Threads |
- Direct Messages
Date/Time: Fri, 29 Nov 2024 17:52:31 +0000
[Locked] - Order types
View Count: 4185
| [2015-08-20 12:47:08] |
| vbmithr - Posts: 204 |
|
I'm trying to bind Bitfinex to DTC. The supported order types for Bitfinex are explained here: https://www.bitfinex.com/pages/features DTC supports: ORDER_TYPE_UNSET, ORDER_TYPE_MARKET, ORDER_TYPE_LIMIT, ORDER_TYPE_STOP, ORDER_TYPE_STOP_LIMIT, ORDER_TYPE_MARKET_IF_TOUCHED. http://www.sierrachart.com/index.php?l=doc/doc_OrderTypes.html In here I see actually more order types than supported by DTC (typically trailing stop). What should I do in order to support all Bitfinex order types ? Cheers, Vincent |
| [2015-08-21 17:41:55] |
| |
|
Trailing stop: A stop order that can be set to execute once the market goes against you by a defined price, called the price difference. Trailing–stop sell orders are used to maximize and protect profit as a stock's price rises and limit losses when its price falls.
We have been hesitant to support this in DTC because there is not a high amount of standardization with the implementation of these order types on the server side. Although we could define a specification for it in the case of DTC. Although, as a rule for reasons which is a whole other discussion, the Sierra Chart charting and trading program would not use this server-side order type under any condition. It can be done, but we think this should be done later when there is more use of the DTC Protocol among Servers and Clients. One problem with trailing stop orders is that the Server would have to send an execution report every time it changes the price of the Trailing Stop. If it does not, the Client will not be aware of price changes. Fill or Kill: This type of order is a limit order that must be filled in its entirety or canceled (killed). The purpose of a fill or kill order is to ensure that a position is entered at a desired price.
This is a time in force: http://dtcprotocol.org/index.php?page=doc/doc_DTCMessageDocumentation.php#TimeInForceEnum One Cancels Other (OCO): This option allows you to place a pair of orders stipulating that if one order is executed fully or partially, then the other order is automatically canceled. An OCO combines a stop order with a limit order. This option allows you to place both take profit and stop loss targets for your position.
This is already supported: http://dtcprotocol.org/index.php?page=doc/doc_DTCMessageDocumentation.php#Messages-SUBMIT_NEW_OCO_ORDER Hidden order: A hidden order is an order which does not appear in the orderbook, and thus doesn't influence other market participants. See the fees page for minimum size and fee applicable.
I believe this is like an iceberg order. We have to look this up in FIX. |
| [2015-08-21 18:48:19] |
| vbmithr - Posts: 204 |
|
Ok, thank you very much for this! I don't care if all order types are not supported by SC, I plan to bind several BTC exchanges anyway, I just wanted to know how correctly map DTC order types to the exchanges' ones. I'm gonna have a closer look at this. |
To post a message in this thread, you need to log in with your Sierra Chart account: