# Patent

## Title
Reprice-to-block order

## Abstract

A reprice-to-block order and related market center and process are disclosed which automatically reprice a posted limit order to the price of a block trade executed at an inferior price on a market away from the market center that posted the limit order.

## Background
CROSS-REFERENCE TO RELATED APPLICATIONS
This application claims priority from and claims the benefit of U.S. Provisional Application No. 60/678,108, filed May 5, 2005, entitled “Reprice-to-Block Order Modifier”, which is hereby incorporated by reference.


BACKGROUND
A block trade is a single large trade in excess of a specific volume and/or a specific market value. The definition of a block trade varies across different financial products. For instance, on the equities market, a block trade has traditionally been defined as a trade of 10,000 shares or more or a trade with a total market value of at least $200,000. In contrast, a block trade on the options market has traditionally been defined as a trade of 500 contracts or more, with a total market value of at least $150,000.
Many studies have been conducted on the impact of large block trades on prices in the marketplace, especially as relates to the equities market. Because block trades are perceived to indicate the trading strategies of large institutional investors, market participants often monitor block trades to determine if the market in a given issue is becoming increasingly bearish or bullish. When the price of a block trade is higher than the best offer in the market at the time, market participants typically interpret this to mean the market direction is moving upward for this issue. Similarly, when the price of a block trade is lower than the best bid at the time, market participants typically interpret this to mean the market direction is moving downward for this issue. The execution of a block trade at a price outside the quotes is deemed so important that some trading workstation systems are configured to automatically trigger an actionable alert every time a block trade executed outside the quotes is detected.
On some markets, block trades outside the quotes are allowed, but only under certain conditions. If no such exception condition exists and a block trade executes outside of the quotes, the offending market center “owes a fill” to the market center that had the better price at the time the block trade was reported to the marketplace. The “satisfaction fill” is typically executed in the following manner. The market center whose quote was traded-through (“the aggrieved market center”) generally sends an electronic message (or satisfaction order) to the market center that traded-through the quotes (“the offending market center”) requesting satisfaction for the orders that were traded-through. When the offending market center fulfills the request for satisfaction by sending the requested number of shares (or contracts) at the block price to the aggrieved market center, the aggrieved market center then is able to adjust the trade price of the orders that were traded-through to be equal to the price of the shares (or contracts) that were part of the block trade. In this manner, the aggrieved market participants receive the price improvement they would have received had the block trade interacted with the public order book.
While this “satisfaction fill” process protects orders that were at the top of the book when the block trade executed, it does not protect orders that were lower down in the book or that had a non-displayed component, such as a reserve order. When a block trade executes at a price worse than the best bid or offer, orders lower down in the book or ones that have a non-displayed component become subject to potential arbitrage. With respect to orders that were not at the top of the book and were not protected, other market participants, seeing these orders, may attempt to promptly execute against these orders and then turn around and trade such instruments on another market center to benefit from the spread created between the price the order was posted at and what may be perceived as the market's more ‘informed’ price, as indicated by the price of the executed block trade. Order types with a non-displayed component, such as reserve orders, are targets for possible arbitrage whether they are at the top of the book or not. Only the displayed portion of a reserve order at the top of the book is eligible for satisfaction at the block trade price. Whenever the displayed portion is depleted by trading, it is replenished at its original price, which is superior to the block trade price. Other market participants will typically attempt to execute against the reserve order at its superior price until it moves away or is depleted.
Accordingly, there is a need for a posted limit order that will reprice itself less aggressively in view of a block trade executing in that issue at a trade price that is inferior to the prices quoted on the posting market center.
SUMMARY
According to an aspect of the present invention, a method for repricing a posted limit order on a posting market center in view of a block trade executed on an away market center at an inferior price includes posting a limit order on a posting market center, receiving data regarding a block trade executed on an away market center, determining that the block trade executed at an inferior price to the limit order posted on the posting market center and automatically repricing the limit order posted on the posting market center to the inferior price that the block trade executed at. The posted limit order may be a buy order or a sell order. The posted limit order may also be a reserve order. The posting market center may operate in an equities marketplace, an options marketplace or any other financial instrument marketplace.



DESCRIPTION OF THE DRAWINGS
These and other features, aspects and advantages of the present invention will become better understood with regard to the following description, appended claims and accompanying drawings where:
FIG. 1 is a block diagram illustrating the trading environment in which an embodiment of the present invention operates;
FIG. 2 is a flow diagram illustrating a process implemented by an embodiment of the present invention for tagging an incoming reprice-to-block buy order;
FIG. 3 is a flow diagram illustrating a process implemented by an embodiment of the present invention to detect and analyze last sale market data;
FIG. 4 is a flow diagram illustrating a process implemented by an embodiment of the present invention to determine if a trade was a block trade;
FIG. 5 is a flow diagram illustrating a process implemented by an embodiment of the present invention to reprice a posted buy order to an executed block trade price;
FIG. 6 is a flow diagram illustrating a process implemented by an embodiment of the present invention for tagging an incoming reprice-to-block sell order; and
FIG. 7 is a flow diagram illustrating a process implemented by an embodiment of the present invention to reprice a posted sell order to an executed block trade price.



