Cboe Europe’s mandatory migration to Binary Order Entry version 3 has two separate 2027 dates: BOEv3 is scheduled for introduction on 1 February across BXE, CXE and DXE, while BOEv2 is slated for decommissioning on 30 July. The August 2026 notice is not an announcement that a platform switched protocols this October. It sets an execution-technology readiness window for brokers, proprietary trading firms and connectivity vendors that continue to use the older binary order channel.[1]
Certification is an explicit prerequisite. Participants must pass Cboe Europe Trade Desk testing through the customer portal’s certification tool before asking for live BOEv3 order-entry ports. A development environment can connect without the production order flow being authorised. Firms therefore have to coordinate their certification, gateway release, exchange port request and cutover procedures as separate work items. Simply compiling a new parser does not demonstrate that session semantics and recovery paths have been certified.[1]
The order-entry migration boundaries
BOEv3 announced schedule
| Item | Published requirement |
|---|---|
| Markets | BXE, CXE and DXE |
| BOEv3 start | Monday 1 February 2027 |
| BOEv2 retirement | Friday 30 July 2027 |
| Production ports | Formal Cboe Trade Desk certification first |
| ETR/APA reports | Not supported by BOEv3; separate reporting scope |
| Purge and dedicated-core options | Published as available on BOEv3 |
Cboe states that BOEv3 applies to order entry and does not support ETR or APA reports. That is a material product boundary, because a broker may simultaneously maintain exchange order flow, off-exchange reporting and market-data ingestion. Swapping a BOEv2 binary message handler is not a universal replacement for those other gateways. The notice also says existing port-type options, including dedicated-core and purge sessions, remain available.[1][2]
A safe migration must test logon and session recovery, acknowledgment sequence, cancel/replace, drop copies where used, mass purge and market-specific routing. It also needs deliberate rollback criteria before the BOEv2 retirement date. The notice does not provide evidence that a firm’s algorithmic strategy will run faster or that its execution quality will improve merely because the protocol version changes.[1]
Why the 2026 announcement still merits a desk review
The operative February and July dates have not occurred as of 31 October 2026, so this is a forward-readiness report about an established public timetable. A broker that waits until next summer to certify may encounter preventable port and change-control constraints. Cboe’s own release notes are the relevant technical source for further changes; the deadline should not be confused with the separate October 2026 index-data migration from Multicast PITCH to CGIF.[1][2]
Sources & further reading
- BOEv3 protocol release notice, 18 August 2026 Cboe Europe · 18 Aug 2026 · Accessed 31 Oct 2026
- European equities release-notes notices and updated documentation Cboe Europe · Accessed 31 Oct 2026