Public methodology
How OracleIQ reaches a verdict
OracleIQ combines observed market, liquidity, holder, contract, and wallet-flow fields. Every verdict exposes reason codes and remains a research prioritization—not a prediction.
Opportunity score
The score begins from a neutral baseline and applies bounded adjustments for contract risk, liquidity depth, holder concentration, developer holdings, buy pressure, volume, and observed smart-wallet participation.
- Honeypot and severe contract-risk flags dominate positive momentum.
- Thin liquidity and concentrated holders reduce the score.
- No missing field is silently treated as a positive result.
Signal outcomes
Every recorded market signal stores its trigger-time price or market capitalization. Oracle measures the same basis after 5 minutes, 1 hour, 6 hours, 24 hours, and 7 days, including losing and invalidated outcomes.
Wallet and lineage inference
Funding and co-trader edges are associations derived from observed fields and shared token participation. Creator lineage uses the creator address and returned launch history. Neither establishes common ownership or intent.
Data coverage and refresh
On-chain market and wallet intelligence is normalized into one research model. Terminal data is cached for roughly 10–60 seconds by volatility; score history records at most once every five minutes. Each live surface exposes freshness or generation time.
Known limitations
Coverage varies by chain and token age. Off-chain identities, private order flow, centralized-exchange positions, and hidden wallet control are not observable. Results can be delayed, incomplete, or wrong.