DETAILED DESCRIPTION
Referring to FIG. 1, a trading environment in which an embodiment of the system and method of the present invention operates is depicted. The examples discussed herein describe the use and application of the present invention in an equity security market center environment, but it should be understood that the present invention could be used in any type of financial instrument market center environment (e.g., securities, futures, options, bonds, etc.). The trading environment of this embodiment includes a posting market center 20 which interacts with a number of other market centers 24 (i.e. away markets), traders at order sending firms 26, and Market Makers 31. It should be understood that the trading environment of this embodiment supports, but does not require Market Makers 31, a Market Maker Interface 32, or Market Maker Quotes 33. It should also be understood that the posting market center 20 referred to herein refers to a computing system having sufficient processing and memory capabilities and does not refer to a specific physical location. In fact, in certain embodiments, the computing system may be distributed over several physical locations. It should also be understood that any number of traders 26, Market Makers 31 or away market centers 24 can interact with the posting market center 20. The posting market center 20 is the market center on which a specific trader 26 posts a specific order, and on which a specific Market Maker 31 posts a specific quote. The posting market center 20 includes an order matching engine 21, which validates, matches and processes all orders on the posting market center 20. In this embodiment, the code for the order matching engine 21 is stored in the posting market center's memory.
The posting market center 20 may also include a quote and last sale interface 23 that interacts with the away market centers 24 to capture quote and last sale information. This information is stored to a best bids and offers and last sales data structure 25. This data structure 25 is where the market best bid and offer information is stored. This data structure 25 is also where the market trade reports (prints) are stored. The posting market center 20 may also include an order and trade parameters data structure 27. The order and trade parameters data structure 27 stores pre-defined trading parameters and rules that are used by the order matching engine 21 in matching orders and executing trades. The posting market center 20 may also include an order and execution interface 28 which interacts with the traders 26, the Market Makers 31, the away market centers 24 and the order matching engine 21 in the order execution process. The posting market center 20 may also include an order information data structure 29 where order information is stored and a trade information data structure 30 where completed trade information is stored. The posting market center 20 may also include a Market Maker interface 32 that interacts with Market Makers 31 to capture Market Maker bids and offers in assigned issues. These bids and offers are logically depicted in a Market Maker Quotes structure 33 in this illustration. In actuality, the Market Maker bids and offers may physically reside in the away market center best bids and offers data structure 25.
Throughout the discussion herein, it should be understood that the details regarding the operating environment, data structures, and other technological elements surrounding the posting market center 20 are by way of example and that the present invention may be implemented in various differing forms. For example, the data structures referred to herein may be implemented using any appropriate structure, data storage, or retrieval methodology (e.g., local or remote data storage in data bases, tables, internal arrays, etc.). Furthermore, a market center of the type described herein may support any type of suitable interface on any suitable computer system.
Incoming Reprice-to-Block Buy Order
FIG. 2 illustrates the process implemented where a trader 26 sends a buy order to the posting market center 20 with instructions that the buy order be repriced to match the price of any block trade executed at an inferior price (i.e. a reprice-to-block order). At step 100, a new reprice-to-block buy order is received by the order matching engine 21, and the order matching engine 21, recognizing the incoming order processing request, initiates the process which tags the order as a reprice-to-block order. In this embodiment, the process tags a reprice-to-block buy order by setting the reprice-to-block field in the order data structure to “Y”. In this embodiment, a reprice-to-block tag can be attached to any limit order that is displayed in the order book. This tag is especially appropriate to orders having reserve shares (or contracts). For such orders, the reprice-to-block tag applies to all shares (or contracts) in the order, both disclosed and in reserve. However, a reprice-to-block tag is not used with orders that are automatically repriced by other market indicators, such as the best bid or best offer.
At step 102, the process checks to see if the buy order is marketable against the best offers in the marketplace. It should be understood that reprice-to-block orders trade like any other limit order, and trade against the marketplace accordingly. If the buy order is marketable, the process proceeds to step 104 where the order matching engine 21 trades the new buy order against sell orders posted in the posting market center's order book and/or routes to superior away market quotes according to the market center's trading rules. Then, at step 106, the process checks to see if the buy order still has any quantity remaining on the order to be traded. If the buy order does not, then the order is complete, and the process ends with respect to this order, as indicated at step 114. If the order is not complete and still has quantity remaining to be traded, the process proceeds to step 110. Referring back to step 102, if the incoming buy order is not marketable, the process proceeds to step 110 at this point as well.
At step 110, the process sets the “OriginalPrice” parameter equal to the price set in the incoming reprice-to-block buy order. The “OriginalPrice” parameter retains the original order price for later audit purposes. Next, at step 112, the order is inserted into the posting market center's virtual consolidated electronic order and quote book (“internal book”) and displayed on the public order book according to the price/time priority rules. The process terminates at step 114.
Detection of New Last Sale and Repricing of Posted Reprice-to-Block Buy Order in Response to a Block Trade at an Inferior Price
With the tagged reprice-to-block order posted to the order book, the process, in this embodiment, continuously polls the last sale prices from the market-wide “Tape.” The “Tape” refers to the facility that disseminates continuous trade information for a given symbol to the entire marketplace. For example, trades in exchange-listed securities are reported to the Consolidated Tape, trades in Nasdaq-listed securities are reported to the UTP Trade Data Feed and trades in options are reported to the Options Price Reporting Authority. In this document, the term “Tape” is not limited to these facilities, and may include additional facilities that disseminate last sale information for other issues.
In this embodiment, the process instituted by the order matching engine 21 reads all trades printed on the away markets for various reasons, including, most pertinent to this invention, the need to determine if the away market trade printed at a price outside the posting market center best bid or offer, and if so, if the trade was a block trade. In this embodiment, if the process detects a block trade outside the posting market center's best bid or offer, the process checks the posting market center's order book to determine if any posted orders in the traded symbol carry a reprice-to-block tag.
Specifically, referring to FIG. 3, the process at step 120 detects a new last sale on the Tape. At step 122, the process determines whether the trade executed on the posting market center 20. If it did, then the process ends, as indicated at step 126. If the trade did not execute on the posting market center 20, the process proceeds to step 124 where it determines whether the trade was a regular-way trade. A regular-way trade is a trade without any stated conditions attached. Reprice-to-block orders are not re-priced if the trade is not a regular-way trade because such block trades are typically not indicative of current conditions in the marketplace. Examples of trades that are not regular-way trades because they have conditions attached are trades that are reported late after other prints have occurred (e.g., sold sales), trades that occur outside of normal market hours (e.g., opening and closing trades, prior day trades, next day trades) or trades that have special delivery or sale conditions attached. The preceding types of trades do not cause reprice-to-block orders to be repriced.
If the process determines that the trade was not a regular-way trade, the process ends as indicated at 126. If the process determines that the trade was a regular-way trade, the process proceeds to step 128 where the “PrintTradeVolume” parameter is set equal to the size of the trade. The process then proceeds to step 130 where it sets the “PrintTradePrice” parameter equal to the price of the trade.
Next, at steps 132, 134 and 142, the process retrieves the posting market center's best bid and offer price and compares these prices to the stored “PrintTradePrice” value. At step 134, the process determines whether the “PrintTradePrice” parameter value is lower than the posting market center's best bid. If it is determined that the “PrintTradePrice” parameter value is lower than the posting market center's best bid, the process proceeds to step 136 where it executes a routine to determine if the trade was a block trade. If, at step 134, the process determines that the “PrintTradePrice” parameter is not lower than the best bid posted on the posting market center 20, the process proceeds to step 142. At step 142, the process determines whether the “PrintTradePrice” parameter value is higher than the posting market center's best offer. If it is determined that the “PrintTradePrice” parameter value is higher than the posting market center's best offer, the process proceeds to step 146 where it executes a routine to determine if the trade was a block trade, as it did at step 136. If, at step 142, the process determines that the “PrintTradePrice” parameter value is not higher than the posting market center's best offer, then the process ends as indicated at step 144.
At steps 138 and 148, after the block trade determination process, as explained below, has been run and if the binary value of the “IsBlock” parameter equals “1” (true), meaning the trade was a block trade, then the process proceeds to implement processes for repricing either the applicable buy order (step 140) or applicable sell order (step 150) in view of the executed block trade.
Referring to FIG. 4, the block trade determination process 160, referred to at steps 136 and 146 above, executes as follows in this embodiment. At step 162, the process retrieves the “MinBlockVolume” parameter which is set to the minimum number of shares (or contracts) that the trade must include to be considered a block trade. At step 164, the process determines whether the “MinBlockVolume” parameter is greater than the “PrintTradeVolume” parameter value. In this embodiment, if the “MinBlockVolume” parameter is not greater than the “PrintTradeVolume” parameter, the trade has to be further analyzed to determine if it is a block trade or not, according to applicable market rules. The process, then, at this point, proceeds to step 165, where the process determines whether the trade must also meet a minimum value requirement, in addition to meeting a minimum volume requirement, to be considered a block trade, according to applicable market rules. For instance, the options market defines a block trade as a trade that meets a minimum volume requirement and a minimum marketplace value requirement. Referring back to step 164 again, if the process, on the other hand, determines that the “MinBlockVolume” parameter is greater than the “PrintTradeVolume” parameter, the trade does not meet the volume definition of a block trade. However, that does not mean it is definitely not a block trade because it still might satisfy the trade value criteria for a block trade, which is analyzed starting at step 166. Specifically, the equities marketplace requires that for a trade to be considered a block trade, it must meet either a minimum volume requirement or a minimum marketplace value requirement. This is in contrast to the options marketplace explained above, which requires both criteria to be satisfied.
Referring again to step 165, if the process determines that the trade does not need to meet a minimum value requirement, in addition to meeting a minimum volume requirement, to be considered a block trade (as in the equities market), then the trade is a block trade and the parameter “IsBlock” in this example is set to “1” or true, as indicated at 174. If on the other hand, the trade must also meet a minimum market value requirement, such as in the options market, the process proceeds to step 166.
At step 166, the process retrieves the “MinBlockValue” parameter which is set to the minimum monetary value that the trade must execute at to be considered a block trade. At step 168, the process computes the value of the reported trade and stores it as the “TotalTradeValue” parameter. The “TotalTradeValue” parameter is equal to the volume of the print trade (i.e. “PrintTradeVolume”) multiplied by the price of the print trade (i.e. “PrintTradePrice”). The process then, at step 170, determines whether the “MinBlockValue” parameter is greater than the “TotalTradeValue” parameter. In this embodiment, if the “MinBlockValue” parameter is not greater than the “TotalTradeValue” parameter, the trade is a block trade, and the parameter “IsBlock” is set to “1” or true, as indicated at 174. If the “MinBlockValue” parameter is greater than the “TotalTradeValue” parameter, then the print trade is not a block trade and the “IsBlock” parameter is set to “0” or false, as indicated at 172. As indicated at steps 176 and 178, the value of the “IsBlock” parameter is passed to the process at steps 138 and 148 (FIG. 3).
Referring back to FIG. 3, at steps 138 and 148, the process determines if the “IsBlock” parameter equals “1”. If the “IsBlock” does not equal “1”, the process ends as indicated at 144. If the “IsBlock” parameter does equal “1”, the routine for repricing either a posted buy order (step 140) or a posted sell order (step 150) is initiated.
Referring to FIG. 5, the process to reprice a posted buy order to the block trade price is illustrated at step 200. At step 202, the process retrieves a buy order with a reprice-to-block buy order tag set to “Y”. At step 204, the process then determines whether the retrieved buy order price is higher than the “PrintTradePrice” parameter. If it is, the process reprices the buy order and sets the buy order price equal to the “PrintTradePrice” parameter value and then inserts the repriced buy order into the posting market center's internal order book and the public order book according to its new price/time priority, as indicated at steps 206 and 208. The process then proceeds to determine if there are any further buy orders tagged to be repriced at step 210. At step 210, if the process determines that there are further buy orders tagged to be repriced, the process returns to step 202 to repeat the posted buy order repricing process over again. If there are no further buy orders tagged to be repriced, the process terminates as indicated at step 212. The process also proceeds to step 212 if the buy order retrieved and checked at steps 202 and 204 does not have a price that is higher than the “PrintTradePrice” value.
Incoming Reprice-to-Block Sell Order
Referring to FIG. 6, the process for tagging and handling an incoming reprice-to-block sell order is very similar to the process described above for reprice-to-block buy orders. At step 300, a new reprice-to-block sell order is received by the order matching engine 21, and the order matching engine 21, recognizing the incoming order processing request, initiates the process which tags the order as a reprice-to-block order. As with the reprice-to-block buy orders described above, the process tags a reprice-to-block sell order by setting the reprice-to-block field in the order data structure to “Y”. At step 302, the process checks to see if the sell order is marketable against the best bids in the marketplace. If the sell order is marketable, the process proceeds to step 304 where it trades the new sell order against buy orders posted in the posting market center's order book and/or routes to superior away market quotes according to the market center's trading rules. Then, at step 306, the process checks to see if the sell order still has any quantity remaining on the order to be traded. If the sell order does not, then the order is complete, and the process ends with respect to this order, as indicated at step 314. If the order is not complete and still has quantity remaining to be traded, the process proceeds to step 310. Referring back to step 302, if the incoming sell order is not marketable, the process proceeds to step 310 at this point as well.
At step 310, the process sets the “OriginalPrice” parameter equal to the price set in the incoming reprice-to-block sell order. Next, at step 312, the order is inserted into the posting market center's internal order book and displayed on the public order book according to the price/time priority rules. The process terminates at step 314.
Repricing a Reprice-to-Block Sell Order
Referring to FIG. 7, the process to reprice a posted sell order to the block trade price is very similar to the process of repricing a reprice-to-block buy order described above and is illustrated starting at step 400. At step 402, the process retrieves a sell order with a reprice-to-block sell order tag set to “Y”. At step 404, the process then determines whether the retrieved sell order price is lower than the “PrintTradePrice” parameter. If it is, the process reprices the sell order and sets the sell order price equal to the “PrintTradePrice” parameter value and then inserts the repriced sell order into the posting market center's internal order book and the public order book according to its new price/time priority, as indicated at steps 406 and 408. The process then proceeds to determine if there are any further sell orders tagged to be repriced at step 410. At step 410, if the process determines that there are further sell orders tagged to be repriced, the process returns to step 402 to repeat the posted sell order repricing process over again. If there are no further sell orders tagged to be repriced, the process terminates as indicated at step 412. The process also proceeds to step 412 if the sell order retrieved and checked at steps 402 and 404 does not have a price that is lower than the “PrintTradePrice” value.
Examples of how tagged reprice-to-block orders operate are provided below. It should be understood that the order and quote prices and sizes, as well as Print prices, discussed in these examples are by way of example only to illustrate how the process of an embodiment of the invention handles repricing a tagged order to an executed block trade price.
EXAMPLE 1
Receipt of Reprice-to-Block Buy Orders
At the start of the examples that follow, the internal order book of a posting market center appears as indicated. The issue used in this example is an equity security. The best bid and offer from an away market 24a is also shown included in the internal book in these examples. The posting market center 20 in this example is at the best bid with 11,000 at $20.02 and is also at the best offer with 5000 at $20.03. Away Market Center A is bidding 2000 at $20.00 and offering 1000 at $20.03. The internal book looks like this:











