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

feat(hyperliquid): read-only market data, backtests and cross-venue spread scanner

Aperta
  • Qualcosa non va?
#32 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
python
Ambito
data, fintech-quant

Direzione di ricerca

Start by reading the finance module's existing CSV or downloaded-price input path, the portfolio format, and the dependencies in issues #4 and #12. Then check Hyperliquid's public API limits and terms, and whether the proposed read precompiles are available on mainnet. Done means reproducible allocation backtests from stored inputs and a read-only spread scanner that reports timestamps and fee assumptions, with no order signing or trading keys.

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

Descrizione

chain-integration enhancement finance tier-3

Summary

Use Hyperliquid market data (spot, perps, funding rates) as an input to the finance module, add a backtest of the optimizer's allocations, and a read-only cross-venue spread scanner against Uniswap prices.

Motivation

It supplies a liquid crypto asset universe and ties into the arbitrage-detection capability described in the research paper, without trading risk.

Current state in this repo

  • The finance module consumes CSV or downloaded price data; the research paper in the documentation repo lists arbitrage detection as a target capability.

Proposal

  • Read-only data client for public market endpoints (and, if useful, on-chain read precompiles via the EVM adapter).
  • Asset loader producing input in the existing portfolio format; funding-rate series for analysis.
  • Backtest: apply an allocation over a historical window and report realised return/variance versus the optimizer's expectation.
  • Spread scanner comparing Hyperliquid mid prices to Uniswap quotes (#12) and logging opportunities; no orders are placed.

Acceptance criteria

  • No code path signs an order or holds trading keys.
  • Backtest results are reproducible from stored inputs (#4).
  • Scanner output states data timestamps and fee assumptions.

Out of scope

  • Order placement, even on testnet, until maintainers approve a separate design.

Dependencies

  • #4
  • Optionally #12 for the scanner.

Verify before implementing

  • Public API rate limits and terms of use.
  • Whether the read precompiles and any write paths are available on mainnet versus testnet only.

References

Part of ##1. Ground rules for all issues in this roadmap are listed there (testnet-first, no secrets in the repo, chain logic behind the registry, tests and docs with every PR).

Lingua principale
Python
Stelle
2
Fork
4
Merge medio
6h 14m
PR unite (30g)
18

Preparare l'ambiente

  • Include un Dockerfile o un file Docker Compose
  • Nessun modello di pull request
  • Nessuna guida per i contributori

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 QMeshPy/distributed-quantum

Tutte le issue di QMeshPy/distributed-quantum

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.