> 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/zh-cn/kai-fa-zhe-zhuan-qu/multi-oracle.md).

# 多 Oracle

## 弹性预言机存在的原因

单一价格馈送是单点故障：过时或被操纵的答案会导致不必要的清算或过大的贷款，而没有任何机制来捕捉这些问题。

弹性预言机通过为每种资产提供最多三个独立来源——**主**、**枢轴**和**后备**——并在返回价格之前相互交叉验证它们，从而消除了这一问题。被禁用、缺失、过时或回退的来源会被跳过，超出资产配置范围的价格会被拒绝而不是使用。可以为每种资产添加或切换来源而无需重新部署，因此资产的拓扑结构是配置而不是代码。

抵押资产正在逐步迁移到弹性预言机上，因此每种资产的来源集合不同——请阅读资产的配置而不是假设某种配置。

## 抵押品配置

抵押品定价配置分为两个页面；两组资产都由上述的弹性预言机定价：

* [标准抵押品](/zh-cn/kai-fa-zhe-zhuan-qu/multi-oracle/multi-oracle-standard.md) — BNB链和以太坊链抵押品。
* [bStock抵押品](/zh-cn/kai-fa-zhe-zhuan-qu/multi-oracle/multi-oracle-bstock.md) — 代币化权益（bStock）抵押品。


---

# 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/zh-cn/kai-fa-zhe-zhuan-qu/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.