Bids
Offers


















Order A:
11,000 @ 20.02
Order C:
5000 @ 20.03


Order B:
  3000 @ 20.01,
Away Market
1000 @ 20.03




Center A


Reserve size =


2000


Away Market
  2000 @ 20.00
Order D:
1000 @ 20.05


Center A









The public posting market center book looks like this:











Bids
Offers


















Posting Market
11,000 @ 20.02
Posting Market
5000 @ 20.03


Center

Center


Posting Market
  3000 @ 20.01
Posting Market
1000 @ 20.05


Center

Center









At step 100, the process receives the following incoming reprice-to-block buy order:

    
    
        →Order E: Buy 5000 @ 20.02, Show size=400, Reserve size=4600, RTB=Yes
    
    


At step 102, the process determines that Order E is not marketable, as there is no overlap between the buy order price and the best offer price. At step 110, it stores the order price as the OriginalPrice for audit purposes, and at step 112, it posts the reprice-to-block order to the internal book and public posting market center book according to normal price/time priority rules. The process terminates at step 114.
The internal book looks like this:











Bids
Offers


















Order A:
11,000 @ 20.02
Order C:
5000 @ 20.03


Order E:
  400 @ 20.02,  
Away Market
1000 @ 20.03




Center A


Reserve size =


4600,


