# Onboarding a venue or trading firm

This page connects a venue's, trading firm's, or other participant's own equipment to TheHUB, provisioned as a single [tenant](<https://docs.jointhehub.com/what-is-thehub/index.md#how-thehub-works>) per role. It is for the participant's infrastructure or network engineer, after commercial terms are signed; validators (blockchain nodes with a consensus role) use it too. For how TheHUB works, see [What is TheHUB](<https://docs.jointhehub.com/what-is-thehub/index.md>).

> [!NOTE]
>
> **Servers hosted by a computing provider?**
>
> Follow [If a computing provider hosts your servers](<https://docs.jointhehub.com/onboarding/index.md#if-a-computing-provider-hosts-your-servers>) instead.

## Before you start

You need:

- Your **placement**, one of two: a cabinet in your own space in the same data center as TheHUB's cage, connected over a **cross-connect**, a fiber link ordered from the data-center operator; or a cabinet in TheHUB's cage. Only equipment in TheHUB's cage receives in-hub market data.
- Your technical contacts for the **kickoff** (the technical meeting after signature where target dates are agreed and your TheHUB contact is named).
- A **role for each tenant** (see [Choose a role for each tenant](<#choose-a-role-for-each-tenant>)). TheHUB cannot issue addressing without one.
- A router that can run external Border Gateway Protocol (eBGP) sessions on the routed ports each tenant takes (see [Step 2](<#step-2-interface>)), and your own Autonomous System Number (ASN) for each tenant.

## Choose a role for each tenant

The role decides which other tenants a tenant can reach. TheHUB recognizes two:

| Role | For | Reaches | Does not reach |
| --- | --- | --- | --- |
| Exchange role | A trading venue | Every tenant in the trader role | Any other tenant in the exchange role |
| Trader role | A trading firm | Every tenant in the exchange role | Any other tenant in the trader role |

- **A firm that is both a venue and a trading firm** is provisioned as two tenants.
- **Changing a tenant's role later means renumbering it.**
- **Other participant types,** such as a validator (a blockchain node with a consensus role) or an oracle publisher (a participant that publishes price data onto a blockchain), also take one of the two roles, chosen by what the tenant must reach. The role is agreed at the kickoff.

## Step 1: Physical connection and equalization

Your equipment connects to a **leaf**, a switch where participants plug in; the leaves connect through TheHUB's **spines**, the core switches every flow crosses. Market data and order entry run on [dedicated physical and data paths](<https://docs.jointhehub.com/what-is-thehub/index.md#dedicated-paths>), with failover in the core.

### Where your equipment sits

|  | Your own space in the same building | A cabinet in TheHUB's cage |
| --- | --- | --- |
| How you connect | A cross-connect to the border leaf | A patch inside the cage to a cage leaf, with no Equinix order |
| Your hardware | Stays in your own cabinet, with your existing rack, power, and remote-hands arrangements | Installed in your cabinet in TheHUB's cage (see [Equipment in TheHUB's cage](<#equipment-in-thehubs-cage>)) |
| In-hub market data | Not available: the border leaf carries no in-hub market data, so a venue does not publish in-hub multicast from here and a trading firm does not receive it. DoubleZero, a private fiber network, is the multicast market-data route open to both placements (see [Using DoubleZero](<#using-doublezero>)) | Available: a venue publishes its feed, and subscribers receive it as multicast, one stream delivered to many receivers (see [Receive in-hub market data](<#receive-in-hub-market-data>)) |
| Resilience | One border leaf, with no second leaf to fail over to | Two cage leaves |

The routing contract is the same for either placement: the policy, the addressing, and the BGP session do not depend on which leaf you land on.

### Ordering cross-connects

This section applies to equipment in your own space. Each dedicated port (see [Step 2](<#step-2-interface>)) takes its own cross-connect, built to the common fiber length with its own **compensating spool**, fiber cut to make up the length. Count ports, not tenants.

To order them, see [Cross-connects from your own space](<https://docs.jointhehub.com/operations/cross-connects-and-site-access/index.md#from-your-own-space>). Your request to TheHUB must come from, or be confirmed by, one of your [Authorizing Officers](<https://docs.jointhehub.com/onboarding/index.md#requests-to-thehub>).

### Equalizing your path

TheHUB builds your path, from your **demarcation** (where your network hands off to TheHUB's cabling) to a given spine, to the common fiber length (see [Equal path lengths](<https://docs.jointhehub.com/what-is-thehub/index.md#equal-path-lengths>)).

- **From your own space,** TheHUB measures your cross-connect run and fits a compensating spool at your demarcation. TheHUB schedules the fitting with you.
- **In TheHUB's cage,** TheHUB runs equal-length fiber to every cabinet, so your cabinet's position does not change your path length.
- Your own switches and cabling are on your side of the demarcation, outside the equalized path.
- If you add a cross-connect later, TheHUB builds it to the same fiber length as the first.

### Equipment in TheHUB's cage

If your cabinet is in TheHUB's cage, follow [Site visits and work in the cage](<https://docs.jointhehub.com/operations/cross-connects-and-site-access/index.md#site-visits-and-work-in-the-cage>) before your equipment ships.

## Step 2: Interface

Each tenant gets one or more **dedicated ports**: routed physical ports on TheHUB's leaves for that tenant alone, so separation from every other tenant is at layer 1. You agree the number in Step 1 (see [Ordering cross-connects](<#ordering-cross-connects>)), or, in TheHUB's cage, when you agree with TheHUB how many ports to pre-patch.

### Ports for a venue

A venue's ports are separate physical ports, not one port carrying several virtual local area network (VLAN) tags.

| Port | Direction | Carries | Path | Placement |
| --- | --- | --- | --- | --- |
| **Outbound market-data port** | Outbound from the venue only | The venue's feed, sent to TheHUB as unicast User Datagram Protocol (UDP), and nothing else. TheHUB delivers it as in-hub multicast | The market-data path | A cabinet in TheHUB's cage |
| **Order-entry port** | Two-way | Orders in; order acknowledgements and trade confirmations out | The order-entry path | Either placement |

- **A venue in TheHUB's cage** takes at least two dedicated ports: an outbound market-data port and an order-entry port. TheHUB recommends a second order-entry port, on the other cage leaf, for resilience.
- **A venue can take one outbound market-data port per feed,** for example one for its A feed and one for its B feed.
- **A venue in its own space** has no outbound market-data port.

### Ports for a trading firm or another tenant

- **Ports:** your orders take the order-entry path. Whether a trading firm takes more than one dedicated port, for example a separate port for market data, is agreed with your TheHUB contact.
- **In-hub market data, in TheHUB's cage:** you receive it as multicast by default (see [Receive in-hub market data](<#receive-in-hub-market-data>)). If you cannot ingest multicast, a **dedicated market-data port** is the alternative (see [Market data](<https://docs.jointhehub.com/what-is-thehub/index.md#market-data>)).
- **A venue's market-data application programming interface (API):** a unicast connection to it runs on your order-entry port, so it takes the order-entry path like any order traffic; each connection is its own stream, not the shared multicast one.

### Port settings

Port speeds are in gigabits per second (G).

| Setting | Value |
| --- | --- |
| Port speed | 10 G standard, 25 G on request |
| Maximum Transmission Unit (MTU) | 1500 bytes, the standard MTU, end to end through TheHUB |
| Autonegotiation and the layer-2 security settings for your port | You and TheHUB agree them at the kickoff |

> [!WARNING]
>
> **Do not configure jumbo frames toward TheHUB**
>
> An MTU mismatch fails silently: the link stays up, small packets pass, and large packets are dropped.

[Verify and go live](<https://docs.jointhehub.com/onboarding/verify-and-go-live/index.md>) checks each tenant's leaf ports and speeds against what TheHUB confirmed and what you ordered.

## Step 3: Network architecture and addressing

For each tenant:

1. Configure each port with the values in the allocation table TheHUB sends you.
2. Advertise the tenant's assigned block, and nothing else.
3. Bring up the eBGP session to TheHUB's ASN.

### What TheHUB supplies

TheHUB allocates every value below except your ASN. It sends you an allocation table generated from its registry, the record its switch configuration is rendered from, so what you are told matches what is configured. **Do not derive any of these values yourself.** For a tenant with more than one port, the allocation table sets out which values apply to each port.

| Value | Source |
| --- | --- |
| Each tenant's address block | TheHUB's public Internet Protocol version 4 (IPv4) space, inside the aggregate for the tenant's role |
| Each peering link | A /31 from Request for Comments (RFC) 6598 shared address space (100.64.0.0/10), from the range reserved for directly attached participants. Never advertised |
| Each tenant's ASN | Your own, confirmed at the kickoff |
| TheHUB's ASN | One ASN for every tenant on every leaf |
| For a tenant that uses DoubleZero: the device code of TheHUB's DoubleZero device (DZD), the value of the DoubleZero client's `--device` flag; the DZD's two user-tunnel endpoint addresses, where tenants' tunnels terminate; and the tenant's **DoubleZero client address** (the address from its block that its host sends DoubleZero traffic from) | In your allocation table (see [Using DoubleZero](<#using-doublezero>)) |

Venue endpoint addresses come from the venue: TheHUB's routes carry only the opposite role's aggregate.

### Advertise exactly your assigned block

TheHUB's inbound prefix-list for each tenant accepts only the block registered for that tenant, and each session has a maximum-routes ceiling, a cap on the number of routes TheHUB accepts on it.

> [!WARNING]
>
> **Two ways to lose reachability**
>
> - **Advertise the block, not host routes.** TheHUB's allocation table states the size of each block it assigns, and TheHUB's policy accepts prefixes of that size. A host route (a /32) does not match and is silently rejected.
> - **Coordinate any renumber with TheHUB first.** If you move hosts to new addresses before TheHUB updates its side, the prefix-list rejects every unregistered prefix and tenant reachability is down until TheHUB catches up.

You may translate addresses inside your own network, as long as you advertise the block you were assigned. Address translation must not change a DoubleZero host's DoubleZero client address: the access pass is bound to it. If your hosts use a default route to the internet, pin test traffic to the tenant block: source any test from an address in the tenant's block, or the traffic never crosses TheHUB at all.

### Session

Each tenant runs eBGP from its own ASN to TheHUB's single presented ASN, set out in your allocation table. The value is the same on every leaf.

You do not send anything to be identified: routes arriving from each tenant are tagged inbound at the leaf with a BGP community that identifies the tenant.

**The AS path you receive carries only TheHUB's ASN.** TheHUB's internal structure, and the origin ASN of other tenants' routes, are hidden. Do not use the AS path to tell tenants apart.

*The bring-up sequence: identity, the prefix-list, and the maximum-routes ceiling are applied at the leaf before any route propagates, and a spine returns the opposite role's aggregate and the DZD endpoints, and nothing else.*

## Publish market data

For a venue in TheHUB's cage:

1. Agree with your TheHUB contact where the venue sends its feed on the outbound market-data port.
2. Send the feed there as unicast UDP. TheHUB delivers it in the cage as multicast.

To publish onto DoubleZero too, see [Using DoubleZero](<#using-doublezero>).

## Receive in-hub market data

This section applies to your equipment in TheHUB's cage, patched to a cage leaf.

1. Agree the multicast groups for the feeds you take with your TheHUB contact.
2. Join each group from your host with Internet Group Management Protocol (IGMP). TheHUB handles the joins in its field-programmable gate array (FPGA) appliance, not on its switches. A router or switch between your host and TheHUB's leaf must carry your host's join to TheHUB, as a computing provider's [first-hop switch](<https://docs.jointhehub.com/onboarding/computing-provider/index.md#receive-in-hub-market-data>) does. Agree how with your TheHUB contact.

## Using DoubleZero

Using DoubleZero is optional (see [The DoubleZero device](<https://docs.jointhehub.com/what-is-thehub/index.md#the-doublezero-device>)).

- A venue can publish its market data onto DoubleZero as Internet Protocol (IP) multicast through TheHUB's DZD, and each trading firm subscribes to it in its own DoubleZero tunnel.
- A trading firm uses DoubleZero for market data from other regions. For a participant in its own space, DoubleZero is the multicast market-data route.
- Market-data terms are agreed in the order.

### Request your access pass

Request an [access pass](<https://docs.jointhehub.com/market-data/doublezero-client/index.md#before-you-start>), DoubleZero's entitlement record, bound to one address, for each tenant that uses DoubleZero, through your TheHUB contact. Ask for the pass to be bound to the tenant's DoubleZero client address and to name the group codes, DoubleZero's identifiers for multicast groups, for the feeds the tenant publishes or subscribes to, as agreed with your TheHUB contact.

> [!TIP]
>
> **Verify**
>
> Check that the pass you receive is bound to the tenant's DoubleZero client address.

Then set up the client on the tenant's host: [Set up the DoubleZero client](<https://docs.jointhehub.com/market-data/doublezero-client/index.md>).

**Next:** [Verify and go live](<https://docs.jointhehub.com/onboarding/verify-and-go-live/index.md>), for each tenant.

## See also

- [Cross-connects and site access](<https://docs.jointhehub.com/operations/cross-connects-and-site-access/index.md>): ordering cross-connects, and working in TheHUB's cage.
- [Onboarding a computing provider](<https://docs.jointhehub.com/onboarding/computing-provider/index.md>): the same handoff for a provider that hosts other firms' servers.

Last reviewed 2026-11-20.
