> For the complete documentation index, see [llms.txt](https://docs.bsc.lista.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bsc.lista.org/for-developer/multi-oracle.md).

# Multi-Oracle

## Why the Resilient Oracle exists

A single price feed is a single point of failure: a stale or manipulated answer becomes an unnecessary liquidation or an over-sized loan, with nothing to catch it.

The Resilient Oracle removes that by giving each asset up to three independent sources — a **main**, a **pivot** and a **fallback** — and cross-validating them against each other before a price is returned. A source that is disabled, missing, stale or reverting is skipped, and a price that falls outside the asset's configured bounds is rejected rather than used. Sources can be added or switched per asset without redeploying, so an asset's topology is configuration, not code.

Collateral assets are migrating onto it progressively, so the source set differs per asset — read an asset's configuration rather than assuming one.

<figure><img src="https://1802824789-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F60fXF9rALi6luWHVkkGg%2Fuploads%2F9TYeaAtk5CXCmgVKyYtH%2Fimage.png?alt=media&amp;token=f7d755be-bea6-4371-863e-9ff594dcdc44" alt=""><figcaption></figcaption></figure>

## Collateral configuration

Collateral pricing configuration is split across two pages; both sets of assets are priced by the same Resilient Oracle described above:

* [Standard Collaterals](/for-developer/multi-oracle/multi-oracle-standard.md) — BNB Chain and Ethereum Chain collaterals.
* [bStock Collaterals](/for-developer/multi-oracle/multi-oracle-bstock.md) — tokenized-equity (bStock) collaterals.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.bsc.lista.org/for-developer/multi-oracle.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.