> For the complete documentation index, see [llms.txt](https://docs.chamberfi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chamberfi.com/concepts/oracles.md).

# Oracles

Every USD value Chamber reports (vault NAV, share price, deposit size, performance-fee threshold) comes from an oracle. Chamber uses a mix of **Chainlink**, **Pyth**, and **TWAP** (time-weighted average price) feeds, chosen per asset at the protocol level. Chamber does not run its own price feeds; it reads established third-party oracles.

## Feed types

* **Chainlink**: the default for blue-chip assets and standard USD pairs.
* **Pyth**: used where Chainlink doesn't have coverage, or where a different update profile suits the asset.
* **TWAP**: time-weighted average price derived onchain from trading activity on supported venues. Used for assets without a reliable Chainlink or Pyth feed.

Each supported asset has its feed configured at the **protocol level**, not by individual vault managers. Every vault holding asset X on chain Y uses the same feed.

## Oracle risk

Oracles are external dependencies. The main risks:

* **Staleness**: a feed stops updating. Chamber contracts check staleness thresholds and revert rather than operate on stale prices. Deposits, withdrawals, and trades involving the affected asset will fail until the feed recovers.
* **Manipulation**: theoretically possible on illiquid pairs. TWAP feeds resist single-block manipulation by averaging over a time window. Feed selection favours assets with deep liquidity.

## Related

* [NAV and accounting](/concepts/nav-accounting.md): how oracle prices feed into NAV
* [Denomination asset](/manage/denomination-asset.md): why Chamber reports everything in USD
* [Risks](/deposit/risks.md): depositor-side view of oracle risk