Gate Futures Contract Sizes and Settlement Routes

A Spot quantity and a futures contract size are not interchangeable. Sending an amount of BTC as a Gate futures size can request a different number of contracts from the one the application intended.

The connector needs the settlement route and contract metadata together. A contract name on the wrong route is not repaired by a correct signature.

The Gate SDK tutorial covers client setup. This public request reads the selected USDT-settled contract:

import { RestClient } from 'gateio-api';

const client = new RestClient();
const contract = await client.getFuturesContract({
  settle: 'usdt',
  contract: 'BTC_USDT',
});
console.log(contract);

Gate's futures reference defines quanto_multiplier, size limits, price increments, and enable_decimal. Preserve their returned decimal values. Do not assume every contract uses integer lots merely because an older example used an integer.

For a hypothetical direct contract whose multiplier is 0.0001 BTC, ten contracts represent 0.001 BTC. That arithmetic depends on the selected contract type and multiplier; it is not a value to hardcode for every BTC-related instrument.

Convert the application's intended quantity using the actual metadata, then apply the permitted size and price increments. Check minimums and maximums after conversion. Rounding an invalid amount to the nearest allowed size can increase it, so the direction of rounding belongs to the application's explicit sizing rule.

Signed size distinguishes direction in the applicable Gate futures order model. Position mode, reduce-only behaviour, and close-position fields impose additional rules. A generic buy/sell adapter must translate the complete intended action rather than just negating a number.

Retain exchange, settlement, contract, account, and position mode with every command and state record. The REST route, private WebSocket channel, and position query must describe the same scope.

Changing settlement or margin configuration during a restart can make a previously valid stored intent incompatible. Validate the configured mode before dispatch rather than changing account settings automatically.

The returned order identifier establishes a correlation path. Private updates and later status reads establish execution progress. An awaited command reply cannot replace those records.

Use the order-state workflow for partial fills and unknown outcomes, and the recovery article for interrupted subscriptions. Keep the venue-specific contract conversion at the Gate boundary.