Skip to main content
IFÁ Labs develops in the open. The oracle contracts, interface package, and supporting tools are publicly available on GitHub. This page covers how to report bugs effectively, how to request features, and how to contribute code or documentation back to the project.

Repositories


Reporting Bugs

Before Opening an Issue

Work through the following before filing a bug report — most issues are resolved without needing a GitHub issue:
  1. Check Common Integration Errors for your error type
  2. Check Error Code Reference for the specific revert
  3. Check Price Appears Stale for staleness-related issues
  4. Search existing issues — your bug may already be reported or resolved

Opening a Bug Report

Go to github.com/IFA-Labs/oracle_contract/issues/new and use the Bug Report template. Include: Required:
Include if applicable:
Minimal reproduction example: A minimal code snippet that demonstrates the issue is the single most valuable thing you can include. Strip out everything unrelated to the bug — the shorter, the better.

Requesting Features

Feature requests are welcome — particularly for:
  • New stablecoin feed support for emerging market assets
  • New chains or network deployments
  • Additional derived pair functions or batch query patterns
  • Developer tooling improvements
  • MCP server tool additions
Open a feature request at github.com/IFA-Labs/oracle_contract/issues/new using the Feature Request template. Include:
  • A clear description of what you want and why
  • The use case or protocol it would enable
  • Any relevant technical details or proposed implementation approach
  • Whether this is blocking a specific integration

Contributing Code

IFÁ Labs welcomes pull requests for bug fixes, gas optimizations, test coverage improvements, and documentation enhancements.

Contribution Workflow

1

Fork the repository

Fork oracle_contract or IfaPriceFeed-interface to your GitHub account.
2

Create a branch

Use a descriptive branch name that reflects the change:
3

Make your changes

Keep changes focused — one fix or feature per pull request. Mixed concerns make review slower and harder.
4

Run tests

All existing tests must pass. New functionality should include new tests.
5

Open a pull request

Open a PR against the main branch. Include:
  • A clear title describing what the PR does
  • A description of why the change is needed
  • Links to any related issues
  • Test results or gas comparison if relevant
PRs without a description or failing tests will not be reviewed until these are addressed.

Contribution Areas


Security Vulnerabilities

Do not open a public GitHub issue for security vulnerabilities. Public disclosure before a fix is deployed puts every protocol building on IFÁ Labs at risk. Use the responsible disclosure process:

Repository Structure

Understanding the repository layout helps contributors navigate the codebase:

Staying Connected

Watch the repositories to receive notifications for new issues, releases, and pull requests:
  1. Go to github.com/IFA-Labs/oracle_contract
  2. Click WatchAll Activity
  3. GitHub will notify you of new issues, comments, and releases
Star the repository to show support and make it easier to find:

⭐ Star oracle_contract on GitHub

Stars help IFÁ Labs surface in GitHub search and signal ecosystem trust to protocols evaluating integration.

Next Steps

FAQ

Answers to the most frequently asked questions about IFÁ Labs.

Report a Vulnerability

Responsible disclosure policy for security findings.