Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

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

Aberta
  • Algo errado?
#32 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
25/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
python
Domínio
data, fintech-quant

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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

Linguagem predominante
Python
Estrelas
2
Forks
4
Merge médio
6h 54min
PRs com merge (30d)
7

Preparar o ambiente

  • Inclui um Dockerfile ou arquivo Docker Compose
  • Sem modelo de pull request
  • Sem guia de contribuição

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de QMeshPy/distributed-quantum

Todas as issues de QMeshPy/distributed-quantum

Issues semelhantes

Mais issues de Python

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.