Throughout this Form ATS-N the Broker-Dealer Operator, CODA Markets, Inc., is referred to as "CODA Markets" and the NMS Stock ATS is referred to as "CODA" or "CODA ATS". The following affiliates of CODA Markets will be able to enter or direct orders to CODA: ACS Execution Services, LLC (CRD 17972, SEC 8-36005, MPID: GLPX), an SEC-registered broker-dealer that trades in a principal, riskless principal and agency capacity on CODA; and Comhar Capital Markets, LLC (CRD 47955, SEC 8-51969, MPID: COHR), an SEC-registered broker-dealer that trades in a principal and riskless principal capacity on CODA. 

Subscribers (both Liquidity Seekers and Liquidity Providers) may opt out from interacting with a CODA Markets Affiliate on a limited basis. Specifically, users of CODA MICRO may opt out from interacting with CODA Markets Affiliates. However, the opt-out functionality does not exist for CODA BLOCK or CODA FUSE. Requests may be delivered verbally or in writing by the Subscriber. CODA can process and effect opt out requests intraday or on a scheduled date. Opt out duration is at the discretion of the Subscriber. CODA enforces the opt out at the MPID level, similar to counter party selection as referenced in Part III, Item 14. 

Global Liquidity Partners, LLC ("GLP"), an affiliate of CODA Markets, will be providing certain end data assistance related to operating CODA. In particular, GLP will provide CODA with data analyses performed by Advanced Liquidity Studies and Analytics ("ALISA"). In turn, CODA's, Liquidity Protection Rule ("LPR") functionality relies on ALISA's data analyses in order to function as described in greater detail in response to Part III, Item 11 below. 

The Chief Executive Officer ("CEO"), Chief Compliance Officer ("CCO") and Financial and Operations Principal ("FinOp") for CODA Markets will be dually registered with and will serve in the same roles at one or more broker-dealer affiliates of CODA Markets. These individuals will have access to CODA Markets confidential trading information, as defined in response to Part II, Item 7(d) below. In addition, CODA Markets employees who provide accounting, operations, compliance, technology, and legal services to other business activities of CODA Markets and also support CODA have access to CODA confidential trading information. CODA Markets employees who do not support the CODA ATS do not have access to CODA confidential trading information. As noted above, GLP is the provider of ALISA, and as such, certain GLP employees will provide software support services to CODA Markets in addition to providing software support services to other affiliates of CODA Markets. These individuals may have access to CODA Markets confidential trading information to provide data analysis to CODA Markets products and clients. 

GLP will provide ongoing technological support associated with the development and maintenance of the LPR, discussed in Part II, Item 5(c), as well as to the Liquidity Protection Rule Calculator ("LPRC") made available to registered users of the LPRC on the CODA Markets website. (As background, the LPRC output is a numerical and graphic representation of the Auction Trade Price band used by the LPR in CODA BLOCK and CODA FUSE for that trading day (discussed in detail in Part III, Item 11 (c)). Registered users of LPRC can be both Subscribers and non-Subscribers of CODA.) As background, CODA Markets has entered into a Master Services Agreement ("MSA") with Apex Fintech Solutions Inc. ("AFS" or "Apex") pursuant to which AFS will provide certain hardware, software and data assistance with operating CODA, including assistance associated with the functionalities described throughout Part III below. Development and maintenance of each of the auction platforms (i.e., CODA MICRO, CODA BLOCK and CODA FUSE) are examples of ongoing support provided by AFS to CODA. The following companies will be included in the MSA and provide the services detailed below to CODA Markets: - PICO Quantitative Trading, LLC ("PICO") and SpiderRock Gateway Technologies ("SpiderRock") provide market data to Apex which is integrated into the software provided by Apex to CODA. PICO is Apex's primary market data provider. SpiderRock is Apex's backup market data provider. CODA's usage of market data is discussed in detail in Part III, Item 23. - QUODD Financial Information Services, Inc. ("QUODD") provides reference market data services to CODA. The reference data provided by QUODD is for individual Reg NMS stocks and includes capitalization, sector, consolidated volumes and official closing prices. QUODD data is received daily and in file form. CODA uses QUODD data historically and as an input for the market capitalization-based minimum quantity requirements, as discussed in Part III, Item 11 (c). - NY5 (mentioned in Part I, Item 7 and Part III, Item 6(a)) is the data center where the CODA systems reside. Service and support teams provided by NY5 can, if needed, provide on-site support to the Apex hardware systems supporting the CODA ATS as directed by AFS. Service and support teams provided by the data centers do not have access to any confidential trading information. Merrill Broadcort, a division of BofA Securities Inc., provides clearing services to CODA Markets, CODA, and FLARE via a fully disclosed clearing agreement. FLARE is CODA's outbound router discussed throughout this Form and in detail in Part III, Item 16(b). CODA's clearing and settlement procedures are discussed in detail in Part III, Item 22. 

BofA Securities, Inc., ACS Execution Services, LLC (an affiliate of GLP and CODA Markets), Comhar Capital Markets, LLC (an affiliate of GLP and CODA Markets), and Apex Clearing Corporation (a subsidiary of AFS) are CODA Markets Subscribers and users of the ATS services including the ATS and FLARE. 

