What Can Be Verified
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
1
Open the Read Contract page
2
Call getAssetInfo
Enter the asset ID for the feed you want to verify — for example, USDT/USD:
3
Read the result
Note the
price, decimal, and lastUpdateTime values returned.Convert to human-readable: price ÷ 10^(-decimal)For price = 1000124000000000000 and decimal = -18: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:
What to expect:
For global stablecoins (USDT, USDC), the IFÁ Labs on-chain price should match external sources within 0.1–0.3% under normal market conditions.
For emerging market stablecoins (CNGN, ZARP, BRZ), expect alignment within 0.3–1.0% — slightly wider due to natural spread between exchange venues and the time lag inherent in any oracle update cycle.
Deviations outside these ranges during normal market conditions warrant investigation. See Report a Vulnerability if you observe a persistent unexplained discrepancy.
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.1
Get the audited commit hash
The audited commit is documented in the AdForensics Audit Summary:
2
Clone the repository at that commit
3
Compile the contract
4
Compare against deployed bytecode
5
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.

