Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Crypto and CryptoFuture delisting support

Aperta
  • Qualcosa non va?
#9,795 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@abhi-byte62 ci sta già lavorando.

Dal 17/10/2026.

  • #9916 di @abhi-byte62 — aperta

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
48/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
csharp
Ambito
backend, databases

Direzione di ricerca

Inizia da Data/symbol-properties/symbol-properties-database.csv e traccia come vengono generate le relative righe cryptofuture, verificando se quel generatore è presente in questo repository. Poi segui Common/Securities/SecurityService.cs:152 e Common/Securities/Crypto/Crypto.cs:139 per capire il fallimento della subscription; il lavoro è completato quando i contratti storici delistati possono ancora essere risolti tramite AddCryptoFuture senza perdere i listings correnti.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug depth

Summary

Historical hourly trade/quote data for several Binance USDⓈ-M perpetual futures
contracts is present in the QuantConnect cloud data store, but the contracts
have no row in Data/symbol-properties/symbol-properties-database.csv under
type=cryptofuture, so AddCryptoFuture(...) cannot subscribe to them (the
security service throws Failed to resolve base currency for '<TICKER>', it might be missing from the Symbol database or market '<MARKET>' could be wrong, Common/Securities/SecurityService.cs:152).

Evidence

The following tickers were once tradeable Binance USDⓈ-M futures contracts
(all later delisted from the futures venue by Binance) and have complete
historical trade+quote hour files in the cloud store
(cryptofuture/binance/hour/<ticker>_trade.zip /
cryptofuture/binance/hour/<ticker>_quote.zip both exist for each), yet none
of them has a type=cryptofuture row in the current
symbol-properties-database.csv:

  • AKROUSDT
  • BTTUSDT
  • BZRXUSDT
  • DODOUSDT
  • KEEPUSDT
  • LUNAUSDT
  • NUUSDT
  • YFIIUSDT

All eight tickers do still have a type=crypto (spot) row in the same file,
which is not equivalent - AddCryptoFuture specifically requires a
cryptofuture row (see Common/Securities/Crypto/Crypto.cs:139, which reads
SymbolProperties.QuoteCurrency to decompose the currency pair; without a
matching row the default account-currency quote is used instead, the ticker
does not end with it, and CurrencyPairUtil.TryDecomposeCurrencyPair fails).

Suspected root cause

symbol-properties-database.csv's cryptofuture rows appear to be
regenerated from Binance's current exchangeInfo listing. Once Binance
delists a USDⓈ-M futures contract, its row silently drops out of the next
regeneration - even though the previously-collected historical files for that
ticker remain valid and stay in the data store indefinitely. The result is
that historical data becomes permanently unreachable through the normal
subscription API for any contract Binance later delists, despite the data
itself being intact.

Proposed fix

The cryptofuture generation step should preserve a symbol's row once
delisted (or fall back to the last-known row) rather than dropping it,
similar to how equity delistings do not remove historical map-file/security
entries. Where the historical row differs from the current listing, the
row should be flagged (e.g. by an IsDelisted/last-active-date column) or
delisted rows appended after a snapshot, so AddCryptoFuture can still
resolve the currency pair for periods when the contract was live.

Open questions

  • Is symbol-properties-database.csv's cryptofuture section generated by
    an automated job or hand-maintained? If automated, is the generator in this
    repo or an internal pipeline?
  • Are there other delisted Binance USDⓈ-M contracts with the same gap beyond
    the eight sampled here?

Reported via Intercom conversation 215475946234200.

Lingua principale
C#
Stelle
22k
Fork
5.3k
Merge medio
1g 3h
PR unite (30g)
43

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di QuantConnect/Lean

Tutte le issue di QuantConnect/Lean

Issue simili

Altre issue su C#

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.