OriginalPrice =


20.02,


RTB = Y


Order B:
  3000 @ 20.01,
Order D:
1000 @ 20.05


Reserve size =


2000


Away Market
  2000 @ 20.00


Center A









The public posting market center book looks like this:











Bids
Offers


















Posting Market
11,400 @ 20.02
Posting Market
5000 @ 20.03


Center

Center


Posting Market
  3000 @ 20.01
Posting Market
1000 @ 20.05


Center

Center









In this example, the posting market center 20 receives the following reprice-to-block buy order at step 100:

    
    
        →Order F: Buy 2000 @ 20.01, Show size=900, Reserve size=1100, RTB=Yes
    
    


At step 102, the process determines that Order F is not marketable, as there is no overlap between the buy order price and the best offer price. At step 110, it stores the order price as the OriginalPrice for audit purposes, and in step 112 it posts the reprice-to-block order to the internal book and the public posting market center order book according to normal price/time priority rules. The process terminates at step 114.
The internal book looks like this:











Bids
Offers


















Order A:
11,000 @ 20.02
Order C:
5000 @ 20.03


Order E:
  400 @ 20.02,
Away Market
1000 @ 20.03




Center A


Reserve size =


4600,


OriginalPrice =


20.02,


RTB = Y


Order B:
  3000 @ 20.01,
Order D:
1000 @ 20.05


Reserve size =


2000


Order F:
  900 @ 20.01,  


Reserve size =


1100,


OriginalPrice =


20.01,


RTB = Y


Away Market
  2000 @ 20.00


Center A









The public posting market center order book looks like this:











Bids
Offers


















Posting Market
11,400 @ 20.02
Posting Market
5000 @ 20.03


Center

Center


Posting Market
  3900 @ 20.01  
Posting Market
1000 @ 20.05


Center

Center









EXAMPLE 2
Block Trade on the Tape is not at an Inferior Price
At step 120, the process detects the following Print (Last Sale) on the Tape:

    
    
        →10,000 shares @ 20.02 traded on Away Market A
    
    


At step 122, the process determines that this trade did not execute on the posting market center 20 (i.e. it is an away market execution), and at step 124, the process determines that this is a regular-way trade. As such, at step 128, the process sets the “PrintTradeVolume” parameter equal to 10,000, the size of the trade. At step 130, the process sets the “PrintTradePrice” parameter equal to $20.02, the price of the trade.
Then, at step 132, the process retrieves the posting market center's best bid and offer and at step 134, the process compares the PrintTradePrice parameter ($20.02) to the posting market center best bid ($20.02). As the PrintTradePrice parameter is not lower than the posting market center best bid, the process does not need to check for the presence of any reprice-to-block buy orders. The process continues to step 142 accordingly.
At step 142, the process compares the PrintTradePrice parameter ($20.02) to the posting market center's best offer ($20.03). As the PrintTradePrice parameter is not higher than the posting market center's best offer, the process does not need to check for the presence of any reprice-to-block sell orders. For this last sale price, the process is complete, as indicated at step 144.
EXAMPLE 3
Trade on the Tape is an Inferior Price, But is not a Block Trade
The internal book still looks like this:











Bids
Offers


















Order A:
11,000 @ 20.02
Order C:
5000 @ 20.03


Order E:
  400 @ 20.02,
Away Market
1000 @ 20.03




Center A


Reserve size =


4600,


OriginalPrice =


20.02,


RTB = Y


Order B:
  3000 @ 20.01,
Order D:
1000 @ 20.05


Reserve size =


2000


Order F:
  900 @ 20.01,


Reserve size =


1100,


OriginalPrice =


20.01,


RTB = Y


Away Market
  2000 @ 20.00


Center A









At step 120, the process detects the following Print on the Tape:

    
    
        →9,500 shares @ 20.01 traded on Away Market A
    
    


At step 122, the process determines that this trade did not execute on the posting market center, and at step 124, the process determines that this is a regular-way trade. At step 128, the process sets the PrintTradeVolume parameter equal to 9,500, the size of the trade. At step 130, the process sets the PrintTradePrice parameter equal to $20.01, the price of the trade.
At step 132, the process retrieves the posting market center's best bid and offer, and at step 134, the process compares the PrintTradePrice parameter ($20.01) to the posting market center's best bid ($20.02). As the PrintTradePrice parameter is lower than the posting market center best bid, the process continues to step 136 and initiates the process to determine if the Last Sale constitutes a block trade at step 160 (FIG. 4).
At step 162, the process retrieves the MinBlockVolume parameter, which, in this example, is presently set to 10,000 shares. At step 164, the process compares the PrintTradeVolume parameter (9,500) to the MinBlockVolume parameter (10,000). As the PrintTradeVolume is less than the MinBlockVolume, the process continues to step 166. At step 166, the process retrieves the MinBlockValue parameter, which is presently set to $200,000.
At step 168, the process computes the TotalTradeValue parameter by multiplying the PrintTradeVolume parameter (9,500) by the PrintTradePrice parameter ($20.01). The derived TotalTradeValue=$190,095. At step 170, the process compares the TotalTradeValue ($190,095) to the MinBlockValue ($200,000). As the TotalTradeValue is less than the MinBlockValue, the process determines that this trade does not constitute a block trade. At step 172, the flag “IsBlock” is set to “0” (false).
At step 176, the process passes the binary value back to step 138 in the process New Last Sale Detected (FIG. 3). As the value of IsBlock=0, no reprice-to-block orders are repriced, and the process ends at step 144 with respect to this last sale.
EXAMPLE 4
Trade on the Tape is not an Away Market Execution
The internal book still looks like this:











