Pre-launch · September 2026

The field is open.

Eighty-one markets, eight venues, one price that admits what it does not know. Leverage follows that admission while you hold the position, and the venue warns you before it moves. That alert exists because here leverage moves on its own, and the venue tells you before it does. Real money, a real engine, a small first intake.

sources15 / 15 markets81 median confidence99.7% feed… msg/s enginev0.25
Why a pre-launch at all

Every exchange promises leverage. Ours changes its mind in public.

Four things happen here that do not happen elsewhere. Each one is live below, on the real engine, right now. The pre-launch exists because a rule that moves while you hold a position deserves to be broken by people before it is trusted by anyone.

01

Leverage follows the data.

The ceiling is a property of the market. What you actually get is the ceiling minus what the engine cannot see: divergence between venues, volatility, gaps in the tape. When the sources disagree, leverage comes down, and the account is told why, in numbers, before the margin call.

Leverage ladder · live
02

The price says how sure it is.

Up to eight venues feed every market. The engine estimates a price and attaches a confidence to the estimate. That number is not decoration: it sets the regime, the regime sets the margin, and the venue that pulled the estimate off centre is named on the screen.

Venue divergence · liveFull
03

Liquidation is a forecast, not a surprise.

Because margin moves with the data, the venue can tell you what the data is about to do to you. A push alert names the market, the cut and your buffer. The forward look on every position shows the next regime step before it happens. The alert exists because the cut exists; the pre-launch is where we learn whether it arrives early enough.

Push alert · composed from live state
OPENFIELDnow
    04

    Everything is written down.

    Every order, cancel, fill, funding tick and regime change appends to a hash-chained journal. What the engine did to your account is reproducible from your export, and what we change during the pre-launch goes into the changelog with a date, and with your handle next to it if you found it.

    Journal · illustrationreal hashes live in your export
    Hash-chainedeach record carries the hash of the one before it
    Exportableyour account's full history, one file
    Public changelogevery change during the pre-launch, dated and attributed
    Before you apply

    Read where we lose first.

    Every liquidation the engine would have made across the worst days since 2020 is replayed against a flat-margin baseline and published with a hash, including the entries where only Openfield liquidated and the bug the replay found in our own engine. If you trade leverage for a living, this is the page that should decide you, not this one.

    29episodes replayed
    …entries tested
    …liquidations under Openfield
    …entries where only Openfield liquidated
    The deal

    You get the engine. We get the truth.

    What you get

    • Your deposit, one real engine. Portfolio margin with offsets inside a risk family, a house maker that steps back when you quote, the forward look on every position.
    • Eighty-one markets across crypto, metals, energy, indices, rates and FX, priced from up to eight venues over live WebSocket feeds.
    • Alerts that follow the engine. Regime changes, leverage cuts and buffer changes on your phone, while you sleep.
    • A maker API and a voice. Keys with scopes, batch orders, a WebSocket with cancel-on-disconnect. What you find shapes the next version.

    What we ask

    • Trade the way you actually trade. Size, leverage, hours, instruments, everything.
    • Try to break it. The margin engine, the book, the regime logic, the terminal on a phone, the alerts.
    • Tell us where a number did not add up or a screen lied. In the terminal, by mail, or on X.
    • Accept what this engine does to an open position. Available leverage can fall while you hold it. In Divergence the maintenance margin rises and your buffer shrinks. In Degraded the offsets are cut and the account goes reduce-only. If the buffer runs out, the engine liquidates in steps, in public, on the chain. Here it is the rule, not a decision someone makes in the moment.
    In return

    Access, and a say in what the venue becomes. Points accrue on the public chain by the published table, and accounts opened with a pre-launch invite carry that mark on their journal for good. What either becomes is not decided, and we will not pretend otherwise. When it is decided, the pre-launch is the first line of that changelog.

    How it runs

    Small intakes, written down before they happen.

    Invites go out in batches small enough that every piece of feedback gets read and answered. Each step is on the docs page and in the terms before it starts.

    Now

    Now

    Applications open. Invite-only accounts in USDC on Solana, opened with a passkey, a wallet, a key or an e-mail; deposits on chain, withdrawals approved and signed. Weekly notes in the changelog on what broke and what changed.

    Next

    Next

    More seats, the maker API opened to bots on request, the first replay of the venue's own book against the public record.

    After

    The pre-launch decides

    What the next stage looks like is decided by what the first intake found, not by a roadmap written before anyone traded.

    Apply

    One seat, one person.

    Openfield · pre-launch
    Pre-launch
    Seat pending
    SettlementUSDC on Solana
    Venues per marketup to 8
    Markets81
    Termsv2026-09-02

    Tell us who is trading.

    Two minutes. We keep the application and nothing else.

    Invites are personal, one per person, and the code is shown once. Read the terms and the risk note first.
    Have a code?

    Then the field is already yours.

    The code opens an account. Sign in with a passkey, a wallet, a key or an e-mail inside the terminal, and the account opens in USDC on Solana; your first deposit is what it trades on.