Exchange Traded Options Strategies

, ,
1

Imported from previous forum

2

Hello,

If I wanted to develop an exchange for options strategies, so you could buy and sell butterflys, straddles, etc. would I have participants use NewOrderSingle or NewOrderMultileg to trade my instruments? I’m going to return a SecurityList with a separate security for each options strategy I want to make a market for, so all the participant will have to specify is the contract (security id) and the price and the side. It doesn’t seem right to have them submit a NewOrderMultileg when they aren’t going to be specifying any leg information. Having said that, it doesn’t seem entirely correct to refer to a butterfly as a NewOrderSingle. Any help would be appreciated.

Regards,

3

I think my message is a bit of a mess. Paragraphs are your friend. Too bad there is no edit option on this fine message board :wink:

Let’s say you are going to build a trading platform. The instruments will be equity calendar spreads. There will be 6 stocks and for each stock there will be 8 different spreads offered.

Now I have 48 instruments, each of which represents a multileg strategy. But I’m going to return to the participants in my market a list of securities like this aapl_buy_jan200_call_sell_dec200_call, etc.

So my question is, when I ask participants to place orders in my market, should they send a NewOrderSingle or a NewOrderMultileg?

Thanks!

4

I believe that a New Order – Single is the appropriate message in this particular context. We offer such multi-legged instruments in our trading platform and participants submit orders for them using the New Order – Single message. I believe the same applies for other platforms (e.g. CME).

I think my message is a bit of a mess. Paragraphs are your friend. Too
bad there is no edit option on this fine message board :wink:

Let’s say you are going to build a trading platform. The instruments
will be equity calendar spreads. There will be 6 stocks and for each
stock there will be 8 different spreads offered.

Now I have 48 instruments, each of which represents a multileg strategy.
But I’m going to return to the participants in my market a list of
securities like this aapl_buy_jan200_call_sell_dec200_call, etc.

So my question is, when I ask participants to place orders in my market,
should they send a NewOrderSingle or a NewOrderMultileg?

Thanks!

5

I agree that NewOrderSingle is the right choice IF(!) you never need to specify leg information. Such leg information not always relates to the definition of the instrument but e.g. to clearing information. Examples are the position effect (564) of a leg or different clearing accounts (NestedPartyID group) to be used for each leg. These fields are part of LegOrdGrp but outside of InstrumentLeg group. The latter is to define a multileg instrument.

Definitions like the side or ratio of a leg would not be in your NewOrderXXX message but be part of your SecurityDefinition messages and covered by the single SecurityID value.

In the absence of SecurityDefinition messages, you would need NewOrderMultileg as the user then has to explicitly describe the instrument everytime he enters an order. For that he would use the InstrumentLeg group within LegOrdGrp.

Regards,
Hanno.

I think my message is a bit of a mess. Paragraphs are your friend. Too
bad there is no edit option on this fine message board :wink:

Let’s say you are going to build a trading platform. The instruments
will be equity calendar spreads. There will be 6 stocks and for each
stock there will be 8 different spreads offered.

Now I have 48 instruments, each of which represents a multileg strategy.
But I’m going to return to the participants in my market a list of
securities like this aapl_buy_jan200_call_sell_dec200_call, etc.

So my question is, when I ask participants to place orders in my market,
should they send a NewOrderSingle or a NewOrderMultileg?

Thanks!

6

Thank you gentlemen. In terms of instrument creation I was planning to use MsgType<35>=c SecurityDefinitionRequest to handle participant requests for new strategies. I’m not sure about clearing information so I will look further into ‘position effect (564)’. Thanks again for your helpful suggestions.

Cheers.

I agree that NewOrderSingle is the right choice IF(!) you never need to
specify leg information. Such leg information not always relates to the
definition of the instrument but e.g. to clearing information. Examples
are the position effect (564) of a leg or different clearing accounts
(NestedPartyID group) to be used for each leg. These fields are part of
LegOrdGrp but outside of InstrumentLeg group. The latter is to define a
multileg instrument.

Definitions like the side or ratio of a leg would not be in your
NewOrderXXX message but be part of your SecurityDefinition messages and
covered by the single SecurityID value.

In the absence of SecurityDefinition messages, you would need
NewOrderMultileg as the user then has to explicitly describe the
instrument everytime he enters an order. For that he would use the
InstrumentLeg group within LegOrdGrp.

Regards, Hanno.

I think my message is a bit of a mess. Paragraphs are your friend. Too
bad there is no edit option on this fine message board :wink:

Let’s say you are going to build a trading platform. The instruments
will be equity calendar spreads. There will be 6 stocks and for each
stock there will be 8 different spreads offered.

Now I have 48 instruments, each of which represents a multileg
strategy. But I’m going to return to the participants in my market
a list of securities like this
aapl_buy_jan200_call_sell_dec200_call, etc.

So my question is, when I ask participants to place orders in my
market, should they send a NewOrderSingle or a NewOrderMultileg?

Thanks!