Bids
Offers


















Order A:
11,000 @ 20.02
Order C:
5000 @ 20.03


Order E:
  400 @ 20.02,
Away Market
1000 @ 20.03




Center A 


Reserve size =


4600,


OriginalPrice =


20.02,


RTB = Y


Order B:
  3000 @ 20.01,
Order D:
1000 @ 20.05


Reserve size =


2000


Order F:
  900 @ 20.01,


Reserve size =


1100,


OriginalPrice =


20.01,


RTB = Y


Away Market
  2000 @ 20.00


Center A









The process receives the following limit order:

    
    
        →Order G: Sell 10,000 @ 20.02
    
    


The process matches incoming Order G with 10,000 shares of posted Order A according to normal trading rules, depleting all of Order G and leaving 1,000 shares of Order A posted to the book.
The internal book looks like this:











Bids
Offers


















Order A:
1000 @ 20.02  
Order C:
5000 @ 20.03


Order E:
 400 @ 20.02,
Away Market
1000 @ 20.03




Center A


Reserve size =


4600,


OriginalPrice =


20.02,


RTB = Y


Order B:
3000 @ 20.01,
Order D:
1000 @ 20.05


Reserve size =


2000


Order F:
 900 @ 20.01,


Reserve size =


1100,


OriginalPrice =


20.01,


RTB = Y


Away Market
2000 @ 20.00


Center A









The public posting market center order book looks like this:











Bids
Offers


















Posting Market
1400 @ 20.02  
Posting Market
5000 @ 20.03


Center

Center


Posting Market
3900 @ 20.01
Posting Market
1000 @ 20.05


Center

Center









A few seconds later, at step 120, the process detects the resulting Print on the Tape:

    
    
        →10,000 shares @ 20.02 traded on the Posting Market Center
    
    


At step 122, the process determines that this trade executed on the posting market center 20, so it ends the process at step 126. Only away market trades can reprice reprice-to-block orders.
EXAMPLE 5
Trade on the Tape is an Inferior Priced Block Trade, Reprice-to-Block Buy Orders are Repriced
In this example, the internal book still appear as follows:











Bids
Offers


















Order A:
1000 @ 20.02
Order C:
5000 @ 20.03


Order E:
 400 @ 20.02,
Away
1000 @ 20.03


Reserve size = 4600,

Market


OriginalPrice = 20.02,

Center A


RTB = Y


Order B:
3000 @ 20.01,
Order D:
1000 @ 20.05


Reserve size = 2000


Order F:
 900 @ 20.01,


Reserve size = 1100,


OriginalPrice = 20.01,


RTB = Y


Away Market Center A
2000 @ 20.00









At step 120, the process detects the following Print on the Tape:

    
    
        →10,000 shares @ 20.00 traded on Away Market Center A
    
    


At step 122, the process determines that this trade did not execute on the posting market center 20, and at step 124, the process determines that this is a regular-way trade. At step 128, the process sets the PrintTradeVolume parameter equal to 10,000, the size of the trade. At step 130, the process sets the PrintTradePrice parameter equal to $20.00, the price of the trade.
At step 132, the process retrieves the posting market center's best bid and offer, and in step 134, the process compares the PrintTradePrice parameter ($20.00) to the posting marker center best bid ($20.02). As the PrintTradePrice parameter is lower than the posting market center best bid, the process continues to step 136 and initiates the process to determine if the Last Sale constitutes a block trade, at step 160 (FIG. 4).
At step 162, the process retrieves the MinBlockVolume parameter, which, in this example, is set to 10,000 shares. At step 164, the process compares the PrintTradeVolume parameter (10,000) to the MinBlockVolume parameter (10,000). As the PrintTradeVolume is the same as the MinBlockVolume, the process proceeds to step 165 where it determines if the trade must also meet minimum marketplace value requirements. As this example uses an equity security issue as its basis and block trades are not required to meet minimum value requirements in addition to minimum volume requirements, the process proceeds from step 165 to step 174.
At step 174, the process sets the flag “IsBlock” equal to “1” (true). At step 176, the process passes the binary value back to step 138 in the process New Last Sale Detected (FIG. 3). As the value of IsBlock=1, the process proceeds to step 140 to determine whether any reprice-to-block buy orders must be repriced. Step 140 invokes the process to reprice-to-block buy orders at step 200 (FIG. 5).
At step 202, the process retrieves the first reprice-to-block buy order, Order E. At step 204, it compares the price of Order E ($20.02) to the PrintTradePrice ($20.00). As the buy order's price is higher, at step 206, the process changes Order E's price to $20.00, the price of the PrintTradePrice. At step 208, the process inserts the repriced order in the internal book according to its new price/time priority.
The internal book momentarily appears as follows after Order E has been repriced:











Bids
Offers


















Order A:
1000 @ 20.02
Order C:
5000 @ 20.03


Order B:
3000 @ 20.01,
Away
1000 @ 20.03


Reserve size = 2000

Market




Center A


Order F: 900 @ 20.01,

Order D:
1000 @ 20.05


Reserve size = 1100,


OriginalPrice = 20.01,


RTB = Y


Order E:
 400 @ 20.00,  


Reserve size = 4600,


OriginalPrice = 20.02,


RTB = Y


Away Market Center A
2000 @ 20.00









At step 210, the process checks to see if there are any more buy orders with RTB=Y and determines that there are. The process returns to step 202 and retrieves the next reprice-to-block order, Order F. At step 204, the process compares the price of Order F ($20.01) to the PrintTradePrice ($20.00). As the buy order's price is higher, the process changes Order F's price to $20.00, the value of the PrintTradePrice, at step 206. At step 208, the process inserts the repriced order in the internal order book according to its new price/time priority. At step 210, the process again checks to see if any more buy orders with RTB=Y exist, and finding none in this example, ends the update process at step 212.
The internal book looks like this:











Bids
Offers


















Order A:
1000 @ 20.02
Order C:
5000 @ 20.03


Order B:
3000 @ 20.01
Away 
1000 @ 20.03


Reserve size = 2000

Market




Center A


Order E:
 400 @ 20.00,
Order D:
1000 @ 20.05


Reserve size = 4600,


OriginalPrice = 20.02,


RTB = Y


Order F:
 900 @ 20.00,  


Reserve size = 1100,


OriginalPrice = 20.01,


RTB = Y


Away Market Center A
2000 @ 20.00









The public posting market center book now looks like this:











Bids
Offers


















Posting Market Center
1000 @
Posting Market Center
5000 @



20.02  

