Methodology & Sources

This document explains how FeedOracle calculates key metrics, defines coverage, and attributes data sources. All claims on our public pages are documented here with their methodology and limitations.

Document Version

1.0

Last Updated

9 February 2026

Review Cycle

Quarterly or on material change

Owner

FeedOracle Data Team

TVL Calculation

Claim: "$20B+ TVL" and "97% Coverage"

Definition

Total Value Locked (TVL) refers to the aggregate USD value of assets deposited in tokenized asset (RWA) protocols tracked by FeedOracle. This figure is sourced from DeFiLlama's RWA category and updated automatically.

Calculation Method

Metric	Value	Source
Tracked protocols	52	FeedOracle Protocol Registry
Tracked TVL	$20B+	DeFiLlama API (RWA category)
Total RWA TVL (DeFiLlama)	$22.3B	DeFiLlama API
DeFiLlama RWA protocols (total)	156	DeFiLlama API
Coverage percentage	97.5%	Tracked TVL / Total RWA TVL

What "Coverage" Means

Coverage is defined as tracked TVL as a percentage of total DeFiLlama RWA category TVL. FeedOracle tracks 52 of 156 DeFiLlama RWA protocols by count (33%), but these 52 represent 97.5% of the category's total TVL. The remaining 104 protocols represent long-tail assets with individually small TVL.

On public-facing pages, we round conservatively to "29 scored protocols" and "97% coverage."

Update Frequency

TVL data is refreshed automatically via the DeFiLlama API. The snapshot used for public claims is regenerated daily. The timestamp of the most recent snapshot is available via the /api/v1/rwa/overview endpoint.

Limitation: TVL figures reflect DeFiLlama's methodology and may differ from protocol self-reported numbers. FeedOracle does not independently audit on-chain deposits. TVL is a point-in-time metric and fluctuates with market conditions.

Risk Dimensions (9 Vectors)

Claim: "9 risk vectors" / "9 risk dimensions"

The RWA Risk Oracle scores each protocol across 9 independent risk dimensions. Each dimension has a documented primary data source and scoring methodology.

#	Dimension	What It Measures	Primary Source
1	TVL Weight	Protocol size relative to category	DeFiLlama API
2	Yield Spread	Deviation from risk-free rate (T-Bill)	Federal Reserve FRED
3	Diversification	Asset type concentration	On-chain analysis
4	Maturity Profile	Duration and redemption terms	On-chain + protocol docs
5	Regulatory Alignment	Jurisdiction registration status	Public regulatory registers
6	Institutional Backing	Known institutional participants	Public disclosures
7	DEX Liquidity	Secondary market depth	GeckoTerminal API
8	On-Chain Activity	Transaction volume and holder count	Etherscan / Ankr Multi-Chain
9	ESG / Carbon	Network energy and emissions profile	CCRI / EMBER Climate

Scoring Method

Each dimension produces a normalized score (0–100). Dimensions are weighted and aggregated into a composite risk score. The weighting model is documented in the Whitepaper (Chapter 5). algorithmic reason codes explain the primary drivers of each score.

Limitation: Risk scores are data-derived indicators, not ratings or investment recommendations. FeedOracle is not a credit rating agency. Scores should be used as one input among many in institutional risk workflows.

Jurisdiction Coverage (12)

Claim: "12 jurisdictions"

FeedOracle provides regulatory metadata and classification flags for 12 jurisdictions. This means we track which regulatory frameworks apply to each protocol and provide structured metadata — not compliance opinions or legal determinations.

Code	Jurisdiction	Framework(s) Tracked
US	United States	Securities Act 1933, Investment Company Act 1940
EU	European Union	MiCA, MiFID II, CSRD
UK	United Kingdom	Financial Services and Markets Act 2023
SG	Singapore	Payment Services Act, Securities and Futures Act
CH	Switzerland	DLT Act, FinSA/FinIA
DE	Germany	MiCA (EU), KWG, WpHG, eWpG
FR	France	MiCA (EU), PACTE Law
JP	Japan	Payment Services Act, FIEA
AE	UAE (DIFC/ADGM)	Virtual Asset Regulatory Authority Framework
HK	Hong Kong	Securities and Futures Ordinance
BVI	British Virgin Islands	Securities and Investment Business Act, VASPA
KY	Cayman Islands	Virtual Asset Service Providers Act