Protection of CODA Markets Confidential Trading Information: CODA considers Subscribers' confidential trading information to be Participant activity and execution data from their interaction with and usage of the ATS and other CODA services discussed throughout this Form. "Confidential trading information" is deemed to include: 1) Subscriber order and conditional liquidity detail (conditional liquidity refers to conditional interests and inbound IOIs collectively, both of which are discussed individually in detail in Part III, Item 7(a)); 2) Subscriber execution detail; 3) Individual Subscriber order and execution statistics; 4) FIX messages sent to CODA from Subscribers; 5) FIX messages sent from CODA to Subscribers; and 6) LPRC queries. Access to confidential trading information may be in real-time (via the ATS system directly) or post-trade (via other systems/ tools or stored data) or both. Access to real-time confidential trading information is the most sensitive and restricted. Employees are authorized to access confidential trading information when it is necessary to support CODA Markets': 1) Operations; 2) Subscriber support; 3) Business and technological development and support; 4) Systemic testing; and 5) Regulatory reviews, testing, investigations, surveillances, and reporting. Access to real-time confidential trading information is strictly prohibited for any personnel, including personnel of parent or one or more affiliated companies, who directly or indirectly trade for or have influence over the trading decisions of a subscriber or other trading entity. As described in Part III, Item 16(b), FLARE is CODA's outbound router. In addition to public market data, FLARE uses certain Subscriber confidential trading information in order to route and execute individual FLARE-eligible orders at CODA and away markets, including extended hours order entry and execution, as described in Part III, Item 4(a). Three types of Subscriber confidential trading information are used in connection with the FLARE order routing services: 1) In order to route FLARE-eligible orders, FLARE has access to and uses the order detail found in the FIX message sent to CODA. For example, FLARE uses the price or effective price on an order to determine the order's marketability. FLARE can then use the order's marketability to determine the routing logic for that order. 2) Execution data specific to the order being executed can be used by FLARE when an order remains live and partially executed. For example, FLARE can reroute unexecuted shares resting at one venue to another venue based on partial execution data specific to that order. This includes execution data from both CODA and away markets. 3) As part of its smart order routing functionality, FLARE is equipped with a machine learning-based process to optimize order routing decisions based on aggregated information about historical routing and execution results involving orders with similar characteristics that have been previously routed. For example, if FLARE previously routed portions of a certain 2,000 share parent order ("parent_order_1"), 1,000 to Venue A in child_order_a and 1,000 to Venue B in child_order_b, and received a complete fill at Venue A and no fill at Venue B, in an effort to increase the likelihood of a fill and improve overall execution performance for future orders, when the FLARE smart order router receives future parent orders that have similar characteristics to parent_order_1 it will use the execution information from parent_order_1, including child_order_a and child_order_b, to determine where to route child orders for that parent. FLARE's smart order router does not have access to any information regarding live orders or conditional liquidity resting in CODA, nor does FLARE have access to unfilled or cancelled orders, or conditional liquidity that was previously live and resting in CODA. Aside from using historical execution information for regular maintenance and smart order routing optimization, employees are not authorized to use CODA confidential trading information for purposes of operating FLARE. Personal Trading Accounts: Employees are required to obtain compliance approval prior to establishing brokerage accounts. Annually, each employee must attest in writing that they have disclosed to CODA Markets Compliance all their brokerage accounts and they understand and will abide by CODA Markets' personal trading policies. At least quarterly, for each disclosed account, the CODA Markets Compliance Department reviews the trading activity and money movements for insider trading, compliance with CODA Markets policies and anti-money laundering laws. CODA Markets and ACS Global Holdings, LLC prohibit all employees, including those with access to Subscriber confidential trading information, from trading based on non-public or other confidential information, which would include Subscriber confidential trading information. Upon hire and annually thereafter, each employee is required to read and attest to understanding and abiding to CODA Markets' Insider Trading and Personal Securities Transactions/Prevention of Misuse of Non-Public Information Policies and Procedures. Distribution and collection of the attestations are handled by CODA Markets Compliance Department. It is the policy of CODA Markets and its affiliates, ACS Execution Services, LLC and Comhar Capital Markets, LLC, that employees of CODA Markets and its affiliates shall not direct any trading activity for their own accounts to CODA. Internal Systems Access: CODA Markets, AFS and GLP maintain secured access to both physical and non-physical assets. Physical access to servers and related infrastructure is limited to key personnel both at the datacenters and at the main office with a combination of keypad and/or fingerprint scanners. Physical access to desktop terminals is restricted to authorized individuals by physical key and/or electronic locks to gain access to the buildings. Additional keypad access is required to gain access to sensitive / restricted areas within the buildings. Non-physical access to servers / desktops is limited to authorized individuals maintaining active passwords in accordance with leading industry password policy practices. Failure to maintain an active password in accordance with leading industry password policy practices results in revoked access to non-physical assets. Access changes are initiated with a written request to the network administrator (e.g., email, Slack, Jira ticket), including the business justification for new access or increased entitlements. This includes new access for new or transferring personnel, new access or increased entitlements for existing personnel, access removal or downgrade for existing personnel, suspensions of access, and removal of access for terminated employees. Prior to the network administrator granting access to any CODA ATS system, including any system containing real-time or post-trade confidential trading information, the department head must have made or approved the request and confirm that the request has been reviewed with no objections by CODA Compliance. Consideration must be given as to whether a user requires real-time access when such access is being requested or if such user could effectively perform necessary functions with post-trade access. CODA Compliance will raise any questions or concerns prior to the systems access request being granted. Third-Party System Access: CODA provides post-trade confidential trading information to certain third-party software providers to aid it in the operation of its business. As described in greater detail in Part II, Item 7(d), these third-party software providers provide services that includes, but are not limited to, vendor services for best execution reporting, books and record retention, electronic communications, trade surveillance, and compliance software. Vendors with access to confidential trading information are subject to a risk due diligence process, including information and cybersecurity risk assessment prior to onboarding and periodically thereafter. An internal business owner(s) or administrator(s) is assigned to each third-party product in order to manage authorized users on behalf of CODA. Access requests are initiated with a written request to an internal business owner or administrator (e.g., email, Slack, Jira ticket), including the business justification for the new access or increased entitlements. Electronic Files: CODA Markets utilizes electronic file storage systems for business records, documents, user files and folders, etc. Based upon the use case, the storage system may be cloud based, local, or a hybrid. CODA Markets may save files with confidential trading information (such as compliance T+1 exception reports) on such a system. If so, access to the files will be limited to CODA Markets personnel who are authorized to access confidential trading information. In some cases, CODA Markets may be receiving confidential trading information from a third party (such as Apex as part of Apex hosting the ATS system) or sending confidential trading information to a party (such as a Subscriber at the Subscriber's request). In those cases, an encrypted mechanism such as SFTP will be used unless the owner of the confidential trading information (such as the Subscriber) requests an alternative mechanism. Avoiding Conflicts of Interest: In order to prevent the misuse of confidential trading information and other potential conflicts of interest, CODA Markets has implemented the following policies and procedures: Access to real-time confidential trading information is strictly prohibited for any personnel, including personnel of parent and affiliated companies, who directly or indirectly trade for or have influence over the trading decisions of a Subscriber or other trading entity. Everyone with access to confidential trading information is prohibited from accessing and using confidential trading information for any reason other than providing support, business development, and supervision of the ATS. All employees of CODA Markets and its parent and affiliated broker-dealer entities are required to obtain compliance approval prior to establishing brokerage accounts, and approved accounts are subject to ongoing monitoring by the compliance department of CODA Markets. Annually, each employee must attest in writing that they have disclosed all their brokerage accounts and that they understand and will abide by company personal trading policies. It is the policy of CODA Markets and its affiliates, ACS Execution Services, LLC and Comhar Capital Markets, LLC, that employees of CODA Markets and its affiliates shall not direct any trading activity for their own accounts to CODA. CODA Markets provides training to new hires and on an ongoing basis (no less than annually) regarding safeguarding confidential trading information, information barriers, personal trading policies, material non-public information, and information and cyber security. Responsibilities For Users With Confidential Trading Information Access: - Protecting confidential trading information from unauthorized and even inadvertent access; - Remaining familiar with and adhering to information barriers; - Having confidential trading information access removed or reduced when no longer needed; and - Reporting breaches of confidential trading information or other issues of non-compliance or potential non-compliance with this policy to CODA Markets' Chief Compliance Officer. Supervision: Quarterly, the Head of CODA Markets or qualified designee will: - Confirm that the Firm's Technology has generated an export of users with access to all systems. - Confer with department heads, as needed, to confirm whether any systems should be added or removed. - Ensure that new access changes have been approved and appropriate documentation is maintained. - Review exports of users who have access to each system and confer with department heads, as needed, whether any personnel should be added or removed. - Consider deactivation of users with infrequent access unless access is still warranted for such users (reference access logs as needed to identify users with no access within the last 90 days). - Confirm with business leadership as needed to identify users, as needed, who may have transferred to a different department or assumed a new function and no longer require access to a system or require a lower level of entitlement. - Document the review as a Jira instance on the compliance dashboard. Recordkeeping: The Head of CODA or qualified designee will coordinate with the Firm's Technology and Compliance teams to maintain records of: - Proprietary and third-party systems, tools, and platforms used to store or access Confidential trading information; - Appropriate access logs for each system; - Documentation relating to access requests and changes, including business justifications and approvals; and - Evidence of quarterly supervisory reviews and audit of confidential trading information access. CODA Markets requires completion and approval of new hire, terminated employee, and consultant checklists for control of access to Subscriber data, prior to commencement of work with CODA Markets and following termination. Subscriber data includes any confidential trading information as defined above, as well as Subscriber onboarding paperwork, trading reports and other Participant identifying documentation. Written, documented authorization to access confidential trading information must be provided by a supervisory principal of CODA Markets. A Quarterly review of each employees' and consultants' access to confidential trading information through systems and physical areas of CODA Markets is conducted. Recognized cybersecurity protocols are documented, enforced, and reviewed during periodic cybersecurity meetings. AFS and GLP personnel who provide services to CODA ATS are prohibited from accessing and using CODA ATS Confidential Trading Information for any reason other than providing support and supervision to the CODA ATS. Likewise, the CEO, CCO and FinOp of CODA Markets, as dually registered officers, are prohibited from accessing and using CODA ATS Confidential Trading Information for any reason other than providing support and supervision to CODA ATS. 

Disclosure of confidential trading information (e.g. order history, execution history) can occur with written authorization from a Subscriber directing the type and detail of the information, conditions, frequency and with whom that information may be shared. 

A Subscriber may withdraw consent by providing written instruction rescinding the consent to disclose. 

The CODA Markets management team, comprised of the CEO, CCO, and Head of CODA Markets have oversight responsibilities which require access to both real-time and post trade data CODA Markets Confidential Trading Information. The CODA Markets Compliance unit has responsibilities that require access to real-time and post-trade data. Those responsibilities include, but are not limited to, the supervision of CODA Markets compliance program, supervisory reviews and testing, trade surveillance, research, investigation, and the preparation and analysis of trade data. In the event a member of the CODA Markets Compliance unit is unable to perform their responsibilities, a qualified designee of CODA Markets will be named and granted access to both real-time and post-trade data CODA Markets Confidential Trading Information. In certain instances, the qualified designee may be registered with one or more CODA Markets affiliates including SEC registered broker-dealer(s), ACS Execution Services, LLC (CRD: 17972) and Comhar Capital Markets, LLC (CRD: 47955). CODA Markets business development and institutional support roles, require CODA Markets real-time and post-trade data for responsibilities including trade support, customization, Participant education and oversight. As described in Part II, Item 6(a) above, Apex is a software development company that provides certain hardware, software, and data assistance to CODA Markets pursuant to the MSA. Apex's responsibilities include hosting of the CODA platforms, hardware and software support, data administration, reporting, network connectivity, data storage and system access. Access to CODA Markets's real-time and post trade data allows the Apex team to monitor their systems for, but not limited to performance, accurate order handling and system capacity. The CODA Markets Operations unit is the first point of contact for intraday client and trade support. Access to CODA Markets real-time and post-trade data is essential to provide CODA Participants with fast and efficient support while resolving any issues. The Operations unit monitors system performance throughout the day as well. The Operations team of CODA Markets will have access to real-time trade data to provide support and monitor performance of extended hours order entry and execution, as described in Part III, Item 4(a). ALISA is used to analyze the value and efficiencies of CODA Markets' product offerings. Additionally, the ALISA team assists in the development of products incorporated into CODA. Access to real-time and post-trade data is required to thoroughly and accurately analyze CODA's data in a manner that maximizes the value it can provide to the CODA Markets product offering and its Participants. The Accounting Department of CODA Markets is responsible for invoicing, audits, accounts payable and financial reconciliation. As a result, the accounting department has limited access to CODA Markets post-trade data, but not real-time data. CODA Markets' outside counsel is Katten Muchin Rosenman LLP. This counsel and any other legal counsel for CODA Markets may need and have access to all forms of confidential trading information in order to perform their duties. All legal counselors are bound by professional obligations of confidentiality. CODA Markets' CEO, CCO and FinOp are also registered with ACS Execution Services, LLC (CRD: 17972) and Comhar Capital Markets, LLC (CRD: 47955). All CODA business units are part of CODA Markets, and all CODA employees are employees of CODA Markets. Business units and employees of AFS and GLP who provide services to CODA ATS are prohibited from accessing and using CODA ATS Confidential Trading Information for any reason other than providing support and supervision to CODA ATS. S3 Matching Technologies LP ("S3") is contracted by CODA Markets to receive order and execution data to produce public and non-public reports through the S3 platform. Those reports include regulatory reports such as those required by Rules 605 and 606. S3's receipt and usage of CODA Markets' data is subject to a confidentiality agreement. As discussed in Part II Item 5(c), CODA Markets is entering into an MSA with Apex. The following companies will be included in the MSA and provide the services detailed below to CODA Markets: - Amazon Web Services ("AWS") provides CODA Markets with services to maintain and preserve electronic records of post-trade confidential trading information in accordance with Rule 17-(a)(4) and provides compute processing to ALISA. - Trillium Surveyor utilizes confidential trading information to provide post-trade surveillance and related tools to help facilitate CODA Markets Compliance Department's review and surveillance of trading activity on CODA ATS. - My Virtual Business Unit, LLC ("MYVBU") provides CODA Markets monthly services in accounting, data analysis and pre-market open system checks. MYVBU provides custom automated programming through a variety of different excel based tools as well as an internal reporting system. Reports generated by MYVBU support the accounting, billing, and data analysis departments. MYVBU performs a daily review of reports and is instructed to escalate to CODA personnel when certain criteria do not fall within defined parameters. MYVBU performs a pre-market open checklist to ensure CODA systems are started properly and without issue. MYVBU is instructed to notify CODA Markets personnel if an issue is encountered. MYVBU's work on behalf of CODA is subject to a confidentiality agreement. 

CODA Markets, the Broker Dealer Operator of CODA (the Reg NMS Stock ATS), requires broker-dealers and institutions accessing CODA in their own MPID (broker of record) or in their own name (institutional), to complete and execute certain documents, including a Subscriber Agreement, as part of CODA Markets onboarding and approval process. Firms accessing and trading at CODA in this manner are referred to as "Subscribers" in this Form. "Sponsored Users" are defined as firms who access and trade with CODA via an approved risk gateway of a sponsoring broker Subscriber. In all cases, the sponsoring broker is a CODA Subscriber and the broker of record on all orders, conditional liquidity and "firm up" orders received from and on trades with the Sponsored User. CODA Markets requires each Subscriber to be reviewed and approved by a Principal of CODA Markets before accessing the ATS services. Prior to that approval, CODA Markets, as part of its onboarding process, works with new Subscribers to build an understanding of their order flow profile and expected usage of the platform. In addition to a review of the Subscriber Agreement and accompanying paperwork for completeness, CODA Markets' Compliance Department performs a screening of each new Subscriber, its associated persons and direct and indirect owners. New Subscribers are screened for solvency, regulatory disclosures, lines of business, key personnel, AML, sanctions, anti-corruption and negative news. In conjunction with the screening, CODA Markets Compliance Department will access information provided by the Subscriber, such as size of the firm, assets under management, type of orders, e.g., retail, institutional, types of securities to be traded, expected average per order share size, per order notional, number of orders per day, and frequency of orders for the purpose of establishing risk management control settings as required under SEC rule 240.15c3-5 (additional information can be found in Part III, Item 8(a)). A Subscriber will be denied access to the ATS services for having no Rule 15c3-5 market access checks, significant regulatory disciplinary actions, anti-money laundering violations, financial instability that if otherwise approved, could cause a disruption to the ATS services or its Participants. Subscribers that are not registered broker-dealers are required to have $50 million or more in assets under management and a qualifying prime brokerage or custodial agreement to be approved to access the ATS services. CODA Markets' Subscriber Agreements require unique attestations for Broker-Dealer Subscribers and Institutional Subscribers as appropriate for each firm type. 

CODA Markets maintains the right to exclude, at its discretion, Participants from using any feature of the ATS including access to CODA, use of specific auction and order types, acting in the capacity of a Liquidity Seeker or Liquidity Provider, entering or interacting with conditional liquidity, access to Request-for-Trade "(RFT")/Auction Alert feeds and use of the router. CODA Markets reserves the right to modify this list at any time. Examples of why CODA Markets may choose to exclude a Participant include, but are not limited to the following: - CODA Markets determines a Participant's usage of the system to be a risk to the CODA systems and/or other Participants. - A Participant's firm up rate to conditional invites falls below expected levels (as further described in Part III, Item 9). - A Participant receiving RFTs or Auction Alerts (via FIX, OMS/EMS) shows no intent to participate (as further described in Part 3, Item 9). - A Subscriber loses their FINRA (or other SRO) membership. - A Subscriber fails to meet their settlement obligations. 

CODA executes trades in the capacity of a NMS Stock ATS between the hours of 9:30:00 A.M. ET and 4:00:00 P.M. ET. The CODA BLOCK auction type does not allow initiation of a new auction after 3:59:00 P.M. ET. CODA accepts orders and conditional liquidity as early as 4:00:00 A.M. ET, and executes at away trading centers via its router FLARE. At the Subscribers' discretion, orders received prior to 9:30:00 A.M. ET may be accepted and held by CODA until 9:30:00 A.M. ET. At that time, the orders become eligible for execution. At 4:00:00 P.M. ET, CODA cancels all orders and conditional liquidity at CODA. Subscribers utilizing CODA's outbound router, FLARE, and wishing to trade in the "post-market" may have orders routed to away trading centers where orders are eligible for "post-market" execution. CODA accepts orders until 8:00:00 P.M. ET and executes via its router FLARE. At 8:00:00 P.M. ET all open orders are cancelled. CODA accepts orders until 8:00:00 P.M. ET and executes via its router FLARE. At 8:00:00 P.M. ET all open orders are cancelled. 

CODA requires all orders and conditional liquidity to be entered via Financial Information eXchange ("FIX") protocol. CODA supports both FIX 4.2 and 4.4. 

As described in Part II, Item 6(a) above, Apex is a software development company that provides certain hardware, software, and data assistance to CODA Markets pursuant to the MSA. As part of the MSA, Apex will host the CODA ATS in data center space provided by Apex. In addition, Apex provides cabinet space to Apex Clearing Corporation (a subsidiary of Apex) in the same co-location space in which the CODA ATS is hosted. The Apex Clearing Corporation equipment is not used for entering orders in the CODA ATS, interacting with the CODA ATS, or using any services offered by CODA Markets. This equipment will be co-located with CODA ATS, but will be unable to communicate with CODA ATS. CODA offers several cross connect options at the co-location facility where CODA's systems reside. NY5 offers connectivity to CODA systems, and NY5 also hosts CODA matching engines. Cross connects can be intra-datacenter (cage-to-cage). CODA Markets' networking, sales and operations team discuss cross connect and related services with Participants wanting to connect via cross connect. Each configuration is agreed to in advance. A Letter of Authorization ("LOA") is provided to the firm ordering the cross connect. The LOA is provided to the data center as part of the cross connect order request. Standard options for cross connects are based on available cross connect options provided by the datacenter co-location facility and currently supported/owned Apex equipment located at the co-location facility. As part of the MSA, Apex will make available to CODA various cross connect options at NY5, located at 800 Secaucus Road, Secaucus, New Jersey 07094, including the following (Connection Service; Media Type; Protocol Type; Connection Type; Speed): - Single-Mode Fiber; Single-Mode Fiber; 10 GIG ETHERNET; Fiber; 10 GbE - Single-Mode Fiber; Single-Mode Fiber; GIGABIT ETHERNET; Fiber; 1 GbE - Multi-Mode Fiber; 50 MICRON MULTI-MODE FIBER OM3; 10 GIG ETHERNET; Fiber; 10 GbE - Multi-Mode Fiber; 50 MICRON MULTI-MODE FIBER OM3; GIGABIT ETHERNET; Fiber; 1 GbE - Multi-Mode Fiber; 62.5 MICRON MULTI-MODE FIBER; GIGABIT ETHERNET; Fiber; 1 GbE - UTP; CAT6; FAST ETHERNET; Copper; 100 Mbs - UTP; CAT6; GIGABIT ETHERNET; Copper; 1000 Mbs - UTP; CAT6; ETHERNET; Copper; 10 Mbs UTP; CAT5e; FAST ETHERNET; Copper; 100 Mbs - UTP; CAT5e; GIGABIT ETHERNET; Copper; 1000 Mbs - UTP; CAT5e; ETHERNET; Copper; 10 Mbs The terms, conditions and available cross connect options provided above are the same for all Subscribers, Affiliates, and the Broker-Dealer Operator. Subscribers' systems may not support or be compatible with all available options. It is for these reasons that CODA offers multiple options and works closely with Participants while adding new or modifying existing connectivity. 

