Upcoming Change: Consistent Contract Sizing for Scaled Futures Markets

Incident Report for Coin Metrics

Resolved

Effective September 22, 2026, we will update the representation of scaled futures contracts to provide consistent values for base, pair, size_asset, and contract_size across futures markets in the /reference-data/markets and /catalog-v2/markets endpoints.

After this change, base and size_asset will consistently identify the underlying asset, while contract_size will represent the number of underlying units represented by one contract. For example, markets currently represented as 1000bonk or kshib will be updated to bonk and shib, respectively. Exchange-native identifiers will remain available in base_native, and existing symbol and market identifiers will not change.

We will also introduce a new price_scale field to indicate how many units of size_asset are represented by the quoted price. This will allow users to calculate the underlying asset price and notional value consistently across futures markets without relying on exchange-specific symbol parsing.

Trade, quote, funding rate, open interest, liquidation, price, and amount data will not be modified.

**Action may be required for users who query markets using base, pair, or asset values. Queries that currently reference scaled asset identifiers may need to be updated. Users with exchange-specific logic to adjust contract quantities should also review those adjustments, as amount × contract_size will provide the correct underlying quantity following this change.
Posted Sep 16, 2026 - 17:37 UTC
This incident affected: Services (Pro API v4, Community API v4) and Market Data Products (Market Data Feed).