Coinbase’s Deribit migration resets the records needed to reconcile positions and orders

Coinbase’s updated migration guidance records completion of the Deribit move on 1 October. For customers reconciling the transition, the central task is to connect the old position and settlement entries with the new balance, recreated exposure and any orders entered afterwards.[1]

Positions and open instructions followed different paths

The official account describes positions being settled at a mark price, with unrealised profit or loss crystallised and funding settled. Balances were transferred and positions recreated at the settlement price. Open perpetual orders were cancelled rather than carried across. The intended continuity of market exposure therefore did not include continuity of every instruction associated with that exposure.[1]

A simplified hypothetical example shows the accounting distinction. A one-unit linear long entered at $100 and settled at $110 records a $10 realised gain. Recreating it at $110 and later valuing it at $112 produces $2 of new unrealised gain, for $12 across the two records before funding and fees. A reset entry price changes the presentation of the gain; the two records need to be read together.

Coinbase’s customer guidance explains that unrealised P&L can reappear as prices move after recreation. Open perpetual orders were cancelled, so a matching position size does not establish that an old stop or limit instruction remains active.[3][1]

Institutional connectivity and history need their own reconciliation

The institutional FAQs describe the account and portfolio mapping and the need for new API credentials. The migration material also distinguishes the former connectivity arrangements from the available Deribit access routes. Firms therefore have to reconcile identity, connectivity and permission configuration, not simply change a screen label.[2]

The updated overview specifies new API endpoints and says VPC Peering users must move to Private Link or colocation. It also says International Exchange history will remain available through its APIs for a limited time and will not appear on the combined platform. The history-export task therefore sits alongside account and connectivity work.[1]

For an automated system, authentication, portfolio mapping, permissions and order behaviour need separate checks. A connection can succeed while an instruction targets the wrong portfolio or lacks the required permission. This is an implementation framework; no customer integration was tested for this article.

CryptoSlate’s 2 October reporting provides contemporaneous context on the completed switch and the legacy environment’s read-only role. The account mechanics here come from Coinbase’s updated guidance.[4][1]

The audit trail links cash, exposure and instructions

A useful reconciliation follows the pre-migration position, settlement price, crystallised result, funding entry, transferred balance, recreated position and subsequently entered orders. Keeping those objects distinct helps identify whether a discrepancy concerns cash, exposure, an instruction or the presentation of history.

Settlement and recreation can affect realised and unrealised reporting even when the intended market exposure continues. Tax treatment and an entity’s accounting depend on the applicable rules and circumstances; the migration documentation does not supply a universal tax-neutral conclusion.

Report an error or submit an update