Last Updated: 8/27/2026
| # | Status | Summary | Posted Date | Spec Publish Date | Spec Version | Effective Date - Test | Effective Date - Prod |
|---|---|---|---|---|---|---|---|
| 1 | Open | Add new 'MX2OP' value for the destination, senderIMID and marketCenterID fields to support MX2 Options. | 3/06/2026 | 4/30/2026 | 4.2.0 | 8/03/2026 | 9/14/2026 |
| 2 | Open | Add new 'IEXOP' value for the destination, senderIMID and marketCenterID fields to support IEX Options. | 3/06/2026 | 4/30/2026 | 4.2.0 | 8/03/2026 | 10/2/2026 |
| 3 | Open | Pursuant to the Commission's order granting Exemptive Relief, dated January 23, 2026, all RFQ responses that are communicated in standard electronic format directly to an Industry Member's OMS/EMS or to an RFQ platform and that are not "immediately actionable" (i.e., further action is required before a trade can be executed/routed), to the extent such responses are considered "orders" reportable pursuant to Rule 613(j)(8), are no longer required to be reported to CAT:
| 3/20/2026 | 4/30/2026 | 4.2.0 | 11/23/2026 | 12/7/2026 |
4 | Open | Allow for the exchOriginCode field to be blank/null on MOOR and MLOR events when no value is communicated to exchange. This scenario is currently rejected under Error Code 2028. | 8/25/2026 | 9/25/2026 | 4.2.0 r2 | 11/9/2026 | 12/7/2026 |
| 5 | Open | The feedbackVersion on all stages of Transaction feedback will change from 4.1.0 to 4.2.0, reflecting the schema version of the specifications and feedback file. | 8/25/2026 | 4/30/2026 | 4.2.0 | 11/9/2026 | 12/7/2026 |
*Planned Technical Specification Updates are subject to approval by the CAT NMS Plan Operating Committee.