CODA operates on an on-demand order-initiated, auction-based market structure offering three Auction Types, CODA MICRO, CODA BLOCK and CODA FUSE. Each Auction Type supports certain order types and may handle order types differently based on the Auction Type and capacity ("Liquidity Seeker" vs. "Liquidity Provider" as designated by FIX tag) in which an order is interacting on the ATS. Subscribers can review, complete and submit CODA's "Auction Order Handling Configuration Request Form" which provides an overview of CODA ATS order handling defaults for orders, conditional interests and firm up orders (all of which are also discussed extensively in Form ATS-N). Customized order handling can be requested via the form and the available options are also listed in Part III, Item 11.c of Form ATS-N. The form is available on the CODA website (www.codamarkets.com) and applies to non-FLARE eligible (non-routable) orders from Liquidity Seekers. Unless otherwise requested by a Subscriber when setting up their FLARE routing strategy, CODA Markets retains discretion on CODA ATS auction type and auction order handling configuration for Subscribers when using routable FLARE eligible strategies. CODA will discuss with the Subscriber and review any specific Participant requests regarding handling of their FLARE eligible (routable) order flow. "Liquidity Seeker" orders and conditional interests participate on CODA by: - Initiating on-demand auctions, or in the case of conditional interests, removing liquidity via the FUSE Auction type; - Resting orders and/or conditional interests to participate in future auctions initiated by other Liquidity Seeker orders; and/or - Liquidity Seeker orders (not conditional interests) using CODA's outbound order router, FLARE. "Liquidity Provider" orders and Inbound IOIs participate on CODA by: - Responding with orders to on-demand auctions initiated by Liquidity Seeker orders; and/or - Resting Inbound Indications-of-Interests ("Inbound IOIs") in the CODA Book to participate in future CODA FUSE auctions CODA MICRO accepts and handles the following order types from Liquidity Seekers: - Limit - Market - Pegged (midpoint, primary, market). Peg Offset is allowed for primary and market pegged orders and discussed in detail in this item below. - Resting - Resting orders reside in the CODA Order Book ("CODA Book") and allow Liquidity Seekers to interact with and execute against order flow from other Liquidity Seekers if the resting order provides executable liquidity to any of the auction types or matching protocols discussed in this document. Resting orders do not have priority over Liquidity Provider responses and are subject to the same price / size / time matching priority used in CODA MICRO auctions (see description in Part III, Item 11(c)). In other words, in CODA MICRO, if two resting orders have the same price and are on the same side, then the resting order with the larger quantity is awarded priority over the smaller resting order, up to the resting order's quantity. In a case where both price and size are equal, priority will be awarded to the resting order with the earlier time stamp of receipt. At CODA's discretion, resting orders can be deemed ineligible to interact with certain CODA MICRO auctions. For example, a Subscriber's negotiated fee for initiating and executing in CODA MICRO may be a rebate higher than the average negotiated fee charged to other Subscribers for resting orders in the CODA Book (see detail on Fees in Part III, Item 19). As a result, CODA Markets would be expected to pay a rebate to the initiating Subscriber that is of a greater amount than what it charged to the Subscriber resting in the CODA Book. Since CODA Markets would lose money on the trade, this is an example of why resting orders can be deemed ineligible for interaction in an initiating Subscriber's CODA MICRO auctions. Conditional - Conditional liquidity from Liquidity Seekers is referred to as "Conditional Interests". Conditional interests and "firm up" orders do not initiate CODA MICRO auctions. Conditional interests allow Liquidity Seekers to provide liquidity to auctions initiated by other liquidity-seeking orders and remove liquidity upon receipt via CODA FUSE (see description in Part III, Item 11(c)). In CODA MICRO auctions, conditional interests and "firm up" orders are deemed a supplemental liquidity source and only trade with residual shares of an auction-initiating order once the CODA MICRO auction is complete. At that time, if an eligible CODA MICRO initiating order is executable against a contra conditional interest then the conditional interest is invited to firm up. Conditional interests may be entered as Market, Limit or Pegged. A conditional interest must be replaced with a firm (Market, Limit or Pegged) order prior to execution. The process of replacing conditional interests with firm orders, known as a "firm up", introduces latency to the execution process. As such, Liquidity Seekers may opt out of interacting with conditional interests and "firm up" orders. Additionally, CODA can opt out certain CODA FLARE-eligible orders of interacting with conditional interests as needed to achieve the execution goals of the specific FLARE strategy and to optimize performance. For example, the performance of certain FLARE strategies could be negatively impacted by the latency of the "firm up" process. CODA can peg Conditional interests to the midpoint of the NBBO by default at the request of the Liquidity Seeker. Conditional interests and firm ups that are tagged for CODA MICRO are eligible to receive invites from and provide liquidity to all other auction types, unless requested otherwise by the Subscriber. CODA BLOCK accepts and handles the following Order Types from Liquidity Seekers: - Market - Market orders are treated as market pegged orders. - Limit Orders - Pegged Orders - Market, primary and midpoint pegged orders are all accepted and are handled the same as pegged orders in CODA MICRO. - Resting - Resting orders greater than or equal to 1,000 shares and residing in the CODA Book are eligible to interact with CODA BLOCK auctions. Resting orders are reserved as participating orders in a CODA BLOCK auction during the Phase 3 Auction Alert (see description of CODA BLOCK in Part III, Item 11 (c)). Conditional - Conditional interests and "firm up orders" can only participate (not initiate) in CODA BLOCK auctions. Conditional interests sent to CODA BLOCK will remove liquidity using the CODA FUSE logic upon receipt (see description in Part III, Item 11(c)). Conditional interest invites will include an indication that the invite is for a CODA BLOCK auction. CODA BLOCK auction conditional interest invites will be sent to all eligible conditional interests in that symbol regardless of side, size and price of the initiating order. The CODA BLOCK invite does not indicate the explicit side, size or price of the initiating order, but instead echoes the information from the conditional interest of the Subscriber receiving the invite. Therefore, the CODA BLOCK invite is deemed to be symbol-only in nature. As with all participating orders, "firm up" orders submitted to a CODA BLOCK auction must be at least 1,000 shares to be eligible. "Firm up" orders must be Limit or Pegged Orders (Market orders will be rejected). Conditional interests whose "firm up" orders are submitted to a CODA BLOCK auction are treated with the same priorities and on the same basis as other participating orders. Due to the multilateral (potential for more than two counterparties to participate in a single auction with one print to the tape) matching rules of CODA BLOCK (discussed in detail in Part III, Item 11 (c)), conditional interests and their subsequent "firm up" orders may not participate in the allocation process due to their limit price, minimum fill quantity or other order instructions even following receipt of an invite. As a result of the symbol-only nature of the CODA BLOCK conditional interest invite, Subscribers may choose to not submit a "firm up" order. Any unfilled shares on a "firm up" order will be cancelled back to the Subscriber at the completion of the auction. Unless requested otherwise, conditional interests and firm ups that are tagged for CODA BLOCK are only eligible to receive invites from and provide liquidity to CODA BLOCK auctions. CODA FUSE accepts and handles the following Order Types from Liquidity Seekers: - Market - Market orders are treated as market pegged orders. - Limit - Pegged Orders - Market, primary and midpoint pegged orders are all accepted and are handled the same as pegged orders in CODA MICRO. - Resting - Resting orders greater than or equal to 100 shares, or of at least $5,000 in in notional value, and tagged for CODA FUSE are eligible to provide liquidity to CODA FUSE auctions as well as all other auction types, unless requested otherwise by the Subscriber. - Conditional - Conditional interests sent to CODA FUSE will, upon receipt, attempt to remove liquidity using the CODA FUSE auction type (discussed in detail in Part III, Item 11 (c)). If a trade opportunity is identified, an invite will be sent to the Liquidity Seeker, as well as other Liquidity Seekers whose conditional interests represent executable liquidity in the CODA FUSE auction. Conditional interest invites will include an indication that the invite is for a CODA FUSE auction. As with all participating orders from Liquidity Seekers, "firm up" orders submitted to a CODA FUSE auction must be at least 100 shares, or of at least $5,000 in notional value, to be eligible. Due to the multilateral (potential for more than two counterparties to participate in a single auction with one print to the tape) matching rules of CODA FUSE (discussed in detail in Part III, Item 11 (c)), conditional interests and their subsequent "firm up" orders may not participate in the allocation process due to their limit price, minimum fill quantity or other order instructions being incompatible even following receipt of an invite. Conditional interests and firm ups that are tagged for CODA FUSE are eligible to receive invites from and provide liquidity to all other auction types, unless requested otherwise by the Subscriber. CODA MICRO, CODA BLOCK and CODA FUSE accept and handle Liquidity Provider orders as follows: - All CODA auction types and matching protocols allow Liquidity Providers to generate firm IOC orders in response to liquidity-seeking order flow. When responding to CODA MICRO "price improvement auctions" and CODA BLOCK RFT/Auction Alerts, the Liquidity Provider responses remain tagged as IOC; however, eligible responses are paused for the full length of the auction in order for CODA to identify and complete the price discovery process (discussed in detail in Part III, Item 11 (c)). - Liquidity Providers may send Pegged Orders (midpoint, market, primary). Peg Offset is allowed for primary and market pegged orders and discussed in detail later in this section. - Liquidity Providers may send orders with discretion offset to provide additional price improvement to their orders. Discretion offset values may be no smaller than $0.01. - At the completion of any CODA auction, unfilled Liquidity Provider responses are cancelled. Liquidity Providers may only enter orders when responding to an RFT/Auction Alert. All Liquidity Provider orders are treated as IOC and are not eligible for routing via FLARE. If Liquidity Providers send Day orders they will be treated as IOC as described above. CODA FUSE accepts and handles Liquidity Provider conditional liquidity as follows: - Conditional liquidity from Liquidity Providers is referred to as "Inbound IOIs". - Inbound IOIs allow Liquidity Providers to express their CODA FUSE trading interests through non-executable messages that rest at CODA. - Inbound IOIs and "firm up" orders may be entered as Limit or Pegged, with or without offset, similar to Liquidity Provider orders (discussed above). - Inbound IOIs are required to contain symbol, side and size, and typically contain price instructions from the Liquidity Provider; however, if price is not present then CODA treats the Inbound IOI as a primary peg (or midpoint peg upon request). - Similar to conditional interests, inbound IOIs are invited to "firm up" their inbound IOI with an order when CODA FUSE identifies a trade opportunity that includes the liquidity represented by the inbound IOI. - Unlike conditional interests, inbound IOIs do not attempt to remove liquidity via CODA FUSE upon receipt, they only respond to invites. - Inbound IOIs are not included in CODA MICRO and CODA BLOCK auctions. Priority is determined by the matching engine logic and rules of engagement of each Auction Type as discussed in Part III, Item 11. Any conditions affecting rank and/or price for execution are defined throughout this Item and in the Auction Type descriptions detailed in Part III, Item 11(c). Orders (non-conditional) tagged for and directed to CODA BLOCK are only eligible to participate in CODA BLOCK auctions. Day orders tagged for and directed to CODA MICRO or CODA FUSE are eligible to participate in CODA BLOCK auctions while resting in the CODA Book and of at least 1,000 shares. Day orders tagged for and directed to CODA MICRO are eligible to participate in CODA FUSE auctions while resting in the CODA Book and of at least 100 shares or $5,000 in notional value. Resting orders and conditional interests are defined as liquidity-providing order types. As a result, Liquidity Seekers using these order types may award price improvement to the contra side counterparty. For purposes of this filing, CODA will refer to "remove liquidity" as initiating an auction and "adding liquidity/resting orders/post-only orders" as participating in auctions/responding orders. Subscribers wishing to trade on CODA strictly by participating in auctions initiated by other Subscribers may do so via the following means: 1) Participate via the Liquidity Provider FIX Specification and/or Inbound IOI FIX Specification 2) Nonmarketable orders by rule do not initiate auctions. Liquidity Seekers sending orders that are nonmarketable, defined by default as buy orders with a limit price less than or equal to NBB or sell orders with a limit price greater than or equal to NBO at the time of receipt, will not initiate auctions. Subscribers may also request to treat orders priced greater than NBB and less than NBO as nonmarketable. Based on Subscriber preference, nonmarketable Day orders may rest in the CODA Book to participate in future auctions or cancel back to the Subscriber. 3) Request a participate only (post-only) configuration. In this case, FIX tags are used on an order-by-order basis as order handling instructions for CODA. 4) Subscribers may instruct CODA to handle an order as a resting order via a custom time-in-force value (Tag 59 = A). As previously discussed, CODA supports pegged orders from both Liquidity Seekers and Liquidity Providers. The supported pegged order types or execution instructions are: - MIDPOINT - Midpoint pegged orders allow the Liquidity Seeker to use any of the auction types or matching protocols to source liquidity at the midpoint of the NBBO or better ("Midpoint Order"). CODA identifies an order as a Midpoint Order in each CODA MICRO RFT/Auction Alert sent to the Liquidity Providers (does not apply to CODA FUSE and CODA BLOCK auctions). When responding to auctions, a Liquidity Provider can send a Midpoint Pegged Order in response. Using both CODA's market data feed and the limit prices (if present) on the Subscribers' orders, CODA matches the Liquidity Seeker and Liquidity Provider(s) at the midpoint of the NBBO and prints to the TRF. - MARKET - Market pegged orders allow Subscribers to instruct CODA to execute its order at the current market price. Market pegged orders maintain a limit price equal to the NBO for buy orders and a limit price equal to the NBB for sell/sell short orders. - PRIMARY - Primary pegged orders allow the Subscribers to instruct CODA to execute its order at a limit price that is relative to the NBBO. Primary pegged orders maintain a limit price equal to the NBB for buy orders and a limit price equal to the NBO for sell/sell short orders. Non-marketable Liquidity Seeker primary pegged orders do not initiate auctions but instead they rest, eligible to participate in future auctions. CODA supports peg offset instructions from both Liquidity Seekers and Liquidity Providers. Subscribers may add offset (at a value no less than $0.01 for stocks priced above $1.00) to market and primary pegged order instructions. This will maintain a limit price above or below the NBBO equal to offset value. Peg offset is supported on Primary and Market pegs only. To provide price improvement to Liquidity Seekers via limit orders, Liquidity Providers can populate an additional FIX tag (discretion offset) in their response. This tag will identify the amount (numeric value) to which they are willing to provide price improvement beyond their limit price. When CODA matches a Liquidity Provider's order indicating a willingness to provide price improvement against a liquidity-seeking order, CODA's matching logic adds the value in that FIX tag to the limit price on the Liquidity Provider's order to calculate the final price for the trade. Liquidity Providers may provide price improvement instructions to limit orders based on their limit price (discretion offset) as well as offset to pegged orders based on the NBBO (peg offset). Except for trading in stocks priced below $1.00, CODA does not accept orders with sub-penny values in the price tag; however, midpoint executions may occur at sub-penny values. Liquidity Seekers may instruct CODA to default orders to a midpoint pegged order type. Pegged orders are treated the same as non-pegged orders in terms of priority. CODA does not adjust limit prices or peg type based on NBBO or other market conditions. Liquidity Providers' orders are not eligible for routing to other Trading Centers. Liquidity Seekers' instruct CODA to route orders to other Trading Centers via FIX tags and as discussed with the Subscriber (verbally, in writing or both) during the onboarding process and ongoing support conversations. Both Day and IOC orders can be eligible for outbound routing. Custom time-in-force values (Tag 59 = 9, Tag 59 = B and 59 = A) in addition to the standard values for Day and IOC orders (Tag 59 = 0 and Tag 59 = 3) are supported by CODA. The custom TIF values instruct CODA to either route or not route orders on an order-by-order basis. Subscribers interested in using custom TIF values can request information from CODA at any time. All auction types allow time-in-force instructions of Day and IOC. A Day order is an order that automatically expires if it is not executed before the end of the trading day on which the order was entered. Subscribers can cancel Day orders at their discretion during the trading day. An IOC order is an order that executes all or part immediately and automatically cancels any unfilled portion of the order. CODA handles IOC orders as follows: Auction-initiating orders with time-in-force instructions of IOC survive for the length of the auction unless successfully cancelled by the Subscriber before the end of the auction. Responding orders to CODA MICRO (Price Improvement Auction), CODA FUSE and CODA BLOCK with time-in-force instructions of IOC can survive for the length of the auction unless successfully cancelled by the Subscriber. Liquidity Provider orders (non-conditional) are all treated as IOC. Time-in-force instructions of Day from Liquidity Provider orders will be accepted, but the order will still be treated as IOC. All orders types can be modified to update price, quantity, order type (limit to market, or vice versa) and side (sell to sell short, or vice versa). Other modifications are not allowed. CODA BLOCK and CODA FUSE orders and/or conditional interests modified to reduce quantity will be rejected if the reduced quantity violates initiating or participation requirements. All order types can be replaced with the allowed modifications identified above. All order types can be cancelled at any time by the Subscriber including during a CODA auction, after a CODA auction, while an order is routing out via FLARE and while an order is resting at CODA or an away trading center. CODA will process cancel requests immediately upon receipt, but executions may occur before the cancel request is fully processed. Order types may be rejected for several reasons including a violation of CODA's FIX specifications, Subscribers' risk limits (discussed in Part III, Item 2) or the product requirements of CODA's three auction types (discussed in detail in Part III, Item 11(c). An order for one auction type cannot by modified or replaced to a different auction type. Availability of order types is not determined by form of physical connectivity to CODA ATS. FIX sessions are, however, configured as either Liquidity Seeker or Liquidity Provider, not both. Subscribers wishing to act in the capacity of both a Liquidity Seeker and Liquidity Provider must do so over unique FIX sessions. Subscribers using third party OMS/EMS vendors or algorithms to enter orders to CODA ATS may be limited with respect to entering orders into CODA based on the limitations of the third-party provider. For example, one EMS vendor may offer its clients pegging functionality while another EMS vendor does not. 

CODA enforces a maximum per order quantity and notional value as part of its inbound order risk checks and 15c3-5 obligations. CODA MICRO: There are no minimum or maximum order quantities based on rules of the matching engine for orders entered in the capacity of a Liquidity Seeker or Liquidity Provider. CODA BLOCK: To initiate CODA BLOCK Liquidity Seekers are required to send a minimum order quantity based on the market capitalization or price of the symbol. The minimum order quantity requirements to initiate CODA BLOCK are as follows: - Small Cap. (market cap. less than or equal to $2B) = 2,000 - Mid Cap (market cap. greater than $2B and less than or equal to $10B) = 5,000 - Large Cap (market cap. greater than $10B) = 10,000 - High-Price (stock price greater than or equal to $100.00/share) = 2,000 To respond to a CODA BLOCK auction, Liquidity Seekers and Liquidity Providers are required to send a minimum quantity of 1,000 shares. The 1,000 share minimum also applies to resting orders, both firm and conditional, in the CODA Book. Resting orders under 1,000 shares are deemed ineligible to participate in a CODA BLOCK auction. There are no maximum quantity rules in CODA BLOCK other than the aforementioned 15c3-5 risk limit. CODA FUSE: CODA enforces a minimum order quantity, or notional value, of either at least 100 shares or $5,000 on all orders from Liquidity Seekers and Liquidity Providers. There is no maximum quantity other than the aforementioned 15c3-5 risk limit. 

CODA MICRO accepts odd-lot orders from Liquidity Seekers and Liquidity Providers. CODA MICRO allows for odd-lot executions. Odd-lots are not allowed or eligible to participate in CODA BLOCK. CODA FUSE accepts odd-lot orders from Liquidity Seekers and Liquidity Providers if the notional value of the order is at least $5,000. CODA FUSE allows for odd-lot executions. 

The CODA MICRO and CODA FUSE auction types accept and process mixed-lot orders and may execute and print mixed lot trades. The CODA BLOCK auction type accepts mixed lot orders, but rounds mixed lots down to the nearest round lot for processing. The odd lot portion of a mixed lot order tagged for CODA BLOCK is cancelled back to the Subscriber following a trade if the residual quantity is less than 1000 shares. 

Request-for-Trade / Auction Alerts: CODA MICRO, CODA BLOCK and CODA FUSE, utilize the on-demand, order-initiated auction market structure. CODA sends "symbol-only" notifications, referred to as Request-for-Trades ("RFT") or Auction Alerts, to other Participants (both Liquidity Providers and other Liquidity Seekers depending on the Auction Type). The RFT/Auction Alert process serves as the auction call and is used to attract liquidity from other Subscribers that will potentially trade with the initiating liquidity-seeking order, as well as resting orders and conditional liquidity. RFT/Auction Alerts may be sent via FIX or third-party vendors such as Bloomberg and various OMS/EMS platforms. The RFT/Auction Alert may be in the form of an IOI FIX message type. IOIs typically contain symbol, side, size and price; however, as previously mentioned, RFTs/Auction Alerts are "symbol-only". For that reason, CODA does not refer to RFTs/Auction Alerts as IOIs other than during FIX messaging discussions. For detailed information regarding RFTs/Auction Alerts, including what information can be found in a RFT/Auction Alert, please refer to Part III, Item 11 (a) and (c). Conditional Liquidity (Conditional Interests and Inbound IOIs): Conditional interests allow Liquidity Seekers to express interest with symbol, side, and size (price is required if Limit order type, but not required if Market or Pegged order type) to provide liquidity to on-demand auctions. Conditional interests reside in the CODA Book. Subscribers can tag conditional interests to receive invites to firm up from one or more auction types. The invite type (based on auction type) is identified in a FIX tag. Invites are generated by a live auction event (discussed in detail in Part III, Item 11(c)). Only firm (non-conditional) orders cause CODA MICRO and CODA BLOCK invites to be sent. Firm orders and other conditional interests cause CODA FUSE invites. Subscribers can tag conditional interests as market, limit or pegged orders. Following receipt of an invite, a Subscriber must send a firm up order to the invite within approximately 28 milliseconds to be eligible for execution. The order type, quantity and price on the firm up may be modified from the conditional interest, but they must comply with the auction types' standard rules (discussed in detail in Part III, Item 11(c)). The reasons a Subscriber would modify their firm up order include a decision by the Subscriber to increase or decrease quantity and/or price. CODA can peg conditional interests and corresponding "firm up" orders to the midpoint of the NBBO by default at the request of the Liquidity Seeker. Inbound IOIs allow Liquidity Providers to express interest to provide liquidity to CODA FUSE auctions. Inbound IOIs reside in the CODA Book. Inbound IOIs are eligible to receive invites from CODA FUSE auctions, exclusively. The CODA FUSE invite type is identified in the FIX tag. Firm orders and other conditional interests generate CODA FUSE invites. Subscribers can tag Inbound IOIs as limit or pegged. Following receipt of an invite, a Subscriber must send a firm up order to the invite within approximately 1 millisecond to be eligible for execution. Inbound IOI responses that come after 1 millisecond will be rejected. If the Inbound IOI fails to respond it is cancelled. The order type, quantity and price on the firm up may be modified from the Inbound IOI, but they must comply with the CODA FUSE rules (discussed in Part III, Item 11(c)). The reasons a Subscriber would modify their firm up order include a decision by the Subscriber to increase or decrease quantity and/or price. - In CODA MICRO, conditional interests are deemed a supplemental liquidity source and only trade with residual shares from an auction-initiating order once the auction is complete. Conditional interests showing an executable contra side interest are invited to firm up at that time, based on price / size / time priority, in sequential order. The information in the invite echoes the symbol, side and price from the invited conditional interest. The size on the invite reflects the requested quantity to be firmed up, which may be less than or equal to the quantity on the invited conditional interest, based on the quantity of residual shares from the CODA MICRO initiating order. The process of replacing conditional interests with firm orders, known as a "firm up," introduces latency to the execution process. As such, conditional interests may not be eligible to interact with some liquidity-seeking orders. For example, a Liquidity Seeker may request (opt out) that their CODA MICRO initiating orders do not interact with conditional interests and firm up orders because they do not want to wait up to 28 milliseconds for the conditional Participant to respond with a firm up order. The Liquidity Seeker order is not eligible for interacting with other orders in CODA while CODA waits for the "firm up" order following an invite. Additionally, a latency sensitive FLARE routing strategy may be less effective if subjected to the additional pause of up to 28 milliseconds during the "firm up" process following the initial CODA MICRO pause as detailed in Part III, Item 11 (c). - CODA FUSE invites to firm up are sent by the CODA system to Participants with conditional interests and/or Inbound IOIs in the CODA Book when a potential match is identified based on available liquidity represented by the liquidity removing order or conditional interest, resting firm orders and other conditional liquidity in the CODA Book at that time. Conditional liquidity showing an executable interest is invited to firm up based on the CODA FUSE volume-weighted pro-rata allocation and matching process (discussed in detail in Part III, Item 11(c)). The information in the invite echoes the symbol, side and price from the invited conditional interest(s) and/or Inbound IOI(s). The size on the invite reflects the requested quantity to be firmed up, which may be less than or equal to the quantity on the invited conditional liquidity, based on the quantity of shares initially allocated during the CODA FUSE allocation and matching process. - Participants using conditional interests and/or Inbound IOIs in CODA MICRO and/or CODA FUSE are expected to maintain a firm up rate over 80%. CODA Markets monitors daily and monthly firm up rates across all Participants. Unless CODA is aware of a known reason for a monthly firm up rate less than 80% for the previous month, CODA will contact the conditional Participant and request an explanation. CODA will work with the Participant (i.e., additional testing, review of examples, etc.) to improve the firm up rate. If the conditional Participant fails to improve their firm up rate, CODA reserves the right to disable the Participant's usage of conditional liquidity as discussed in Part III, Item 3(a). - CODA BLOCK auction conditional interest invites will be sent to all eligible conditional interests in that symbol regardless of side, size and price of the initiating order. Eligible conditional interests for CODA BLOCK are conditional interests of at least 1,000 shares. Additionally, Participants can tag conditional interests to opt out of receiving CODA BLOCK invites. The information on the invite echoes the order detail (symbol, side, size, price) from the conditional interest. Conditional interests whose "firm up" orders are submitted to a CODA BLOCK auction are treated with the same priorities and on the same basis as other participating orders. Following receipt of a CODA BLOCK invite, due to the multilateral matching rules of CODA BLOCK (discussed in detail in Part III, Item 11 (c)), conditional interests and their subsequent "firm up" orders may not participate in the allocation process due to the terms and conditions of the firm up order, such as limit price, minimum fill quantity or other order instructions. As a result of the symbol-only nature of the CODA BLOCK conditional interest invite, Subscribers may choose to not submit a "firm up" order following receipt of a CODA BLOCK invite. Any unfilled shares on a "firm up" order will be cancelled back to the Subscriber at the completion of the auction. By default, conditional interests will attempt to remove liquidity upon receipt using the CODA FUSE auction type (discussed in detail in Part III, Item 11(c)) if CODA identifies an indicative trading opportunity based on the conditional interest and resting orders/conditional liquidity in the CODA Book. Subscribers sending conditionals can customize the handling of their conditional interests through the "Auction Order Handling Configuration Request Form" that is available upon request and on the CODA website (www.codamarkets.com). Available order handling customizations are also listed in Part III, Item 11.c. By rule, inbound IOIs do not attempt to remove liquidity upon receipt. Inbound IOIs are a participate-only order type. 

CODA opens for trading in the capacity of an ATS each trading day at 9:30:00 ET A.M. for all Reg NMS stocks as defined by Regulation NMS rule 600(b)(34) which defines a listed equity security as any equity security listed and registered, or admitted to unlisted trading privileges, on a national securities exchange. Upon request, Liquidity Seekers may enter orders and conditional interests prior to 9:30:00 A.M. ET to be held at the ATS until 9:30:00 A.M. ET at which time they will initiate an on-demand auction, route out or rest in the CODA Book to participate in future auctions. Liquidity Providers can enter Inbound IOIs prior to 9:30:00 A.M. ET. Inbound IOIs entered prior to 9:30:00 A.M. ET rest in the CODA Book, eligible to participate in CODA FUSE auctions starting at 9:30 A.M. ET. CODA does not use any special order acceptance, handling, or execution procedures at the open, during a re-open or following stoppage of trading during regular trading hours. At the open, during a re-open or following a stoppage, CODA accepts, handles, and executes orders and conditional liquidity as described in Part III, Item 11(c). 

At the start of regular trading hours, CODA handles unexecuted orders as described in Part III, Item 11(c). Any auction-initiating orders that were held at the ATS until the open (as described in Part III, Item 10(a)) will initiate an auction at that time. Following a stoppage of trading in a security during regular trading hours, unexecuted orders and trading interests in CODA are made available for execution. Unexecuted orders will not reinitiate an auction, but any resting orders and conditional liquidity may participate in future auctions as described in Part III, Item 11(c). 

CODA, which is operated by CODA Markets, identifies and executes orders that can be matched or crossed in an agency capacity via CODA's on-demand, order-initiated auction matching protocols for all Reg NMS stocks. To address the varying liquidity needs and diverse workflows of its Participant base, CODA offers three auction types, CODA MICRO, CODA BLOCK and CODA FUSE, which are discussed individually and in detail below. As described in Part II, Item 6(a) above, Apex is a software development company that provides certain hardware, software and data assistance to CODA Markets pursuant to the MSA. Apex provides CODA Markets licensed technology and software used to operate CODA. Apex is responsible for the maintenance and continued development of the technology and software. Apex will also provide operational and administrative support to CODA. All three auction types, CODA MICRO, CODA BLOCK and CODA FUSE, utilize the on-demand, order-initiated auction market structure. Individual auctions are initiated by unique Liquidity Seeker orders. Only Liquidity Seeker orders deemed "marketable" upon receipt can initiate auctions. For purposes of auction initiation, "marketable" is defined as Buy orders priced greater than the national best bid and Sell/Sell Short orders priced less than the national best offer. Initiating orders are paused at CODA while the auction process occurs (the "Pause"). Once an auction is initiated, CODA sends "symbol-only" notifications, referred to as Request-for-Trades ("RFT") or Auction Alerts, to other Participants (both Liquidity Providers and other Liquidity Seekers depending on the Auction Type). The RFT/Auction Alert process serves as the auction call and is used to attract liquidity from other Participants that will potentially trade with the initiating liquidity-seeking order, as well as resting orders and conditional liquidity. To minimize information leakage and protect initiating Liquidity Seekers' orders, the information included in RFT/Auction Alerts sent to Participants is limited to the ticker symbol from the initiating Liquidity Seekers' orders. Form ATS-N and other CODA materials refer to this RFT/Auction Alert format as "symbol only." Participants can receive additional information related to the trading opportunity on RFT/Auction Alerts, including a commission amount to be assessed if a trade occurs, midpoint pegging instructions (not supported in CODA FUSE and CODA BLOCK), and/or the duration of the auction type or matching engine logic for the corresponding auction (discussed in detail in Part III, Item 11 (c)). Exclusive to CODA MICRO and in order to provide Liquidity Seekers with additional flexibility, they can request in writing that CODA send RFT/Auction Alerts containing their full order detail (symbol, side, size and price) to one or more Liquidity Provider Participants instead of the default "symbol only" format. RFT/Auction Alerts sent to Liquidity Providers indicate a required minimum response size based on auction type and as stated below: -CODA MICRO indicates a minimum response size of 1 share. -CODA BLOCK indicates a minimum response size of 1,000 shares. -CODA FUSE indicates a minimum response size of 100 shares, or an amount less than 100 that would satisfy the $5,000 minimum notional value requirement and is calculated based on the midpoint of the NBBO at the time. Liquidity Seekers can rest orders in the non-displayed CODA Book. To rest orders in the CODA Book, Liquidity Seekers send Day orders or use custom TIF values as discussed in Part III, Item 7. CODA auctions reserve orders from the CODA Book if and when the resting orders are executable in auctions initiated by other liquidity seeking orders. Orders resting in the CODA Book are referred to as "resting orders". Conditional interests also reside in the CODA Book. Unlike resting orders where the resting orders can participate in an auction with no further action by the Subscriber, Conditional interests are required to firm up in order to participate in an auction (discussed in detail in Part III, Item 9). 

CODA MICRO: During a CODA MICRO on-demand auction a liquidity seeking order is routed to CODA and subjected to a Pause of up to and approximately 1 millisecond (default), or as determined and specified by the Liquidity Seeker. Liquidity Seekers may opt to lengthen the Pause time. Following receipt of the order and standard risk checks, a RFT/Auction Alert is sent to all Liquidity Providers simultaneously and anonymously (unless directed otherwise by Liquidity Seeker as discussed in Part III, Item 14 (a)). Any executable contra side liquidity generated from the Liquidity Providers and/or resting orders reserved from the CODA Book during the Pause is crossed with the initiating order based on one of two CODA MICRO matching protocols as directed by the initiating Liquidity Seeker via a predetermined FIX tag and order handling configuration: 1) "First-to-respond-first-to-trade" (time priority for Liquidity Provider responses and resting orders): a. Liquidity-seeking orders tagged to use CODA MICRO's "first-to-respond-first-to-trade" protocol trade with Liquidity Provider responses and resting orders on a first-come, first-served basis provided that the response is at or inside the National Best Bid and Offer ("NBBO") and at or better than the initiating order's limit price. b. Executed trades print individually to the Trade Reporting Facility ("TRF") as they occur. For example, a liquidity-seeking order configured for a 1ms Pause may execute and print in 750 microseconds if a Liquidity Provider responds with executable contra side liquidity within that timeframe. 2) "Price improvement auction" (price / size / time priority for Liquidity Provider responses and resting orders): a. Liquidity-seeking orders tagged to use CODA MICRO's "price improvement auction" protocol trade with Liquidity Provider responses and resting orders at the end of an auction order entry period (the default is approximately 1 millisecond) b. During the Pause, CODA assembles the eligible Liquidity Provider responses and resting orders based on price / size / time priority into an Auction Book. c. Orders in the Auction Book are non-displayed and non-executable until the end of the auction. d. Orders in the Auction Book may be cancelled or replaced during the auction order entry period. e. At the end of the order entry period the Auction Book is closed and all orders are deemed firm. f. CODA rechecks the NBBO. The auction matching logic calculates the final execution price or prices for the trade(s) based on price / size / time priority. g. The liquidity-seeking order first trades against the best priced order that arrived in response to the RFT/Auction Alert during the Pause or resting order from the CODA Book, then moves to the second-best priced order, if necessary, and so on until the entire liquidity-seeking order is filled, cancelled back, sent to the CODA Book or routed out as directed by the Liquidity Seeker. In cases when multiple responses and/or resting orders have the same price, priority will first be awarded to the response or resting order with the largest quantity. If both price and size are equal, priority is awarded to the order with the earliest time stamp of receipt. h. Trades are individually printed to the TRF at the completion of the auction. i. RFT/Auction Alerts for "price improvement auction" CODA MICROs are identified as such to encourage price competition and so that Liquidity Providers do not interpret the additional latency as a system defect or error. Additional CODA MICRO rules include: - Multiple CODA MICROs in the same symbol can run simultaneously. - Minimum fill Quantity instructions are supported and satisfied one-to-one (no aggregation). - Liquidity Seekers and Liquidity Providers may enter orders with quantities within their established risk limits, including odd lots. - Resting orders are eligible to participate in CODA MICRO. - "Firm up" orders from invited conditional interests (discussed in detail in Part III, Item 9) may be eligible to interact, based on price / size / time priority, with residual shares on the Liquidity Seeker's order following a CODA MICRO. - Trades print to the TRF as individual prints. - Any price improvement is awarded to the initiator. - CODA MICRO trades are priced at or within the NBBO. The "Auction Order Handling Configuration Request Form" mentioned in Part III, Item 7(a) and available on the CODA website (www.codamarkets.com) allows for the following CODA MICRO customizations: Available order handling customizations for firm orders tagged for CODA MICRO include: a) Opt out of interacting with conditional liquidity. b) Opt out of eligibility to trade in other auction types while resting (post auction). Available order handling customizations for conditional interests tagged for CODA MICRO include: a) Opt out of removing liquidity via CODA FUSE upon receipt (see CODA FUSE detail below). b) Opt out of receiving invites from other auction types while resting. CODA, the ATS, via its router, FLARE, allows Liquidity Seekers, at their discretion and as described in Part II, Item 7(a), to route orders to external trading centers, including exchanges, ATSs, Single Dealer Platforms, and brokers. CODA MICRO orders are eligible to be routed via FLARE either as residual liquidity from an initiating CODA MICRO order or as a non-marketable CODA MICRO order. Subscribers can choose not to have orders enter the ATS via FLARE prior to being routed externally for execution. Subscribers may also instruct orders to be sent to other trading centers before (or instead of) initiating an auction at CODA. All outbound routing via FLARE is at the discretion and direction of the Liquidity Seeker Subscriber. When an order is being routed by FLARE, such order does not participate in the CODA auction process. An unexecuted order routed by FLARE may, consistent with the instructions of the Subscriber, be re-entered into CODA and participate in CODA's auction process. Depending on Subscriber preference, The ATS and FLARE utilize the same FIX connections to receive messages from and send messages to Subscribers. As such, a Subscriber wishing to modify or cancel an order will send the same message regardless of whether the order is being handled by the ATS or FLARE at the time of the modification or cancellation. CODA BLOCK: CODA BLOCK is CODA's on-demand block auction type. CODA BLOCK utilizes a multilateral, call auction price discovery model, providing trading opportunities for large orders and latent liquidity which may reside outside the NBBO, and therefore may execute outside the NBBO. As described below, CODA BLOCK and CODA are compliant with Rule 611 of Regulation NMS. A 30-second Pause serves as the approximate time length of the auction and order entry period during which orders are entered by Subscribers into a non-displayed auction order book. The CODA BLOCK matching algorithm (see "Pricing, Share Allocation and Trade Reporting" below) uses a series of rules resulting in a varying time-to-print at the end of the 30-second order entry window; therefore, 30 seconds is the approximate length of a CODA BLOCK auction. The CODA BLOCK auction process contains four stages: 1) Auction Initiation 2) Auction Alert & Participation 3) Auction Pricing, Share Allocation and Trade Reporting 4) Post Auction Auction Initiation - A CODA BLOCK eligible (as described below) order is sent to CODA and triggers the start of a CODA BLOCK auction. Only one CODA BLOCK auction can be in progress at a time for each symbol. A snapshot of the NBBO is taken at this time. Liquidity Seeker orders can initiate CODA BLOCK during the Core Trading Session with firm orders up until 3:59:00 P.M. Eastern Time. No CODA BLOCK auctions will be initiated after that time. As with other auction types only Buy orders priced greater than the NBB and Sell/Sell Short orders priced less than the NBO upon receipt are eligible to initiate a CODA BLOCK auction. A minimum order quantity is required to initiate CODA BLOCK based on the following criteria (market capitalization data is updated in the morning of each trading day): - Large Market Capitalization (greater than $10 billion market capitalization). Initiation order size must be at least 10,000 shares. - Middle Market Capitalization (greater than $2 billion and up to $10 billion market capitalization). Initiating order size must be at least 5,000 shares. - Small Market Capitalization or Smaller ($2 billion or smaller market capitalization). Initiating order size must be at least 2,000 shares. - "High Price" (Reg NMS stocks priced greater than or equal to $100.00 per share) are subject to the aforementioned Small Market Capitalization requirements. - Odd lot orders are not accepted in CODA BLOCK auctions and will be rejected. - Mixed lot orders are accepted in CODA BLOCK auctions, but only the round lot portion will be eligible for participation in CODA BLOCK auctions. The odd lot portion of a mixed lot order tagged for CODA BLOCK is cancelled back to the Subscriber following a trade if the residual quantity is less than 1000 shares. Stocks priced less than $1.00 are not eligible for CODA BLOCK and orders in these stocks will be rejected. - If the NBB is less than $1.00 upon receipt of an initiating order, the order will be rejected. - No CODA BLOCK auction will execute with a trade price less than $1.00 (CODA BLOCK auction pricing is discussed below). Following successful eligibility and CODA standard risk checks on the initiating order the "30-second" order entry period begins (discussed further under "Auction Alert & Participation" below) and no further CODA BLOCK auctions can be initiated in that symbol until the end of the current CODA BLOCK auction. All CODA BLOCK auction orders received in that symbol while a "30-second" order entry period is open are included in the existing CODA BLOCK auction for that symbol as "participating orders" (discussed further below). CODA will monitor for repeated cancelling by initiators and will address and take action by disabling a Participant's access to CODA BLOCK as it deems necessary. Auction Alert & Participation - A successful initiation of a CODA BLOCK auction is followed by the distribution of CODA BLOCK Auction Alerts and the opening of a "30-second" order entry period. CODA distributes Auction Alerts to its Participants (both buy-side and sell-side) using its "symbol only" RFT, similar to CODA MICRO. The alerts notify Participants that a CODA BLOCK auction has been initiated in that symbol and is in progress. Participants (both Liquidity Seekers and Liquidity Providers) can receive Auction Alerts at three distinct times, in order to accommodate the varied trading workflow needs and latency sensitivities of CODA and CODA BLOCK's diverse Participant community. The first of the three Auction Alerts, Phase 1 Auction Alert, is sent at the start of this stage. Auction Alerts are distributed to Participants via IOI, Instant Message ("IM"), OMS/EMS platforms, direct FIX connections and other third-party messaging platforms and networks. If any alert distribution platforms or networks require "Side" in their specification, then CODA will send both a Buy Auction Alert and a Sell Auction Alert to the platform or network to avoid disclosing the direction of the initiating order. The Auction Alerts can also include the start and stop time for the order entry period. Orders received during the order entry period are placed in the CODA BLOCK auction order book for that symbol as participating orders. There is no time priority in the auction pricing process (allocation rules are described later in this document); therefore, a Subscriber can respond to any of the three Auction Alerts at any time. CODA BLOCK enforces the following requirements on participating orders: - Participating orders may be priced below, at, inside or above the NBBO. - A minimum order quantity of 1,000 shares is required for a participating (responding) order. - Resting orders and "firm up orders" from invited conditional interests are eligible for participating in CODA BLOCK auctions if they meet the aforementioned criteria. The Phase 2 and Phase 3 Auction Alerts are designed to accommodate quantitative, algorithmic and conditional interest Participants. The Phase 2 Auction Alert is sent approximately 29.972 seconds after the Phase 1 Auction Alert. This time is also approximately 28 milliseconds prior to the end of the "30-second" order entry period. The Phase 2 Auction Alert is the invite to all eligible conditional interests. The Phase 3 Auction Alert is the final Auction Alert and is sent 1 millisecond prior to the end of the "30-second" order entry period. Resting orders in the CODA system that are CODA BLOCK auction eligible are reserved for the auction book at this time. The Auction Alerts are sent to Participants according to the following schedule: - Phase 1 Auction Alert: Time ~0 seconds - Phase 2 Auction Alert: Time ~29.972 seconds (29 seconds and 972 milliseconds). - Phase 3 Auction Alert: Time ~ 29.999 seconds (29 seconds and 999 milliseconds). Participating orders in the auction order book may be entered, replaced or cancelled at any time during the order entry period. All participating orders in the CODA BLOCK auction order book are non-displayed. All participating orders and the initiating order are not executable until the end of the "30-second" order entry period. The stage is complete at the end of the "30-second" order entry period. At that time all participating orders in the auction order book are deemed firm and cannot be cancelled. An initiating order can be replaced with an order that doesn't qualify as an initiating order, but does qualify as a participating order; however, the replaced order will forfeit its initiator priority. Auction Pricing, Share Allocation and Trade Reporting - After the thirty-seconds, which includes the aforementioned initiation, alert and response processes, the CODA BLOCK auction matching logic determines the price for the auction, the allocation of shares to each Participant, and the sending of trade reports as required to a TRF. CODA rechecks the NBBO to establish the current NBBO for pricing and allocation as well as identifying the protected markets' "top of book" should the CODA BLOCK auction be priced outside the NBBO requiring CODA to fulfill any Rule 611 of Regulation NMS obligations. All CODA BLOCK auction eligible orders are aggregated in the CODA BLOCK auction order book at their most aggressive (i.e., highest priced Buy orders/lowest priced Sell/Sell Short orders) price levels. Since a CODA BLOCK auction is a multilateral trading environment that allows multiple buy orders and multiple sell/sell short orders to compete in a single auction, there may be multiple orders to buy and sell up to or down to any given price level. Pricing: CODA BLOCK's auction pricing logic determines the single price where the most aggregated buy shares can trade with the most aggregated sell/sell short shares while taking into consideration all of the following: 1) All Limit prices. 2) All Pegged Orders, the limit price on the pegged orders and any peg offset value specified on the order (Pegged orders are pegged to the NBBO snapshot taken at the end of the order entry period). 3) Minimum Fill Quantity instructions (CODA BLOCK satisfies Minimum Fill Quantity instructions) a. Unless Subscriber specifies another value on the order, CODA BLOCK enforces a default 100 share minimum fill quantity instruction on all initiating and participating orders. 4) Maximum contra is not supported in CODA BLOCK (discussed later in this Form). 5) Self-trade prevention is not supported in CODA BLOCK, but is actively monitored by CODA. CODA addresses self-trade concerns with Subscribers directly as needed. 6) CODA BLOCK's Passive Order Rule ("POR") a. Only applied when the auction price will be outside the NBBO. b. Designed to prevent an order that is small in size and passive in price from having an undue influence on the auction trade price (when compared to the aggregate share volume of orders on the passive side of the auction trade). c. The POR establishes a threshold to determine which, if any, passive (non-marketable) orders should be excluded from participating in a specific CODA BLOCK auction. d. The POR inputs include all orders eligible to participate on the passive side of a CODA BLOCK auction and the share-weighted average price of these orders collectively. The POR threshold is established and defined as twice the distance of the aforementioned share-weighted average price from the NBBO midpoint. The NBBO used for the calculation is from the NBBO snapshot taken at the end of the order entry window. Any orders priced beyond the threshold in a given auction are excluded and will not receive any allocation in that CODA BLOCK auction. All orders on the passive side of a CODA BLOCK auction are subject to the POR if the CODA BLOCK auction is to be priced outside of the NBBO. 7) CODA BLOCK's Liquidity Protection Rule ("LPR") a. Only applied when the auction price will be outside the NBBO. b. Designed to prevent an auction trade from executing at an unreasonable distance outside the spread given the size of the execution and the liquidity profile of the symbol. c. The LPR is driven by an equation that is calibrated individually for every Reg NMS stock based on the pattern of its trades over the last twenty trading days (unlike the POR which uses a static formula for each auction). The calibration methodology is designed to reflect the typical price variance of each stock as a function of its notional turnover. The LPR takes the size of a potential CODA BLOCK print as an input and returns the maximum distance the CODA Block engine will allow the auction to go up outside the NBBO as the output. d. If the auction trade price would be outside of that threshold, the orders passively priced outside of that threshold are deemed ineligible and the auction is repriced and reallocated. e. As discussed in Part II, Item 5(c), registered users of the LPRC can enter an NMS stock symbol and auction trade quantity, and the LPRC output is a numerical and graphic representation of the Auction Trade Price band used by the Liquidity Protection Rule ("LPR") in CODA BLOCK on that trading day. Registered users of the LPRC may request a daily file containing the same LPR output data available on CODA Markets' website. That file may be delivered via FTP or the user's preferred delivery methodology. 8) If CODA BLOCK determines that the maximum number of shares that can trade is equal at multiple price levels, CODA BLOCK prices the auction at the price where the most shares can trade that is closest to the NBBO midpoint from the snapshot taken at the end of the order entry period. Trade Size Requirements: The CODA BLOCK auction trade size must satisfy CODA BLOCK Trade Size Requirements as follows: 1) CODA BLOCK auctions with an execution price at or within the NBBO: a. Large Market Capitalization (greater than $10 billion market capitalization): The Auction trade size minimum is 5,000 shares. If the CODA BLOCK auction price and share allocation results in an auction trade that is less than 5,000 shares, the CODA BLOCK auction and all related orders are canceled. b. Middle Market Capitalization (greater than $2 billion and up to $10 billion market capitalization): The Auction trade size minimum is 1,000 shares. If the CODA BLOCK auction price and share allocation results in an auction trade that is less than 1,000 shares, the CODA BLOCK auction and all related orders are canceled. c. Small Market Capitalization or Smaller ($2 billion or smaller market capitalization): The Auction trade size minimum is 1,000 shares. If the CODA BLOCK auction price and share allocation results in an auction trade that is less than 1,000 shares, the CODA BLOCK auction and all related orders are canceled. d. "High Price" (Reg NMS stocks priced greater than or equal to $100.00 per share) are subject to the aforementioned Small Market Capitalization requirements. 2) CODA BLOCK auctions with an execution price outside the NBBO: a. Large Market Capitalization (greater than $10 billion market capitalization): The Auction trade size minimum is 10,000 shares. If the CODA BLOCK auction price and share allocation results in an auction trade that is less than 10,000 shares, CODA BLOCK reprices the auction without the passively priced orders in the auction book to determine if a trade can occur at or within the NBBO. If not, the CODA BLOCK auction and all related orders are canceled. b. Middle Market Capitalization (greater than $2 billion and up to $10 billion market capitalization): The Auction trade size minimum is 5,000 shares. If the CODA BLOCK auction price and share allocation results in an auction trade which is less than 5,000 shares, CODA BLOCK reprices the auction without the passively priced orders in the auction book to determine if a trade can occur at or within the NBBO. If not, the CODA BLOCK auction and all related orders are canceled. c. Small Market Capitalization or Smaller ($2 billion or smaller market capitalization): The Auction trade size minimum is 2,000 shares. If the CODA BLOCK auction price and share allocation results in an auction trade which is less than 2,000 shares, CODA BLOCK reprices the auction without the passively priced orders in the auction book to determine if a trade can occur at or within the NBBO. If not, the CODA BLOCK auction and all related orders are canceled. d. "High Price" (Reg NMS stocks priced greater than or equal to $100.00 per share) are subject to the aforementioned Small Market Capitalization requirements. 3) If CODA's protected markets "top of book" snapshot shows more shares available in aggregate at the protected markets "top of book" than the pending CODA BLOCK auction trade size, then CODA, if possible, will reprice and reallocate the CODA BLOCK auction, not including the passively priced orders outside the NBBO, and price the auction at or inside the NBBO. If not possible, the CODA BLOCK auction and all related orders in the auction are cancelled. If CODA BLOCK Trade Size Requirements are satisfied the allocation process is affected as described below. Primary Allocation: If an initiating or participating order is priced at or through the auction trade price, the order will be allocated shares from the auction order book as follows: 1) The initiating order receives 100% allocation priority. a. If the initiating order's limit price, minimum fill quantity or other order instruction prevents it from trading at the auction's trade price, then the initiating order will not be included in the allocation process. (If an initiating order is not included in the CODA BLOCK auction allocation process due to its limit price or other order instructions, it will not result in the cancelation of the auction.) 2) Participating orders receive a quantity weighted pro-rata allocation. a. If a participating order's limit price, minimum fill quantity or other order instruction prevents it from trading at the auction's trade price, then the participating order will not be included in the allocation process. b. Multiple orders from the same Subscriber on the same side are not aggregated for pro-rata allocation and calculation purposes. 3) If the auction price is outside the NBBO, then Rule 611 of Regulation NMS Trade Through requirements are triggered. In these cases, CODA BLOCK will reduce the number of shares allocated to CODA BLOCK Participants by the number of shares shown as protected "top of book" according to Rule 611 of Regulation NMS and CODA BLOCK's NBBO snapshot at the end of the 30-second order entry window. CODA will route orders outside CODA to satisfy the requirements of Rule 611 of Regulation NMS in an agency capacity. Any shares filled at the protected prices will be allocated according to the "Secondary Allocation" described below. 4) The primary allocation process will not allocate shares in mixed or odd lots. If the final 100 shares need to be allocated to one participating order while there are several participating orders in the CODA BLOCK auction order book, the final 100 shares are allocated to the participating order based on price/time priority (price and time stamp on new order receipt). TRF Trade Reporting: As detailed in Part III, Item 21, once the auction trade price and the primary allocation is determined, a trade report is generated as a single price and a single trade execution. This is the media print to the TRF. CODA sends the trade report to a TRF at this time along with any required Intermarket Sweep Orders ("ISO") (described below). Regulation NMS Rule 611 ISO Sweep (if necessary): To comply with Rule 611 of Regulation NMS, if the auction trade price is outside the NBBO, CODA will route ISOs to access the liquidity deemed as protected markets "top of book" according to CODA's "protected market" snapshot. CODA will send ISO orders to the protected markets in an agency capacity; therefore, the CODA BLOCK auction trade size may be adjusted as necessary and to comply with Rule 611 of Regulation NMS. The initiator's 100% allocation priority from the primary allocation is maintained during any auction trade size adjustment. Fills for participating orders are adjusted on a volume weighted pro-rata basis if necessary. If an auction trade size adjustment would result in a violation of CODA BLOCK's auction Trade Size Requirement then CODA, if possible, will reprice and reallocate the CODA BLOCK auction, not including the passively priced orders outside the NBBO, and price the auction at or inside the NBBO. Should that not be possible, the CODA BLOCK auction and all related orders in the auction are cancelled. The ISO order(s) to the protected markets and the auction trade print to the TRF are sent contemporaneously. Secondary Allocation (if necessary): To comply with Rule 611 of Regulation NMS, if CODA receives full or partial fills on any of the ISO orders, the filled shares will be allocated on a quantity weighted pro-rata basis to the aggressively priced orders (i.e., Buy orders in a CODA BLOCK auction with an auction trade price greater than NBO/Sell orders in a CODA BLOCK auction with an auction trade price less than NBB) that received allocations in the auction (which may include the initiator). Post Auction - Immediately after the auction price, share allocation, and TRF reporting has been completed: Subscriber execution reports: Subscribers receiving fills from CODA BLOCK will receive one fill at a single price. That fill price reflects the auction price unless the Participant receives secondary allocation shares as described above. Participants receiving secondary allocation shares in addition to primary allocation shares will receive a single fill at the average price. Post auction residual processing: a. All unfilled or partially filled IOC orders are cancelled back to the Participant. b. Day orders remain active as Resting orders as follows: i. If an initiating or participating order received in response to an Auction Alert and tagged for CODA BLOCK has residual quantity, it is eligible to interact with future CODA BLOCK auctions, but not eligible to interact with other CODA auction types. ii. If the remaining quantity on a CODA BLOCK auction Day order is less than 1,000 shares, then CODA BLOCK will cancel the order. iii. All CODA BLOCK auction orders that do remain active as Resting orders will maintain the 100-share minimum fill quantity unless another value is specified by the Subscriber. c. Conditional interests that send Day orders as a firm up to a CODA BLOCK invites are cancelled after the auction. d. Resting orders (not designated as CODA BLOCK-only) that were included in a CODA BLOCK auction will remain live and active as Resting orders in CODA. e. CODA Block orders are not eligible for routing by FLARE. Clearance and settlement: CODA BLOCK's clearing and settlement procedures are consistent with other CODA auction types. At the completion or cancellation of a CODA BLOCK auction, the symbol is again available for initiation of a new CODA BLOCK auction. Character limit exceeded. Please refer to the attachment for Part III, Item 11(c) for additional information on CODA ONE, CODA FUSE, maximum contra-size, minimum full quantity, self-trade prevention and the handling of errors. 