What "Jurisdiction Coverage" Means

For each jurisdiction, FeedOracle provides:

Regulatory framework metadata (which laws/regulations apply)
Classification flags (e.g., "securities", "e-money", "utility token" per jurisdiction)
Registration status indicators (where publicly available)
Regime-specific disclosure requirements (structured data)

Limitation: Jurisdiction coverage provides regulatory metadata and flags, not legal opinions. Classification determinations are based on publicly available regulatory guidance and may not reflect final regulatory positions. Institutions should verify with qualified legal counsel.

DNV Attribution

Claim: "DNV-verified" / "DNV-certified carbon data"

Scope of DNV Reference

FeedOracle references DNV in the context of carbon/ESG data sourced from VeChain's ToolChain platform. VeChain's carbon data pipeline is certified by DNV (Det Norske Veritas) under ISO 14040/14044 lifecycle assessment standards.

FeedOracle consumes this DNV-certified data as one of several carbon data sources. The DNV certification applies to VeChain's data production process, not to FeedOracle's platform or services.

Carbon Data Source Attribution

Source	Data Type	Certification
VeChain ToolChain (DNV)	Lifecycle carbon attestations	ISO 14040/14044 (DNV-certified)
CCRI (Crypto Carbon Ratings Institute)	Blockchain network energy consumption	Independent research institute
EMBER Climate	Global electricity generation and emissions	Independent climate think tank
EU ETS	European carbon allowance pricing	European Commission regulated market
Climatiq	Emission factor database	Commercial API provider

Clarification: FeedOracle itself is not DNV-certified. Public references to "DNV" describe a data source attribution, not a platform certification. We are working toward explicit language across all pages to make this distinction clear.

Complete Data Source Register

FeedOracle aggregates data from the following categories of sources. No single source is treated as authoritative — cross-source validation is applied where possible.

Blockchain & On-Chain

Source	Data Provided	Integration
Ankr Multi-Chain RPC	On-chain data across 50+ networks	Direct API AUTO
DeFiLlama	Protocol TVL, category data	Direct API AUTO
GeckoTerminal	DEX liquidity and trading pairs (trusted chains only)	Direct API AUTO
Etherscan / Block Explorers	Transaction history, holder counts	Direct API AUTO

Macroeconomic & Financial

Source	Data Provided	Integration
Federal Reserve FRED	T-Bill rates, CPI, economic indicators	Direct API AUTO
World Bank	Country-level economic indicators	Direct API AUTO
ECB (European Central Bank)	Euro area rates and monetary policy	Direct API AUTO

Carbon & ESG

Source	Data Provided	Integration
CCRI	Blockchain energy and carbon ratings	Direct API AUTO
EMBER Climate	Global electricity and emissions data	Direct API AUTO
VeChain DNV ToolChain	Carbon lifecycle attestations	Direct API AUTO
EU ETS	Carbon allowance pricing	Direct API AUTO
Climatiq	Emission factors	Direct API AUTO

Regulatory & Compliance Metadata

Source	Data Provided	Integration
Public regulatory registers	Entity registration status	Manual + automated checks
Protocol documentation	Legal structure, jurisdiction, terms	Manual review
MiCA/MiFID II texts	Classification framework	Structured mapping

Data Freshness & Update Policy

Data Category	Update Frequency	Method
TVL & Protocol Data	Daily (automated)	DeFiLlama API pull
On-Chain Metrics	Every 15 minutes	Ankr RPC polling
Macroeconomic Indicators	Daily	FRED/ECB/World Bank API
Carbon & Energy	Daily	CCRI/EMBER/EU ETS API
Regulatory Metadata	As published	Manual + automated monitoring
Risk Scores	Daily recalculation	Automated scoring engine

SLO Target: Data freshness target is ≤15 minutes for on-chain data and ≤24 hours for derived scores. See Trust & Security for availability targets.

Methodology Change Log

Date	Change	Impact
9 Feb 2026	Initial methodology documentation published	No change to calculations

Material changes to scoring methodology, data sources, or coverage definitions will be documented here and announced via the API changelog.

Questions about our methodology?

We welcome scrutiny. Contact us for detailed methodology discussions.

enterprise@feedoracle.io