Version: 8.4.12.1

V7 to V8 Migration

SpiderRock Connect (aka Version 8) has the following key features and changes compared to our current production V7 system:

Client Firm Structure

We have expanded our existing trading account and client firm structure and now natively support a two level hierarchy for larger clients (a core client firm with any number of sub-client firms). And we allow core client firms to be sponsored by a firm other that SpiderRock EXS itself. Existing V7 client firms most closely represent core- client firms in V8. Please confirm with our Client Support Desk that your current configuration is appropriate.

SpiderRock is currently in the process of migrating our current Citrix-based Tools to WebApps. We expect the process to convert the legacy tools to web-based to last at least a year or more. The first incantation of our WebApps is the Trade App, which is a live order and execution management tool that will allow clients to view market data and interact with the SpiderRock ATS, as well as interact with any public market.
The Control Viewer from V7 has been replaced by a new Web-based Portal.
All new WebApps will require 2-factor authentication to login and clients must reach out to the Client Support Desk to request a token for their initial login.

SpiderRock Connect is offering a new MLink API to provide access to live-data objects via both REST queries and WebSocket streaming. For further details, please visit: MLink

Coming soon, our new options ATS, SpiderRock ATS, will match indications of interest from liquidity seekers and responders in both Flash and Block Auctions. Participation is available to broker-dealers and qualified institutional clients of SpiderRock EXS. If you would like to participate, please reach out to our Client Support Desk to confirm if you are eligible. For further information, please visit: SpiderRock ATS.

All SRSE instances will now be exclusively run on MariaDB databases. Clients accessing a public SRSE will round-robin their access amongst a pool of SRSE instances, allowing real-time redundancy.
Some tables have been deprecated, while others have been modified and new tables have been added. To learn more about the SRSE differences between V7 and V8, please visit: V7 to V8 Differences.

SpiderRock Connect (V8) will operate out of the NY5 and DC3 data centers, in comparison to V7, which resides in NY4 and CH2 data centers. While the two environments will run completely separate from a physical perspective, critical messages will be bridged between them to ensure that risk is updated real-time. This will allow clients to trade in both systems concurrently and manage their migration to V8 in stages as they see fit.
Firms that currently maintain direct connectivity into our V7 environment should work with our Client Support Desk & Networking teams to ensure that this connectivity can be leveraged for V8 as well.

SpiderRock Connect has implemented a network proxy layer in between all externally-sourced connections and our MLink, SRSE, FIX and WebApp infrastructures. This will allow for increased redundancy amongst services, as well as enhance our protections against unexpected and potentially harmful activity. This implementation should be transparent to clients and require no further action from them.

SpiderRock Connect has modified our MAR limits (Market Access Rule/SEC 15c3-5) in V8 to what we believe are more appropriate and relevant limits to our clients’ activity. In addition, we’ve introduced the ability to add symbol-specific limits at the MAR level. Furthermore, we’ve modified our $delta calculations for equity options, removing the multiplier component. For further information, please visit: Execution Risk Controls.

The list of available User Types has been simplified and we have added a number of more granular Access Control Settings that will control a user’s access going forward. Please review your firm’s current user list and coordinate with the Client Support Desk to configure the appropriate access control settings per user.