On-chain settlement means the state of a trade — an opened position, an adjusted margin balance, a closed trade — is recorded as a transaction on a public blockchain. A perpetual DEX built this way settles directly to the chain it runs on; the trade-off for that transparency and lack of a central custodian is that the trader is bound by that chain's own block time, confirmation process and, where relevant, bridging mechanics.
Every state change to an on-chain perpetual position — opening it, adding or removing margin, closing it, or being liquidated — is submitted as a transaction that the underlying blockchain's validators or sequencers process and record. Once that transaction is included in a block and the chain reaches finality on it, the change is part of the chain's permanent, public history and cannot be reversed by any single party, including the exchange's own operator.
A blockchain produces new blocks at an interval specific to its own design — Ethereum's base layer, for example, has produced blocks roughly every twelve seconds since its 2022 transition to proof of stake — and a transaction is not final the instant it is submitted; it becomes final once enough subsequent blocks have confirmed it that reversing it would require an implausible amount of coordinated work or stake. Different chains reach that point of practical irreversibility on different schedules, which is why the same category of transaction can settle in a few seconds on one chain and take longer on another. Consensus designs also differ on how finality is reached: a probabilistic-finality chain becomes progressively less likely to be reversed with each additional confirming block, without ever reaching an absolute guarantee, while a deterministic-finality design has a specific point at which a block is formally certified as final by the validator set and cannot be reversed short of a coordinated protocol-level fork. A trader moving significant margin onto a chain benefits from knowing which model that chain uses, since it determines how many confirmations, or how much time, represents a safe threshold before treating a deposit as settled.
A layer-2 rollup — the architecture behind chains such as Arbitrum and Base — batches many transactions together off the base chain and posts a compressed proof of that batch back to the underlying layer-1 chain, most commonly Ethereum. This lets a rollup process transactions faster and at lower cost than the base layer alone while still inheriting the base layer's security once a batch's proof is confirmed there; the trade-off is a withdrawal from the rollup back to the base layer that can involve a waiting period, depending on the specific rollup's design, before funds are fully available on the base chain. Submitting a transaction to most blockchains also requires paying a network fee, commonly called gas, priced in the chain's own native asset and set by market demand for the limited space in each block; during periods of high network activity this fee can rise sharply and a low-fee transaction can sit unconfirmed for longer than usual, which matters for a trader who needs a margin adjustment or a liquidation-avoiding top-up to settle quickly. A congested base layer is part of why many perpetual DEXs choose to build on a faster or cheaper layer-2.
Moving an asset from one blockchain to another — funding a wallet on one chain with an asset that originated on a different one — requires a bridge, a protocol that locks or burns the asset on the source chain and mints or releases an equivalent on the destination chain. A bridge is a separate piece of software with its own security assumptions distinct from either chain it connects, and bridge exploits have historically been among the largest categories of loss in the industry — a fact that makes the choice of bridge part of the risk a trader takes on when moving funds to open a position. A bridged asset is typically a synthetic representation — a token certifying a claim on the original asset locked elsewhere — and the value of that claim depends entirely on the bridge continuing to hold what it locked; a bridge that is exploited or drained leaves the synthetic token on the destination chain worth less than the asset it was meant to represent.
Not every part of a perpetual exchange necessarily runs on-chain:
Running matching or indexing off-chain can improve speed at the cost of moving some trust back toward the operator running that component. A trader evaluating a specific venue should check which parts of the trading process are on-chain and verifiable and which are not.
Settlement architecture determines what a trader can verify independently — a fully on-chain venue lets anyone audit open interest, liquidation events and contract balances directly from the blockchain, without relying on the operator's own reporting — and it determines what happens if the operator's front end goes offline: a trader who understands the underlying smart contract can, in principle, still interact with it directly, which is not true of a purely off-chain system. This is also why the specific chain and settlement design a venue uses is a legitimate part of evaluating it, on the same footing as its fee schedule or its market list; it is not a purely technical detail a trader can safely ignore. See how wallet custody works for the other half of that same trader-controlled design.
On-chain settlement is recording a trade's state changes — opening, adjusting or closing a position — directly as transactions on a public blockchain. It makes the resulting record public and, once final, irreversible by any single party.
Finality is the point at which a blockchain transaction becomes practically irreversible, typically once enough subsequent blocks have confirmed it that undoing it would require an implausible amount of coordinated work or stake. Different chains reach finality on different schedules based on their own consensus design.
A layer 2 is a protocol, such as a rollup, built on top of a base blockchain like Ethereum that batches transactions off the base chain and posts a compressed proof back to it. It processes transactions faster and more cheaply than the base layer while still inheriting the base layer's security.