CODA MICRO: Subscribers (both Liquidity Seekers and Liquidity Providers) may elect to not trade with or block any number of specified counterparties in CODA MICRO auctions. Subscribers can identify such counterparties to CODA Markets by name or by reference to their own historical executions. If identified to CODA Markets by name, CODA Markets will not confirm or deny to such identifying Subscriber any active subscriptions of any other Subscribers (unless authorized to do so by the Subscriber being identified), but CODA Markets will satisfy the do-not-trade request if the identified counterparty is a CODA Markets Subscriber. Sponsored Users may also submit a do-not-trade request with proper disclosure to their sponsoring broker Subscriber. CODA enforces the block at the MPID level. Therefore, if a do-not-trade request is in effect between "Subscriber A" with a MPID of ABCD and "Subscriber B" with a MPID of WXYZ, then any trades that would otherwise occur in CODA MICRO, as discussed throughout this Form between ABCD and WXYZ, will result in a nothing done. Requests may be delivered verbally or in writing by the Subscriber. CODA can process and effect counterparty blocking requests intraday or on a scheduled date. If a trade does not occur due to an active do-not-trade request by a Subscriber, neither the identifying Subscriber nor the identified counterparty will be notified that this was the reason the order was cancelled or for a nothing done. Two or more Subscribers may request to trade exclusively with each other in CODA MICRO. From the Liquidity Seeker's perspective, its RFT/Auction Alerts will only be sent to the exclusive Liquidity Provider(s) it has designated. From the Liquidity Provider's perspective, it will only receive RFT/Auction Alerts from the exclusive Liquidity Seeker(s) it has designated. The request can be set as a default for the Subscribers, or specified at the session level or on an order-to-order basis. As described previously, CODA Markets will not confirm or deny whether any firm or person is a CODA Subscriber, but Subscribers may disclose their subscription status/participation in CODA to third parties at their discretion, for the purpose of arranging exclusive trading or otherwise. As previously mentioned, CODA MICRO enforces self-trade prevention at the MPID level. Subscribers cannot opt out of enforcement of self-trade prevention in CODA MICRO. CODA BLOCK and CODA FUSE: Counterparty restriction is not supported in CODA BLOCK and CODA FUSE auctions. However, order type restriction is supported using the "Auction Order Handling Configuration Request Form" (mentioned in Part III, Item 7(a)) and available order handling customizations (discussed in Part III, Item 11(c)). As previously mentioned, CODA BLOCK and CODA FUSE does not enforce self-trade prevention due to the multilateral auction process (defined in Part III, Item 7 (a)). All Auction Types: Each auction type allows for customized order handling (mentioned in Part III, Item 7(a)), which is requested via the "Auction Order Handling Configuration Request Form" (available on the CODA website (www.codamarkets.com)). The customizations available offer the ability to exclude specific types of orders and/or trading interests. For example, a Liquidity Seeker can exclude one or more of the following: conditional interests from CODA MICRO, conditional liquidity from CODA FUSE and Liquidity Provider responses from CODA FUSE. The order handling customization process also allows Liquidity Seekers to prevent their resting orders and conditional interests from participating in one or more auction types. Customized order handling optionality, specific to each auction type, is discussed in further detail in Part III, Item 11(c). 

