Copy the unit of each contract specification
Two products may express size in different units. Record the exact instrument, specification version, contract size, base unit, quote unit and relevant price instant. Product schemas illustrate why base, quote and margin assets are distinct fields.
The two definitions below are invented. One teaching contract has fixed face 100 USD per contract; the other represents 0.01 BASE units per contract. They are not actual product specifications and do not imply equal sensitivity, collateral or risk.
Compare at one explicitly supplied teaching price
Enter 2 contracts of each type and a supplied reference price of 10000 USD per BASE. The fixed-face amount is 200 USD. The linear quantity is 0.02 BASE, which converts to 200 USD under that entered price. The matching amount depends on the price input and the chosen comparison measure.
At a second teaching price of 20000 USD per BASE, the same linear quantity converts to 400 USD while the fixed face remains 200 USD. Equal contract counts did not preserve that quote-unit comparison across the two price inputs.
| Fictional definition, count2 | At10000 USD/BASE | At20000 USD/BASE |
|---|---|---|
| Fixed face 100 USD/contract | 200 USD | 200 USD |
| Linear 0.01 BASE/contract | 200 USD | 400 USD |
| Real risk equivalence | Not established | Not established |
The base-equivalent figure also needs its price
For the fixed 200 USD teaching face, dividing by 10000 gives 0.02 BASE, while dividing by 20000 gives 0.01 BASE. These are conversion outputs under the entered model. They are not proof that an actual account transferred or held those quantities.
If the required price or currency conversion is missing, preserve the dimensional amounts and leave the common-unit comparison unresolved. Do not copy a current price into a historical row merely to make both products comparable.
Separate quote notional from margin and payoff behaviour
A matching quote-unit amount at one instant does not establish matching margin, liquidation, settlement or response to future moves. Those questions can require further specifications. Keep the comparison target narrow rather than labelling the result equivalent contracts without a definition.
A Singapore report may add SGD valuation, but that requires another conversion layer. The USD quote unit, BASE quantity and collateral asset should remain named separately. Changing a displayed currency label does not perform that conversion.
Preserve the conversion direction with its dimensions
A price labelled USD per BASE multiplies a BASE quantity to obtain USD; dividing a USD face by that price instead obtains BASE. Reversing either operation can produce a plausible-looking number with the wrong unit. Write the input unit beside every factor and keep the original contract count. This dimensional check should happen before comparing results across products, not after a rounded total has been selected.
Show the definitions and the missing evidence
A useful sheet preserves both supplied contract definitions, counts, reference price and the precise common-unit measure. It can show that one invented quote notional matches at 10000 and differs at 20000 without ranking the products.
The case authenticates no instrument specification or position and recommends no trade. It complements a specification-comparison tool by making the price-dependent unit conversion explicit. All prices and sizes here are fictional.
The optional link below leads to this site's separate crypto signals and Telegram updates offer. The record method is usable without that offer. It does not independently verify the offer, establish country eligibility or turn the teaching example into an actual transaction.
Primary sources and scope
- Binance Developer Docs: COIN-M exchange-information schema
Product metadata separates size, base, quote and margin assets. Numerical contract definitions below are invented and do not establish equivalent real risk. Checked 2026-10-21.