20.03


Posting Market Center
3000 @
Posting Market Center
1000 @



20.01  

20.05


Posting Market Center
1300 @



20.00  









EXAMPLE 6
Incoming Sell Order Trades with Posted Buy Orders where Reprice-to-Block Orders have Already Moved Their Prices
At around the same time the above process is happening, a market participant has also detected the block trade that executed priced at $20.00, and this market participant also detected the superior-priced bids that were displayed on the posting market center prior to being repriced. As a reminder, at the time the block trade at $20.00 was reported to the Tape, the public book for the posting market center looked like this:











Bids
Offers


















Posting Market Center
1400 @ 20.02
Posting Market Center
5000 @





20.03


Posting Market Center
3900 @ 20.01
Posting Market Center 
1000 @





20.05









The market participant that detected the block trade at $20.00 sees that the posting market center is displaying 5300 orders superior to the block trade at $20.00 (i.e. 1400 at $20.02 and 3900 at $20.01). The market participant attempts to trade against the superior priced orders immediately.
The posting market center 20 receives the following order:

    
    
        →Order H: Sell 6000 @ 20.01, IOC
    
    


The process retrieves the highest buy order, Order A. It compares the price of Order A ($20.02) to the price of incoming Order H ($20.01). As the prices overlap, the process matches 1000 shares at $20.02, Order A's price, completely filling Order A and removing it from the books. The process checks to see if incoming Order H still has additional shares to trade, and determines that it has 5000 shares remaining.
The process retrieves the next buy order, Order B. It compares the price of Order B ($20.01) to the price of incoming Order H ($20.01). As the prices are equal, the process matches 5000 shares at $20.01, completely filling Order B and removing it from the books. The process first matches the 3000 displayed shares of Order B and then matches the 2000 reserve shares of Order B. The process checks to see if incoming Order H still has additional shares to trade, and determining that none remain, the process is terminated.
The internal book looks like this:











Bids
Offers


















Order E:
 400 @ 20.00,
Order C:
5000 @ 20.03


Reserve size = 4600,


OriginalPrice = 20.02,


RTB = Y


Order F:
 900 @ 20.00,
Away
1000 @ 20.03


Reserve size = 1100,

Market


OriginalPrice = 20.01,

Center A


RTB = Y


Away Market Center A
2000 @ 20.00
Order D:
1000 @ 20.05









The public posting market center book now looks like this:











Bids
Offers


















Posting Market Center
1300 @
Posting Market Center
5000 @



20.00  

20.03




Posting Market Center
1000 @





20.05









As illustrated in this example, Orders A and B left themselves open to arbitrage since they were not reprice-to-block orders. After the block trade, Orders A and B remained at their original prices. As a result, these orders, Orders A and B, were hit by an incoming order taking advantage of this arbitrage opportunity.
In contrast, Orders E and F, which were tagged to reprice, promptly repriced to the block trade price when the block trade at the inferior price was detected. As a result, the automatic repricing of these orders prevented then from being hit at their original, superior order price. Once repriced, a reprice-to-block order, such as Orders E and F in this example, do not revert to their original price. However, Orders E and F could be repriced lower. For instance, should another block trade subsequently trade at a price that is lower than their current price ($20.00), Orders E and F would be automatically repriced again, and their previous price would be stored for audit purposes as well. This process is repeated as necessary until Orders E and F are fully executed or canceled.
Away Market Center A then changes its offer price to $20.01. The internal book looks like this:











Bids
Offers


















Order E:
 400 @ 20.00,
Away
1000 @ 20.01  


Reserve size = 4600,

Market


OriginalPrice = 20.02,

Center A


RTB = Y


Order F:
 900 @ 20.00,
Order C:
5000 @ 20.03


Reserve size = 1100,


OriginalPrice = 20.01,


RTB = Y


Away Market Center A
2000 @ 20.00
Order D:
1000 @ 20.05









Market Center A's Offer of $20.01 is now the best offer. As shown in the examples that follow, reprice-to-block orders are repriced whenever a worse-priced block trade is detected, regardless of whether the posting market center 20 is at the NBBO or not.
EXAMPLE 7
Reprice-to-Block Sell Order is Received
At step 300, the process receives the following incoming reprice-to-block sell order:

    
    
        →Order I: Sell 3000 @ 20.02, Show size=300, Reserve size=2700, RTB=Yes
    
    


At step 302, the process determines that Order I is not marketable, as there is no overlap between the sell order price and the best bid price. (Note that even though the OriginalPrice of Order E is $20.02, the order can only trade at its current price of $20.00.) At step 310, the process stores the order price as the OriginalPrice for audit purposes, and at step 312, it posts the reprice-to-block order to the internal book and the public posting market center order book according to normal price/time priority rules. The process terminates at step 314.
The internal book looks like this:











Bids
Offers


















Order E:
 400 @
Away Market Center A
1000 @



20.00,

20.01


Reserve size = 4600,


OriginalPrice = 20.02,


RTB = Y


Order F:
 900 @
Order I:
300 @



20.00,

20.02,  


Reserve size = 1100,

Reserve size = 2700,


OriginalPrice = 20.01,

OriginalPrice = 20.02,


RTB = Y

RTB = Y


Away Market
2000 @
Order C:
5000 @


Center A
20.00

20.03




Order D:
1000 @





20.05









The public posting market center order book now looks like this:











Bids
Offers


















Posting Market Center
1300 @
Posting Market Center
 300 @



20.00

20.02  




Posting Market Center
5000 @





20.03




Posting Market Center
1000 @





20.05









EXAMPLE 8
Block Trade on the Tape is Not at an Inferior Price
At step 120, the process detects the following Print on the Tape:

    
    
        →10,000 shares @ 20.02 traded on Away Market Center A
    
    


At step 122, the process determines that this trade did not execute on the posting market center 20, and at step 124, it determines that this is a regular-way trade. At step 128, the process sets the PrintTradeVolume parameter equal to 10,000, the size of the trade. At step 130, it sets the PrintTradePrice parameter equal to $20.02, the price of the trade.
At step 132, the process retrieves the posting market center best bid and offer and in step 134, it compares the PrintTradePrice ($20.02) to the posting market center best bid ($20.00). As the PrintTradePrice parameter is not lower than the posting market center best bid, the process does not need to check for the presence of any reprice-to-block buy orders, so the process continues to step 142.
At step 142, the process compares the PrintTradePrice parameter ($20.02) to the posting market center best offer ($20.02). As the PrintTradePrice parameter is not higher than the posting market center best offer (the prices are equal), the process does not need to check for the presence of any reprice-to-block sell orders. The process, in this example, is complete as indicated at step 144.
EXAMPLE 9
Trade on the Tape is an Inferior Price, But is Not a Block Trade
In step 120, the process detects the following Print on the Tape:

    
    
        →9,500 shares @ 20.03 traded on Away Market Center A
    
    


