Perpetual Markets: Building the Infrastructure for Always-on Derivatives

According to the CFTC, perpetual contracts have become "a dominant form of crypto derivative trading in global markets". Most of that growth happened offshore, pushed there by uncertainty over how such instruments should be classified in the US.

That position is changing. On 29 May 2026 the CFTC and its staff took coordinated action to advance perpetual trading, including an order permitting a designated contract market to list a perpetual referencing the spot price of bitcoin as a futures contract.

Traditional venues are learning from crypto. Prediction market operators are discussing perpetuals as a next step, and established exchanges are starting to look at them. Capturing the opportunity depends on infrastructure engineered for continuous operation and real-time risk.

What perpetual markets require from infrastructure

A perpetual contract has no fixed expiration date. Instead it relies on a periodic funding rate mechanism to maintain relative price parity with the underlying asset's spot price. A position can be held until it is offset, and contracts are typically cash-settled and margin-based.

For retail participants the appeal is access: a low-cost route to exposure in large institutional contracts and underlying assets they cannot otherwise reach.

The design consequences follow quickly:

• Trading may run continuously or on a conventional schedule.
• Contracts are leveraged and margin-based, with funding obligations arising periodically.
• Exposure, balances and collateral requirements move in real time.

Retail brings an operating challenge of its own. Large exchanges move institutional collateral in very substantial size on established rails, and those do not carry across to a consumer base. Extended trading hours compound the problem, since continuous access is part of the attraction and support has to hold across the whole window. Money movement, risk and the length of the trading day all become live operational questions.

Regulatory backdrop: one product, several regimes

As with prediction markets, regulation has arrived after the market took shape, and it is now moving quickly. Perpetuals have the advantage of being a better understood instrument than binary event contracts, though treatment is developing along different lines across jurisdictions.

In the US, the CFTC's policy statement takes the view that perpetual contracts referencing asset classes not contemplated in the bitcoin order should be submitted for Commission review and approval under Regulation 40.3, rather than self-certified under Regulation 40.2. The reasoning matters for infrastructure. Susceptibility to manipulation in a cash-settled future turns on one moment, the integrity of the settlement reference price at expiry. In a perpetual, that price must hold at every funding interval, without interruption, for as long as the contract remains active.

ESMA has come at it from another direction. Instruments marketed as perpetual futures or perpetual contracts are likely to fall within existing national product intervention measures on CFDs where they meet the CFD definition. That brings leverage limits, mandatory risk warnings, margin close-out, negative balance protection and bans on incentives. The EU remains the more conservative environment.

One product, then, with configurations that differ by jurisdiction and participant type, all of which an operator needs to accommodate without rebuilding the core market architecture if they want to attract a global audience.

Strategic priority 1: engineer the market for continuous operation

A market without fixed expiries turns availability into an operating commitment. The core requirements are clear enough:

• A central limit order book capable of supporting both continuous and conventional trading schedules
• Real-time order entry, price discovery and market data distribution
• Capacity that scales as volumes change
• Resilience and disaster recovery, backed by proactive monitoring

Where a market runs continuously, no closing period exists in which to carry out routine intervention, so monitoring and support run without a natural break. Availability of that kind is what holds the reference price steady through each funding cycle. Sustaining it is why operators are looking at modern cloud-agnostic, SaaS-delivered platforms, deployable on public or private infrastructure according to operational and regulatory need, with an API-first architecture connecting the trading core to the systems around it.

Strategic priority 2: integrate real-time risk into the market architecture

The funding mechanism sits at the heart of the contract. Payments pass periodically between long and short positions, their direction and size generally determined by the difference between the contract's market price and the underlying spot price.

That mechanism sets the terms for everything downstream. Positions and exposure need continuous calculation, with balances updating in real time. Funding obligations must be recorded accurately as they arise. And pre-order validation has to stop anything that would breach defined risk parameters.

A ledger performing real-time risk calculations does much of this work, supporting the periodic payments on which the contract depends. Matching, risk and ledger have to operate as connected components, since batch or fragmented processing leaves gaps in a leveraged market that never closes.

Where the platform's responsibility ends is worth stating plainly. Real-time calculation supports the venue's risk framework. The rulebook and the physical movement of money to and from retail clients remain with the operator, and that is where the harder challenge tends to sit.

Strategic priority 3: design for integration and rapid market testing

The matching engine is one component of a much broader environment. Around it sit compliance processes covering know-your-customer (KYC) and anti-money laundering (AML), market surveillance, regulatory and participant reporting, payment flows, reference data management, and retail-facing web and mobile interfaces. Modular architecture allows specialist providers to be integrated with the core trading platform.

Asset-agnostic infrastructure can support perpetual contracts across underlying markets, from crypto to commodities, with regulatory treatment varying by class. The CFTC has said each merits independent analysis (although perpetual contracts are likely particularly ill-suited to agricultural products).

Sandbox access is central to this. Teams can explore asset types and trading models, work against the full set of APIs, simulate activity and validate integrations before production. A pre-built trading foundation lets operators concentrate their own effort on the participant experience, the distribution model and the rulebook governing both. Flexibility, integration depth and speed to launch tend to be the criteria operators select on. Two groups stand to benefit: new innovators entering the space, and established venues broadening an existing product range.

Building the foundations before the market opens

The first approved bitcoin perpetual contract is now approved for listing on a US designated contract market, and regulated perpetual futures have opened to US customers across a range of digital assets.

The infrastructure question is the open one.

Continuous availability, and the way funding and risk are calculated, are architectural choices taken before launch. They shape what a venue can support for years afterwards. Operators weighing perpetuals should be testing that architecture now, while the regulatory picture is still forming.