CODA does NOT display any orders or quotes in the NMS Stock ATS to any Person (not including those employees who are operating the system). Information from an order can be displayed in an invite to conditional liquidity as described below and in Part III, Item 9(a). Conditional liquidity is supported by CODA and discussed in detail in Part III, Item 7(a) and Part III, Item 9(a). The process of inviting a conditional interest to be firmed up may be considered an expression or display of trading interest. - In CODA MICRO and CODA FUSE, invites to conditional liquidity represent current executable trading opportunities. As a result, Participants using conditional liquidity in CODA MICRO and CODA FUSE are expected to maintain an 80% or greater firm up rate. Invites are delivered to Participants with live conditional liquidity representing an executable trading interest. In CODA MICRO, delivery of the invite is sequential and based on price / size / time priority amongst the resting conditional interests until the initiator's order is filled. In CODA FUSE, delivery of invites is based on the CODA FUSE volume-weighted pro-rata allocation and matching process (discussed in detail in Part III, Item 11(c)). Invites contain the symbol, side, price and size (up to the quantity on the conditional interest or Inbound IOI being invited) for which CODA is requesting the conditional Participant to firm up. - A CODA BLOCK invite to a conditional interest represents nothing more than an alert that there is an in-progress on-demand CODA BLOCK auction for a particular Reg NMS stock. The CODA BLOCK conditional invite is therefore "symbol-only" by nature and does not represent the presence of an executable contra-side order. Regardless of side and price, invites are delivered contemporaneously to all Participants with a live CODA BLOCK eligible conditional interest in the same symbol as the in-progress CODA BLOCK on-demand auction. Invites contain symbol, side, price and size, but (as previously mentioned) the values echo the values from the conditional interest being invited. As part of the on-demand auction process, and through "symbol-only" Auction Alerts or RFTs, CODA anonymously expresses an initiator's interest to run an on-demand auction in the Reg NMS stock identified in the "symbol-only" alert. As discussed in detail in Part III, Item 11(a) and (c), and by default, RFTs or Auction Alerts do NOT include the side, size or price from the auction-initiating order. "Symbol-only" RFTs or Auctions Alerts are delivered to both Subscribers and Sponsored Users, including buy side traders who access CODA through a sponsoring broker Subscriber. Participants may receive CODA BLOCK RFTs or Auction Alerts through channels such as FIX, Bloomberg and their OMS/EMS. All CODA MICRO and CODA FUSE RFTs or Auction Alerts are delivered via FIX. On request of the Participant, CODA can filter the RFTs or Auction Alerts based on factors such as auction type, symbol sector, and a static symbol list. Orders responding to auctions or resting in the CODA Book are never displayed. 