At step 122, the process determines that this trade did not execute on the posting market center 20, and in step 124, it determines that this is a regular-way trade. At step 128, the process sets the PrintTradeVolume parameter equal to 9,500, the size of the trade. At step 130, it sets the PrintTradePrice parameter equal to $20.03, the price of the trade.
At step 132, the process retrieves the posting market center's best bid and offer and in step 134, the process compares the PrintTradePrice parameter ($20.03) to the posting market center's best bid ($20.00). As the PrintTradePrice parameter is not lower than the posting market center's best bid, the process does not need to reprice any reprice-to-block buy orders, so the process continues to step 142. At step 142, the process compares the PrintTradePrice parameter ($20.03) to the posting market center's best offer price ($20.02) and determines that the PrintTradePrice parameter is higher. The process proceeds to step 146 and initiates the process to determine if the Last Sale constitutes a block trade at step 160 (FIG. 4).
At step 162, the process retrieves the MinBlockVolume parameter, which is currently set to 10,000 shares. At step 164, the process compares the PrintTradeVolume parameter (9,500) to the MinBlockVolume parameter (10,000). As the PrintTradeVolume parameter is less than the MinBlockVolume parameter, it proceeds to step 166.
At step 166, the process retrieves the MinBlockValue parameter, which is currently set to $200,000. At step 168, the process computes the TotalTradeValue parameter by multiplying the PrintTradeVolume (9,500) by the PrintTradePrice ($20.03). The derived TotalTradeValue=$190,285. At step 170, the process compares the TotalTradeValue ($190,285) to the MinBlockValue ($200,000). As the TotalTradeValue is less than the MinBlockValue, it determines that this trade does not constitute a block trade. At step 172, it sets the flag “IsBlock”=0 (false).
At step 176, the process passes the binary value back to step 148 in the process New Last Sale Detected (FIG. 3). As the value of “IsBlock”=0, no reprice-to-block sell orders are repriced, so the process ends at step 144.
EXAMPLE 10
Trade on the Tape is an Inferior Priced Block Trade, Reprice-to-Block Sell Orders are Repriced
The internal book still looks like this:











Bids
Offers


















Order E:
400 @ 20.00,
Away Market Center A
1000 @ 20.01


Reserve size = 4600,


OriginalPrice = 20.02,


RTB = Y


Order F:
900 @ 20.00,
Order I:
 300 @ 20.02,


Reserve size = 1100,

Reserve size = 2700,


OriginalPrice = 20.01,

OriginalPrice = 20.02,


RTB = Y

RTB = Y


Away Market Center A
2000 @ 20.00  
Order C:
5000 @ 20.03 




Order D:
1000 @ 20.05 









At step 120, the process detects the following Print on the Tape:

    
    
        →10,000 shares @ 20.03 traded on Away Market Center A
    
    


At step 122, the process determines that this trade did not execute on the posting market center 20, and at step 124, the process determines that this is a regular-way trade. At step 128, the process sets the PrintTradeVolume parameter=10,000, the size of the trade. At step 130, it sets the PrintTradePrice parameter=$20.03, the price of the trade.
At step 132, the process retrieves the posting market center best bid and offer, and at step 134, it compares the PrintTradePrice ($20.03) to the posting market center's best bid ($20.00). As the PrintTradePrice is not lower than the posting market center's best bid, the process does not need to reprice any reprice-to-block buy orders, so the process continues to step 142. At step 142, the process compares the PrintTradePrice ($20.03) to the posting market center's best offer price ($20.02) and determines that the PrintTradePrice is higher. The process proceeds to step 146 and initiates the process to determine if the Last Sale constitutes a block trade at step 160 (FIG. 4).
At step 162, the process retrieves the MinBlockVolume parameter, which is currently set to 10,000 shares. At step 164, the process compares the PrintTradeVolume (10,000) to the MinBlockVolume (10,000). As the PrintTradeVolume is the same as the MinBlockVolume, it proceeds to step 165, where it checks if the trade must also meet minimum market value requirements. In this example, since this issue is an equity security, the volume and value requirements do not both need to be satisfied, and the process proceeds to step 174.
At step 174, the process sets the flag IsBlock=1 (true). At step 176, the process passes the binary value back to step 148 in the process New Last Sale Detected (FIG. 3). As the value of “IsBlock”=1, the process proceeds to step 150 to determine whether any reprice-to-block sell orders must be repriced. Step 150 invokes the process to reprice-to-block sell orders, at step 400 (FIG. 7).
At step 402, the process retrieves the first reprice-to-block sell order, Order I. At step 404, the process compares the price of Order I ($20.02) to the PrintTradePrice ($20.03). As the sell order's price is lower, at step 406, the process changes Order I's price to $20.03, the price of the PrintTradePrice. At step 408, the process inserts the repriced order in the internal book according to its new price/time priority. At step 410, the process checks to see if other sell orders with RTB=Y exist, and finding none, ends the update process at step 412.
The internal book looks like this:











Bids
Offers


















Order E:
400 @ 20.00,
Away Market Center A
1000 @ 20.01


Reserve size = 4600,


OriginalPrice = 20.02,


RTB = Y


Order F:
900 @ 20.00,
Order C:
5000 @ 20.03


Reserve size = 1100,


OriginalPrice = 20.01,


RTB = Y


Away Market Center A
2000 @ 20.00  
Order I:
  300 @ 20.03,  




Reserve size = 2700,




OriginalPrice = 20.02,




RTB = Y




Order D:
1000 @ 20.05









The public posting market center order book now looks like this:











Bids
Offers


















Posting Market
1300 @ 20.00
Posting Market
5300 @ 20.03  


Center

Center




Posting Market
1000 @ 20.05  




Center









As with Orders E and F in the buy order example above, once repriced, Order I is never reset to its original price. However, Order I could be repriced higher. For instance, should another block trade subsequently trade at a price that is higher than Order I's current price ($20.03), Order I would be automatically repriced again, and its previous price would be stored for audit purposes as well. This process is repeated as necessary until Order I is fully executed or canceled.
EXAMPLE 11
Trade on the Tape is an Inferior Priced Block Trade, Reprice-to-Block Options Sell Order is Repriced
This example, Example 11, is an equity options example and is similar to Example 10 above except that orders and quotes in an equity options issue are shown rather than the orders and quotes in an equity security issue that were shown in Example 10. The particular issue discussed in this example does not have Market Makers assigned to it and, therefore, Market Maker quotes are not discussed in this example. Even if Market Maker quotes were present, they would not be relevant to this discussion, as only orders, not quotes, can be repriced-to-block. As previously described, the definition of a block trade is different on an options market than on an equities market.
At the start of this example, the internal book looks like this. Note that Order L and Order M have already been previously repriced-to-block, as evidenced by their higher OriginalPrices:











