What Can Be Verified
| Claim | Verification Method | Trust Required |
|---|---|---|
| Current on-chain price is accurate | Compare against external market sources | None |
| Price feed is fresh | Read lastUpdateTime from contract | None |
| Asset ID is correctly derived | Independently compute keccak256 | None |
| Contract is the official deployment | Cross-reference against this page + Basescan verification | None |
| Historical prices are unmodified | Query PriceUpdated event log | None |
| Audit findings are resolved | Review deployed bytecode against audited commit | None |
Method 1: On-Chain Price Verification
The most direct verification. Read the current price from the oracle contract and compare it against independent market sources.Step 1 — Read the Current On-Chain Price
- Basescan (No Code)
- ethers.js
- web3.py
Open the Read Contract page
Step 2 — Compare Against Independent Market Sources
Cross-reference the on-chain price against independent market data sources. For accurate verification, use sources that are not part of IFÁ Labs’ aggregation pipeline. Recommended verification sources by asset:| Asset | Recommended Sources |
|---|---|
| USDT/USD | CoinGecko, CoinMarketCap, Kraken, Binance spot price |
| USDC/USD | CoinGecko, CoinMarketCap, Coinbase spot price |
| CNGN/USD | Nigerian exchange rates, CBN reference rate, local P2P markets |
| ZARP/USD | South African Reserve Bank reference rate, local exchange rates |
| BRZ/USD | Brazilian exchange rates, local exchange spot price |
| ETH/USD | CoinGecko, Binance, Coinbase spot price |
Method 2: Asset ID Independent Verification
Verify that any asset ID published by IFÁ Labs is correctly derived from its symbol string — without trusting IFÁ Labs’ published values.Method 3: Historical Price Verification
Verify that historical prices recorded in the event log are consistent and unmodified.- Consistent update cadence — intervals should align with the expected deviation/heartbeat trigger model
- Reasonable price progression — prices should move gradually, not jump discontinuously except during known market events
- No gaps in the log — each event references the previous block’s state; gaps may indicate a period of staleness worth investigating
- Transaction hashes are unique — duplicate transaction hashes would indicate data tampering, which is cryptographically impossible on a functioning blockchain
Method 4: Cross-Chain Price Consistency Verification
For protocols operating across multiple chains, verify that IFÁ Labs prices are consistent across deployments.Method 5: Contract Authenticity Verification
Verify that the contract at the published address matches the audited source code.Get the audited commit hash
The audited commit is documented in the AdForensics Audit Summary:
Compare against deployed bytecode
Alternative — use Basescan verification
Basescan’s verified contract badge independently confirms the deployed bytecode matches the submitted source. View the verification status at: basescan.org/address/0xA9F17344689C2c2328F94464998db1d3e35B80dC#code
Reporting a Discrepancy
If any verification method returns a result that cannot be explained by normal oracle update timing or known market events, report it immediately:- Email: support@ifalabs.com
- Telegram: t.me/ifalabs
- GitHub: IFA-Labs/oracle_contract/issues
- The asset and network where the discrepancy was observed
- The on-chain price at the time of observation
- The external market price you compared against
- The transaction hash or block number of the relevant update
- The output of any verification scripts you ran
Next Steps
Report a Vulnerability
Responsible disclosure policy and contact channels for security issues.
Running Price Monitoring
Automate ongoing verification with production monitoring scripts.