CODA, the ATS, via its router, FLARE, allows Liquidity Seekers, at their discretion and as described in Part II, Item 7(a), to route orders to external trading centers, including exchanges, ATSs, Single Dealer Platforms, and brokers, as well as CODA Markets affiliated broker-dealers, ACS Execution Services, LLC and Comhar Capital Markets, LLC. Subscribers can choose not to have orders enter the ATS via FLARE prior to being routed externally for execution. As described in Part III, Item 4(a), FLARE orders are eligible for extended hours order entry and execution. CODA MICRO and CODA FUSE orders are eligible to be routed via FLARE either as residual liquidity from an initiating order or as a non-marketable order. Subscribers may also instruct orders to be sent to other trading centers before (or instead of) initiating an auction at CODA. All outbound routing via FLARE is at the discretion and direction of the Liquidity Seeker Subscriber. When an order is being routed by FLARE, such order does not participate in the CODA auction process. An order routed by FLARE may be entered or re-entered into CODA and participate in CODA's auction process. The ATS and FLARE utilize the same FIX connections to receive messages from and send messages to Subscribers. As such, a Subscriber wishing to modify or cancel an order will send the same message regardless of whether the order is being handled by the ATS or FLARE. All outbound routing via FLARE is at the discretion and direction of the Liquidity Seeker Subscriber. Participants work with CODA sales, operations and support teams to configure one or more strategies for routing out of the ATS. Subscribers acting in the capacity of a Liquidity Seeker use FIX tags to direct orders to the routable or non-routable strategies. Participants may also opt for a default routable configuration. Affirmative instruction is obtained during the configuration discussions mentioned above and on an order-by-order basis via FIX tags. Liquidity Seeker orders directed to CODA BLOCK are not eligible for routing. Liquidity Provider orders are never eligible for routing. 