Bids
Offers


















Order L:
40 @ 2.00,
Away Market
100 @ 2.05


Reserve size = 460,

Center A


OriginalPrice = 2.10,


RTB = Y


Order M:
90 @ 2.00,
Order N:
 30 @ 2.10,


Reserve size = 110,

Reserve




size = 270,


OriginalPrice = 2.05,

OriginalPrice =




2.10,


RTB = Y

RTB = Y


Away Market Center A
200 @ 2.00  
Order J:
 50 @ 2.15









At step 120, the process detects the following Print on the Tape:

    
    
        →70,000 contracts @ 2.15 traded on Away Market Center A
    
    


At step 122, the process determines that this trade did not execute on the posting market center 20, and at step 124, the process determines that this is a regular-way trade. At step 128, the process sets the PrintTradeVolume parameter=70,000, the size of the trade. At step 130, it sets the PrintTradePrice parameter=$2.15, the price of the trade.
At step 132, the process retrieves the posting market center best bid and offer, and at step 134, it compares the PrintTradePrice ($2.15) to the posting market center's best bid ($2.00). As the PrintTradePrice is not lower than the posting market center's best bid, the process does not need to reprice any reprice-to-block buy orders, so the process continues to step 142. At step 142, the process compares the PrintTradePrice ($2.15) to the posting market center's best offer price ($2.10) and determines that the PrintTradePrice is higher. The process proceeds to step 146 and initiates the process to determine if the Last Sale constitutes a block trade at step 160 (FIG. 4).
At step 162, the process retrieves the MinBlockVolume parameter, which is currently set to 500 contracts. At step 164, the process compares the PrintTradeVolume (70,000) to the MinBlockVolume (500). As the PrintTradeVolume is higher than the MinBlockVolume, it proceeds to step 165.
At step 165, the process checks whether this trade must also meet minimum market value requirements to constitute a block trade. In this example, since the issue is an equity option, the volume and value requirements both need to be satisfied, and the process proceeds to step 166. At step 166, the process retrieves the MinBlockValue parameter, which in this example is set to $150,000. At step 168, the process computes the TotalTradeValue parameter by multiplying the PrintTradeVolume parameter (70,000) by the PrintTradePrice ($2.15). The computed TotalTradeValue=$150,500. At step 170, the process compares the TotalTradeValue ($150,500) to the MinBlockValue ($150,000). As the TotalTradeValue is higher than the MinBlockValue, it determines that this trade does constitute a block trade.
At step 174, the process sets the flag IsBlock=1 (true). At step 176, the process passes the binary value back to step 148 in the process New Last Sale Detected (FIG. 3). As the value of “IsBlock”=1, the process proceeds to step 150 to determine whether any reprice-to-block sell orders must be repriced. Step 150 invokes the process to reprice-to-block sell orders, at step 400 (FIG. 7).
At step 402, the process retrieves the first reprice-to-block sell order, Order N. At step 404, the process compares the price of Order N ($2.10) to the PrintTradePrice ($2.15). As the sell order's price is lower, at step 406, the process changes Order N's price to $2.15, the price of the PrintTradePrice. At step 408, the process inserts the repriced order in the internal book according to its new price/time priority. At step 410, the process checks to see if other sell orders with RTB=Y exist, and finding none, ends the update process at step 412.
The internal book looks like this:











Bids
Offers


















Order L:
40 @ 2.00,
Away Market Center A
100 @ 2.05


Reserve size = 460,


OriginalPrice = 2.10,


RTB = Y


Order M:
90 @ 2.00,
Order J:
 50 @ 2.15


Reserve size = 110,


OriginalPrice = 2.05,


RTB = Y


Away Market Center A
200 @ 2.00  
Order N:
  30 @ 2.15,  




Reserve size = 270,




OriginalPrice = 2.10,




RTB = Y









The public posting market center order book now looks like this:











Bids
Offers


















Posting Market
130 @ 2.00
Posting Market Center
80 @ 2.15  


Center









Order N, as with other repriced-to-block orders above, never resets to its original price after it has been repriced. However, Order N could be repriced higher if necessary. For instance, should another block trade subsequently trade at a price that is higher than Order N's current price ($2.15), Order N would be automatically repriced again, and its previous price would be stored for audit purposes as well. This process is repeated as necessary until Order N is fully executed or canceled.
While the invention has been discussed in terms of certain embodiments, it should be appreciated that the invention is not so limited. The embodiments are explained herein by way of example, and there are numerous modifications, variations and other embodiments that may be employed that would still be within the scope of the present invention.

## Claims

1. A method for repricing a posted limit order on a posting market center in view of a block trade executed on an away market center at an inferior price, the method comprising:
posting a limit order on a posting market center;
receiving data by a computing system regarding a block trade executed (a) on an away market center (b) after posting the limit order on the posting market center;
determining by the computing system that the block trade executed at an inferior price to the limit order posted on the posting market center; and
repricing by the computing system the limit order posted on the posting market center to the inferior price that the block trade executed at.

2. The method of claim 1, wherein the posted limit order is a buy order.

3. The method of claim 1, wherein the posted limit order is a sell order.

4. The method of claim 1, wherein the posted limit order is a reserve order.

5. The method of claim 1, wherein the posting market center operates in an equities marketplace.

6. The method of claim 1, wherein the posting market center operates in an options marketplace.

7. The method of claim 1, wherein the computing system is one or more programmed computers.

8. The method of claim 1, wherein the computing system is distributed over several physical locations.

9. A system, comprising:
a market center memory for repricing a posted limit order on a posting market center in view of a block trade executed on an away market center at an inferior price;
storing code for repricing the posted limit order on the posting market center in view of the block trade executed on the away market center at the inferior price;
a processor for executing the stored code for repricing the posted limit order on the posting market center in view of the block trade executed on the away market center at the inferior price, wherein the stored code comprises:
code to post a limit order on the posting market center;
code to receive data regarding the block trade executed (a) on the away market center (b) after posting the limit order on the posting market center;
code to determine that the block trade executed at the inferior price to the limit order posted on the posting market center; and
code to reprice the limit order posted on the posting market center to the inferior price that the block trade executed at.

10. The system of claim 9, wherein the computing system is one or more programmed computers.

11. The system of claim 9, wherein the computing system is distributed over several physical locations.

12. A system, comprising:
a computing system including at least one processor for executing code stored in at least one memory, wherein the code when executed:
posts a limit order on a posting market center;
receives data regarding a block trade executed (a) on an away market center (b) after posting the limit order on the posting market center;
determines that the block trade executed at an inferior price to the limit order posted on the posting market center; and
reprices the limit order posted on the posting market center to the inferior price that the block trade executed at.

13. The system of claim 12, wherein the computing system is one or more programmed computers.

14. The system of claim 12, wherein the computing system is distributed over several physical locations.