Derivatives Connectivity

​

Data Center Locations

The Coinbase Derivatives trading platform currently operates out of two locations: Chicago, Illinois and Secaucus, New Jersey.

Production: Equinix CH4 Data Center
Address: 350 E Cermak, Chicago, Illinois, 60616

DR/Integration: Equinix NY5 Data Center
Address: 800 Secaucus Road, Secaucus, New Jersey, 07094

Internet connectivity is hosted via AWS.

​

Environments

Coinbase Derivatives operates the following environments:

• Production
• Disaster Recovery (DR)
• Integration (Production Parallel / UAT environment)

​

Connectivity Protocols

​

Coinbase Derivatives Points of Presence

​

Connectivity via Cross Connect

Coinbase Derivatives Exchange (CDE) participants can establish cross-connects in the facilities detailed under CDE Locations.

​

How to Connect

1. Contact the CDE team about establishing a private co-located fiber connection.
   

   The CDE team will:

   a. Issue a letter of authorization (LOA) allowing you, the participant, to connect into CDE equipment.

   Each fiber connects to physical equipment that is completely redundant from the other connections.

   b. Assign 2 IP address per side:

   • 1 address range for BGP peering.
   • 1 address range for connecting to CDE that is advertised by the participant.

   c. Assign a private ASN for BGP peering. Participants can use a public ASN as long as it is owned by them.

2. Configure BGP with all parameters provided by CDE.

3. Optionally, configure PIM and RP addresses to receive multicast market data. RP Addresses for each connection are provided by CDE.

​

Connectivity via Internet

Clients may connect to select Coinbase Derivatives APIs via the internet. This solution is recommended for testing or non-latency sensitive systems. Please note that Coinbase Derivatives only accepts SSL/TLS1 encrypted connections for internet-based connections. See IP Addressing section for target host names.

Clients are encouraged to whitelist both Production and DR public addresses on their firewalls.

​

SSL/TLS Details

• Preferred: TLSv1.2 128 bits ECDHE-RSA-AES128-GCM-SHA256 Curve P-256 DHE 256
• Accepted: TLSv1.2 128 bits ECDHE-RSA-AES128-SHA256 Curve P-256 DHE 256
• Accepted: TLSv1.2 256 bits ECDHE-RSA-AES256-GCM-SHA384 Curve P-256 DHE 256
• Accepted: TLSv1.2 256 bits ECDHE-RSA-AES256-SHA384 Curve P-256 DHE 256
• Accepted: TLSv1.2 128 bits AES128-GCM-SHA256
• Accepted: TLSv1.2 128 bits AES128-SHA256
• Accepted: TLSv1.2 256 bits AES256-GCM-SHA384
• Accepted: TLSv1.2 256 bits AES256-SHA256

​

Connectivity via AWS PrivateLink

Clients may connect to Coinbase Derivatives Exchange via AWS PrivateLink. This allows for some of the benefits of private connectivity without having to cross connect directly in the datacenter. Private connectivity via AWS PrivateLink offers reduced latency and a more stable connection when compared to the Public Internet. It should be noted that for the lowest latency and most stable connection possible, Colocation Cross Connects are still recommended.

Each PrivateLink has multiple availability zones and regions that are supported. However, for the most optimal results using the primary region and availability zone is recommended.

​

Production Connectivity

• PrivateLink offering in AWS Region US-EAST-2 and US-EAST-1
• Service Name: com.amazonaws.vpce.us-east-2.vpce-svc-01bf36c2a63eaf006
• Availability Zones supported:
  • az1 (Primary)
  • az2
  • az3

​

Disaster Recovery Connectivity

• PrivateLink offering in AWS Region US-EAST-1 and US-EAST-2
• Service Name: com.amazonaws.vpce.us-east-1.vpce-svc-0051aaaf1479eae00
• Availability Zones supported:
  • az2 (Primary)
  • az4
  • az6

​

Integration Connectivity

• PrivateLink offering in AWS Region US-EAST-1 and US-EAST-2
• Service Name: com.amazonaws.vpce.us-east-1.vpce-svc-0766c510bc2c236a8
• Availability Zones supported:
  • az1
  • az4 (Primary)
  • az6

To configure PrivateLink, send your AWS Account ID to derivatives@coinbase.com so that it may be authorized. Once authorized, you’ll see the service name in your console.

​

IP Addressing

​

Cross Connect Unicast Networks

​

Cross Connect Multicast Networks

​

Cross Connect Multicast RPs

​

Production

​

Disaster Recovery

​

Integration

​

UDP Multicast Market Data Channel IDs