The CODA BLOCK auction type does not allow the initiation of a new CODA BLOCK auction after 3:59:00 P.M. ET. The CODA FUSE auction type does not allow the initiation of a new CODA FUSE auction after 3:59:59 P.M. ET. All other features of the ATS operate as normal during the close. 

Broker Dealers (when using the ATS as Liquidity Seekers): CODA Markets assesses a negotiated per-executed-share fee to Broker Dealer Liquidity Seekers for shares traded in CODA for stocks priced greater than or equal to $1.00. That fee may be in the form of a charge or a rebate. For stocks priced less than $1.00, CODA Markets assesses a negotiated per-executed-share fee (charge or rebate) or a negotiated fee based on a percentage of the executed notional value of the trade. The decision to assess a fee based on a percentage of executed notional values instead of the number of shares is based on the same factors listed below. The charge assessed or rebate provided to any Broker Dealer Liquidity Seeker may vary based on factors including: 1) Auction Type (e.g., CODA MICRO, CODA BLOCK, CODA FUSE); 2) Order Type (e.g., firm, conditional); 3) Adding (Resting) vs. Taking (Initiating); 4) Security Price (e.g., above a dollar vs. sub-dollar); 5) Strategy (routable vs non-routable): Strategy-based pricing can be considered bundled pricing. For example, a Liquidity Seeker can be charged a flat fee for all executed shares regardless of executing in CODA or an away venue. CODA Markets reserves the right to offer broker dealer Liquidity Seekers a tiered pricing schedule based on volume or large (block) trades. At the time of this filing, there is no tier-based pricing in place for Liquidity Seekers. Liquidity Seeker usage of FLARE may be charged based on established per share executions fees (or rebates), a percentage of notional value executed, a commission-sharing agreement or a cost-plus execution model. Liquidity Seeker Subscribers who are broker dealers may charge their own clients an amount higher than the Subscriber's actual and CODA Markets' own cost of execution through FLARE. CODA Markets and the broker dealer Subscriber may split the difference between the fee charged by the Subscriber to its clients and the actual cost of execution through FLARE to CODA Markets. CODA Markets can refer to this as commission-sharing. A cost-plus model involves CODA Markets charging a Subscriber a negotiated value on top of CODA's execution costs when using FLARE. Broker Dealers (when using the ATS as Liquidity Providers): CODA Markets assesses a per-executed-share fee to the Broker Dealer Liquidity Provider for shares traded in CODA for stocks prices greater than or equal to $1.00. That fee may be in the form of a charge or a rebate. For stocks priced less than $1.00, CODA Markets assesses a per-executed-share fee (charge or rebate) or a fee based on a percentage of the executed notional value of the trade. The fee (charge or rebate) is identified in the "Request-for-Trade" message sent to the Liquidity Provider as part of the ATS's on-demand auction matching process. The per-executed-share or percentage of executed notional value-based fee charged or rebated to the Liquidity Provider is determined by the amount charged or rebated to the initiating Liquidity Seeker of each on-demand auction. CODA Markets offers Liquidity Providers the following participation-based trading credits: CODA MICRO: Average Daily Volume: Liquidity Providers with a qualifying ADV are provided a per-executed-share rebate for all shares traded in CODA MICRO during the month. This rebate is a discount from the fees/rebates assessed for daily trading discussed above. Large (Block) Trades: Liquidity Providers are provided a per-executed-share rebate for trades in CODA MICRO of qualifying size. This rebate is a discount from the fees/rebates assessed for daily trading discussed above. CODA BLOCK: Average Daily Volume: Liquidity Providers with a qualifying ADV are provided a discounted rate for all shares executed in CODA BLOCK during the month. Institutions (whether accessing the ATS as Liquidity Seekers or Liquidity Providers): CODA Markets assesses a negotiated per-executed-share fee to Institutions for shares traded in the ATS. Per executed share rebate and fees, currently range from a $(0.0030) rebate to a $0.0100 fee for brokers and institutions. CODA Markets passes through certain regulatory fees (including FINRA's Section 3 fee and Trading Activity Fee ("TAF") for Subscribers who are not FINRA members). 

FLARE is a service of CODA. All orders are first routed to CODA and based on instructions received from Subscribers and the eligibility requirements discussed in Part III, Item 11(c), can then be executed in the ATS, routed out via FLARE, rest in the CODA Book or cancelled back to the Subscriber. As noted above in Part III, Item 19(a), Subscribers opting to interact with both the ATS and away markets via FLARE can be assessed a bundled fee (i.e., a flat rate for executed shares in both CODA and FLARE) or explicit fees (i.e., varying rates for executed shares in CODA versus away markets). 

The range for the CODA MICRO ADV Liquidity Provider Tier and Large Trade Credit is a $0.0001 to $0.0006 per executed share rebate from agreed upon rates. The range for the CODA BLOCK ADV Liquidity Provider Tier is a $0.0005 to $0.0010 per executed share rebate from agreed upon rates. 

CODA Markets, at its discretion, may choose to limit, suspend or stop trading on CODA in all or individual NMS stocks. Reasons for the stoppage may include regulatory, active street-wide trade halts, unreliable market data, technology or platform issues, programming errors, or systemic issues. CODA Markets, at its discretion, can suspend trading at any time, including the suspension of trading in individual NMS stocks for reasons such as, approaching Regulation ATS Fair Access and Regulation SCI volume thresholds. By default, if trading is suspended in a security during regular trading hours, open orders and trading interests in the ATS will be cancelled. Any new orders received by CODA while a security is disabled or halted will be rejected. 

Following an execution, all sides of the trade are reported to a Trade Reporting Facility ("TRF") to post the trade on the consolidated tape. CODA becomes a counterparty to both or all (CODA BLOCK) sides on each trade. Currently, CODA reports executed trades to the FINRA/NYSE TRF, but reserves the right to report to any other registered TRF. At this time, CODA is only connected to the FINRA/NYSE TRF. CODA reports all executions on its ATS under the MPID, "CODA". CODA MICRO executions involving more than two orders are printed to the tape individually. In other words, if an auction-initiating order trades with two responding orders, then two trades are printed to the tape (potentially at unique prices). CODA Markets will also submit a non-media report for each execution. CODA BLOCK and CODA FUSE executions are printed to the tape as a single multilateral trade. In other words, if an auction-initiating order trades with two responding orders, then one trade is printed to the tape (at a single auction trade price). Individual Participants in the trade receive execution reports only for their respective executed quantity. CODA Markets will also submit non-media reports for the executions. Orders routed via FLARE and executed at away Trading Centers are reported to the TRF by the away Trading Centers. CODA Markets does not submit a non-media report for orders routed via FLARE and executed at away Trading Centers. 

At the time of execution, either inside of CODA or at an away market via FLARE, CODA Markets will substitute itself as counterparty for clearing purposes. CODA Markets utilizes BofA Securities, Inc. to submit trade details for transactions executed inside of CODA for clearing at NSCC and settlement at DTC. CODA Markets utilizes BofA Securities, Inc. to submit trade details for transactions executed via FLARE for clearing at NSCC and settlement at DTC. CODA requires every Subscriber to either self-clear or have its own clearing arrangement with a clearing firm; however, Subscribers are not required to utilize BofA Securities, Inc. BofA Securities, Inc. will submit trades to the NSCC for clearing in accordance with any QSR arrangement between them and the Subscriber or the Subscriber's clearing firm. Although CODA Markets substitutes itself as counterparty for clearing purposes, CODA Markets does not guarantee delivery of trades occurring inside CODA or trades occurring on an away market via FLARE. Instead, clearing and settlement of trades is dependent upon the original counterparties satisfying their delivery obligations. As such, should a counterparty have clearance or settlement issues, as further described below, CODA Markets reserves the option to step into the position of the original counterparty or bust/reverse the trade pursuant to CODA's Subscriber Agreement. In determining whether to step into the position of the original counterparty or bust/reverse the trade, CODA Markets will consider the size of the trade, the potential losses from taking on the position, and the ability of CODA Markets to trade out of the position quickly. Below is a description of how CODA Markets resolves various clearing and settlement issues: Clearing Issues (Uncompares) As discussed below, CODA Markets considers a clearing issue, also referred to below as an uncompare, to be when the trade details submitted by CODA Markets' clearing firm and a Subscribers' clearing firm to NSCC do not match. If the clearing issue was with respect to a trade occurring on the ATS between two Subscribers, CODA Markets would be made aware of the uncompare on T+0 or T+1. At this point, CODA Markets will work with the Subscriber to resolve the uncompare. If CODA Markets is unable to resolve the uncompare, CODA Markets will contact the Subscriber on the other side of the original transaction and, following discussions with the impacted Subscriber, may bust the trade. If CODA Markets decides to bust the trade, CODA Markets will request that its clearing firm cancel the trade and also require the affected Subscriber to submit a trade reversal to its clearing firm to be submitted to NSCC. In the alternative, CODA Markets may decide to maintain the other side of the transaction and trade out of the position. If CODA Markets decides to maintain the other side of the transaction and trade out of the position, CODA Markets will take the necessary market actions to meet its settlement obligation. If the clearing issue was with respect to a trade executed via FLARE where the trading details submitted by an away market or its clearing firm do not match the trading details submitted by CODA Markets' clearing firm, CODA Markets would be made aware of the uncompare on T+0 or T+1. At this point, CODA Markets will work with the away market to resolve the uncompare. If CODA Markets is unable to resolve the uncompare, CODA Markets will contact the Subscriber on the other side of the trade and, following discussions with the impacted Subscriber, may bust the trade. If CODA Markets decides to bust the trade, CODA Markets will request that its clearing firm cancel the trade and also require the affected Subscriber to submit a trade reversal to its clearing firm to be submitted to NSCC. In the alternative, CODA Markets may decide to maintain the other side of the transaction and trade out of the position. If CODA Markets decides to take on the other side of the transaction and trade out of the position, CODA Markets will take the necessary market actions to meet its settlement obligation. If the clearing issue was with respect to a trade executed via FLARE where the trading details submitted by the Subscriber's clearing firm do not match the trading details submitted by CODA Markets' clearing firm, CODA Markets would be made aware of the uncompare on T+0 or T+1. At this point, CODA Markets will work with the Subscriber to resolve the uncompare. If CODA Markets is unable to resolve the uncompare, CODA Markets will contact the away market to discuss how to resolve the issue. If possible, CODA Markets will request that the away market bust the trade. If the away market agrees to bust the trade, CODA Markets will request that its clearing firm cancel the trade. If CODA Markets is required to maintain the trade with the away market, CODA Markets will take the necessary market actions to meet its settlement obligation. Settlement Issues (Fail-to-Delivers) As discussed below, CODA Markets considers a settlement issue to be when trade details have been successfully submitted to NSCC, but one of the counterparties to the original transaction fails to deliver the securities for settlement. If the settlement issue was with respect to a trade occurring on the ATS between two Subscribers, CODA Markets would be made aware of the settlement issue on T+2 or possibly later whenever CODA Markets' clearing firm puts the failed position into CODA Markets' suspense account. CODA Markets will work with the failing Subscriber to resolve the settlement failure. If CODA Markets is unable to resolve the settlement failure, CODA Markets will contact the Subscriber on the other side of the trade and, following discussions with the impacted Subscriber, may require the Subscriber to enter into an offsetting transaction to reverse the trade and CODA Markets' settlement obligation. In the alternative, CODA Markets may decide to maintain the failed position, in which case, the position would be moved from CODA Markets' suspense account to its error account. At this point, CODA Markets will take the necessary market actions to meet its settlement obligation. If the settlement issue was with respect to a trade executed via FLARE where the counterparty on the away market does not meet its settlement obligations, CODA Markets would be made aware of the settlement issue on T+2 or possibly later whenever CODA Markets' clearing firm puts the failed position into CODA Markets' suspense account. CODA Markets will work with the away market to resolve the settlement failure. If CODA Markets is unable to resolve the settlement failure, CODA Markets will contact the Subscriber on the other side of the trade and, following discussions with the impacted Subscriber, may require the Subscriber to enter into an offsetting transaction to reverse the trade and CODA Markets' settlement obligation. In the alternative, CODA Markets may decide to maintain the failed position, in which case, the position would be moved from CODA Markets' suspense account to its error account. At this point, CODA Markets will take the necessary market actions to meet its settlement obligation. If the settlement issue was with respect to a trade executed via FLARE where the Subscriber does not meet its settlement obligation, CODA Markets would be made aware of the settlement issue on T+2 or possibly later whenever CODA Markets' clearing firm puts the failed position into CODA Markets' suspense account. CODA Markets will work with the failing Subscriber to resolve the settlement failure. If CODA Markets is unable to resolve the settlement failure, CODA Markets will contact the away market to discuss how to resolve the issue. If possible, CODA Markets will request that the away market enter into an offsetting transaction to reverse the trade and CODA Markets' settlement obligation. If CODA Markets is required to maintain the trade with the away market, the position would be moved from CODA Markets' suspense account to its error account. At this point, CODA Markets will take the necessary market actions to meet its settlement obligation. 

CODA Markets may clear Broker-dealer Subscribers through QSR, Correspondent or ACT clearing methodologies. CODA Markets clears non-broker-dealer, or Institutional Subscribers, through delivery versus payment ("DVP"). 

CODA uses the Securities Information Processor ("SIP") as its market data feed which is integrated into the software provided by Apex. The market data feed is used to ensure the ATS is executing trades at prices consistent with its matching logic, rules of engagement, Reg NMS and other relevant rules and regulations. Throughout each trading day CODA monitors the market data feed for the NBBO, price bands, short sale restrictions, trade halts and Limit Up Limit Down ("LULD"). Based on this information which is disseminated to its systems in real time from the market data feed, CODA will restrict execution prices and disable trading in halted symbols as required. Each Auction Type checks the market data feed upon receipt of a liquidity-seeking order to establish marketability and determine if the order is eligible to initiate an auction based on marketability. As previously discussed, only marketable orders will initiate auctions. CODA MICRO auctions using the price improvement auction matching protocol, CODA FUSE and CODA BLOCK auctions recheck the NBBO at the end of the auction to establish the NBBO used for pricing market and pegged orders, as well as pricing and executing the auction. Additionally, if a CODA FUSE or CODA BLOCK auction's trade price is set outside the NBBO, the market data feed is used to identify protected quotes in the broader market, finalize the auction trade price and Participant allocations, and establish the details of CODA Markets' responsibility to perform a Regulation NMS Rule 611 ISO Sweep (as discussed in Part III, Item 7). CODA performs several per order risk checks on Subscriber orders upon entry. The Aggressive Limit Order Check rejects orders that are priced over 10% above (on buy orders) or below (on sell orders) the NBBO at time of receipt. Additionally, if the stock is priced less than $10.00, the Aggressive Limit Order Check uses a static value of $1.00 instead of 10%. CODA uses market data to establish the limits, perform this check and reject orders in violation of the limit. CODA's Liquidity Protection Rule (discussed in Part II, Item 5) uses historical market data provided by the SIP as the data input to calculate the price bands used in CODA FUSE and CODA BLOCK. The LPR price bands are also made available along with other symbol-specific, SIP-provided market data on CODA Markets' website via the Liquidity Protection Rule Calculator. During regular trading hours, should Apex lose its connections to the market data feed, CODA will suspend trading in the ATS until the market data feed connection is reestablished. As mentioned in Part III, Item 20, CODA may suspend trading in the ATS if it determines its market data feed is providing inaccurate or unreliable data. As noted in Part III, Item 6, Apex maintains a backup market data connection through SpiderRock.