Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto
  • ¿Algo no está bien?
#32 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python
Área
data, fintech-quant

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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).

Lenguaje dominante
Python
Estrellas
2
Forks
4
Merge medio
6 h 14 min
PR fusionados (30 d)
18

Preparar el entorno

  • Incluye un Dockerfile o un archivo de Docker Compose
  • Sin plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de QMeshPy/distributed-quantum

Todos los issues de QMeshPy/distributed-quantum

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.