Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

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

Open
  • Is something wrong?
#25 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
backend, databases, fintech-quant

Research direction

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.

Written by the indexing model from the issue text.

Description

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

Dominant language
Python
Stars
2
Forks
4
Avg merge
5h 19m
Merged PRs (30d)
11

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from QMeshPy/distributed-quantum

All issues in QMeshPy/distributed-quantum

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.