Support Binance USDⓈ-M TRADIFI_PERPETUAL contracts (tokenized stock/commodity perpetuals)

Summary

Binance USDⓈ-M now lists TRADIFI_PERPETUAL contracts: USDT-margined perpetuals on
equities, ETFs and commodities. LEAN cannot subscribe to any of them. AddCryptoFuture
fails with Failed to resolve base currency for '<TICKER>', it might be missing from the Symbol database or market 'binance' could be wrong (Common/Securities/SecurityService.cs),
because none has a row in Data/symbol-properties/symbol-properties-database.csv.

Contracts

As of Binance exchangeInfo on 2026-09-15, these 22 symbols had
contractType=TRADIFI_PERPETUAL and status=TRADING:

AMZNUSDT, BZUSDT, CLUSDT, COINUSDT, COPPERUSDT, CRCLUSDT, EWJUSDT, EWYUSDT, GOOGLUSDT,
HOODUSDT, INTCUSDT, METAUSDT, MSTRUSDT, NATGASUSDT, NVDAUSDT, PAYPUSDT, PLTRUSDT,
TSLAUSDT, XAGUSDT, XAUUSDT, XPDUSDT, XPTUSDT

None appears in symbol-properties-database.csv under crypto or cryptofuture.

Requested support

• Symbol properties rows (cryptofuture, market binance) for TRADIFI_PERPETUAL contracts.
• Historical trade/quote bars and funding (margin interest) data for backtesting.
• Live trading and data through the Binance USDⓈ-M brokerage.

Open questions

• Do these contracts follow the USDⓈ-M trading hours, margin and funding rules that
  CryptoFuture already models, or do they need their own (e.g. underlying market
  hours, a different funding interval)?
• Does the Binance data pipeline already collect them, or is sourcing required?

Reported via Intercom conversation 215475946234200.

Start with Common/Securities/SecurityService.cs and Data/symbol-properties/symbol-properties-database.csv to trace how Binance CryptoFuture symbols are resolved. Then inspect the Binance USDⓈ-M brokerage and existing CryptoFuture data pipeline for exchangeInfo, historical trade/quote bars, and funding support. Done requires defining the contract behavior and delivering the requested symbol, data, and live-trading support.