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

feat(finance): Chainlink Data Feeds as verifiable price inputs

Abierto
  • ¿Algo no está bien?
#25 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
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python
Área
backend, databases, fintech-quant

Línea de trabajo

Start by reading application/real_options_pricing.py, risk_engine.py, and financial_portfolio.py, then inspect the registry's EVM adapter and issue #4 for the proposed oracle_refs format. Verify which Chainlink feeds are available on the target testnets, including Robinhood Chain. The work is complete when feed sourced runs record their round inputs, stale or missing feeds fail clearly, and recorded inputs reproduce the same result.

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

Descripción

chain-integration enhancement finance tier-2

Summary

Use Chainlink Data Feeds as an optional price source for options pricing, risk and portfolio analysis, and record the feed round ids in the provenance bundle so results are reproducible.

Motivation

Today market inputs come from files or a data-library download. On-chain feeds give verifiable, timestamped inputs and pair naturally with provenance.

Current state in this repo

  • application/real_options_pricing.py, risk_engine.py and financial_portfolio.py take price/vol inputs from request payloads or data files; yfinance is a dependency.

Proposal

  • A price-source interface with implementations: user-supplied, file, and Chainlink feed (read via the registry's EVM adapter).
  • Staleness and deviation checks (reject stale rounds, record decimals).
  • Store {feed, round_id, value, observed_at} in oracle_refs (#4).
  • Frontend: a 'use live feed' option for supported pairs on the options and risk forms.

Acceptance criteria

  • Options pricing run with a feed records the exact round used.
  • Stale or missing feeds fail with a clear message and never silently fall back.
  • Reproducing a run from its recorded inputs gives the same result.

Out of scope

  • Running our own oracle nodes.

Dependencies

  • #2
  • #4

Verify before implementing

  • Which feeds exist on the chosen testnets, including Robinhood Chain.

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
5 h 19 min
PR fusionados (30 d)
11

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.