Skip to main content

Appendix B: Oracle Weights

MAGMA uses category-specific weighted consensus across multiple independent oracle sources. The exact weight assigned to each source per category is not published — publishing these weights would let an adversary identify which sources to target for manipulation.

What Is Documented

ItemValue
Resolution confidence threshold70% minimum across active sources
FAST narratives (MARKET, 5-minute)Price-feed oracles only; the full AI reasoning stack is bypassed for speed
Consensus Oracle categories (SOCIAL, CULTURAL, CONVICTION)Incorporate community signal as an additional input
Universal fallbackSwitchboard, when primary sources are unavailable or return low-confidence data

Each narrative category routes to the sources most appropriate for its resolution criteria. See Oracle Architecture for the full list of sources used per category.

Approximate Public Weights

The values below mirror the public table in Oracle Architecture. They show which sources are active per category and their approximate relative contribution. Exact configured weights are withheld for the security reasons described under Why Weights Are Not Public.

CategoryPythGrokTavilyPerplexitySwitchboardSpecialist Source
MARKET40%25%15%20% fallback
SPORTS20%30%The Odds API 50%
ESPORTS40%PandaScore 60%
LEGAL40%60%
POLITICAL35%65%
SCIENTIFIC40%60%
GEOPOLITICAL35%65%
ECONOMICS35%40%25%FRED/BLS APIs
TECHNOLOGY35%40%25%
SOCIAL20%Neynar 50%, Twitter 30%
CULTURAL30%35%Community 35%
CONVICTION30%35%Community 35%
COMMODITIES25%Alpha Vantage 75%
MACRO30%25%FRED/BLS 45%
EQUITIES30%20%Alpha Vantage 50%
FOREX15%Alpha Vantage 85%
ECOSYSTEM30%30%DeFiLlama 40%
ONCHAIN30%Dune Analytics 70%
BUILDER35%40%25%
CAST30%Neynar 70%
HEALTH40%60%
CLIMATE35%65%
BUSINESS35%40%25%
SATIRE50%25%25%

Weight Governance

PropertyDetail
StorageCategory-specific weights live in protocol configuration.
AdjustmentCan be changed by super admin without a contract deploy.
TimelockSubject to the standard admin parameter timelock (72 hours on mainnet).
AuditabilityAny weight change is logged on-chain.

Why Weights Are Not Public

Once an attacker knows that source X carries Y% weight in category Z, they can focus their manipulation effort precisely on source X rather than needing to corrupt all sources simultaneously. The security benefit of keeping the exact weights non-public outweighs the transparency benefit of publishing them.