> For the complete documentation index, see [llms.txt](https://axon-finance.gitbook.io/axon-finance-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://axon-finance.gitbook.io/axon-finance-docs/huang-pi-shu-d-jie-suan-wei-jia-he-gui/d1-settlement.md).

# D.1 稳定币结算引擎

> **设计状态**：proposed design。支持的稳定币清单待定（[附录 II](/axon-finance-docs/huang-pi-shu-fu-lu/appendix-parameters.md)）。

## D.1.1 结算是一等能力

在通用链上，一笔稳定币转账是一次 ERC-20 合约调用——稳定币只是「一个恰好叫 USDC 的 token」。AXON 把**稳定币结算做成链层原语**：稳定币余额是账户的一等字段（[B.3.1](/axon-finance-docs/huang-pi-shu-b-gong-shi-yu-zhang-ben/b3-state.md) 的 `balances`），结算由结算引擎直接处理，而非某个合约的内部记账。好处：结算路径更短、gas 可预测、且能与账户抽象/合规网关/最终性证明原生集成。

## D.1.2 多资产模型

账户余额是资产到金额的映射：

$$\mathsf{balances} : \mathsf{AssetId} \to \mathbb{Z}\_{\geq 0}$$

$\mathsf{AssetId}$ 涵盖原生 gas 资产与多种法币锚定稳定币。设计原则（proposed）：

* **多资产、不绑定单一发行方**——降低对任一稳定币的依赖。
* **法币锚定优先**——首发聚焦美元等法币锚定稳定币，它们是当下跨境结算主力。
* **资产元数据**：每个 $\mathsf{AssetId}$ 关联发行方、精度、合规标签（供 [D.3](/axon-finance-docs/huang-pi-shu-d-jie-suan-wei-jia-he-gui/d3-compliance.md) 网关判定）与喂价源（[D.2](/axon-finance-docs/huang-pi-shu-d-jie-suan-wei-jia-he-gui/d2-oracle.md)）。

## D.1.3 结算原语

结算引擎提供的核心原语（均为原子操作，要么全成要么全废）：

| 原语                            | 语义                                                                                                                  |
| ----------------------------- | ------------------------------------------------------------------------------------------------------------------- |
| `Transfer(a → b, asset, amt)` | 单资产转账，余额守恒                                                                                                          |
| `BatchSettle([...])`          | 多笔转账原子结算（批量收单/代发）                                                                                                   |
| `PvP(a↔b, x↔y)`               | 支付对支付：两资产原子互换，无一方先付风险                                                                                               |
| `Escrow / Conditional`        | 条件结算：满足谓词（如收货确认、或预言机证明带单场次已结算，[E.3.4](/axon-finance-docs/huang-pi-shu-e-payfi-xie-yi-ji-zhi/e3-copy-trading.md)）才释放 |

**余额守恒**是结算引擎的不变式（invariant）：对任一资产，除铸造/销毁（由发行方经授权路径）外，结算前后总量恒定：

$$\forall, \mathsf{asset}:\quad \sum\_{a} \mathsf{balances}\[a]\[\mathsf{asset}] = \text{const}$$

此不变式在每笔结算后可被校验，是反双花（[B.5.2](/axon-finance-docs/huang-pi-shu-b-gong-shi-yu-zhang-ben/b5-finality.md)）在结算层的体现。

## D.1.4 原子性与最终性

结算的原子性由执行层保证：`BatchSettle`/`PvP` 内的所有转账在同一 $\delta\_{\mathsf{tx}}$（[C.1.4](/axon-finance-docs/huang-pi-shu-c-zhang-hu-chou-xiang-yu-ai-shou-quan/c1-account-abstraction.md)）中执行，任一失败则整体回滚——不存在「A 付了、B 没付」的半成品。

结算的最终性由 [B.5](/axon-finance-docs/huang-pi-shu-b-gong-shi-yu-zhang-ben/b5-finality.md) 保证：结算交易 `Finalized` 后不可逆。结合 [B.3.4](/axon-finance-docs/huang-pi-shu-b-gong-shi-yu-zhang-ben/b3-state.md) 的可证明状态根，结算引擎为每笔结算提供**可验证收据**——外部系统（法币出入金、商户后台、审计）凭状态根 + 包含证明即可确认「此笔已 T+0 结算、金额确定、不可逆」，无需信任单一节点。这是「稳定币即时结算 Rail」（白皮书 [4.1](/axon-finance-docs/part-iv-payfi-yin-qing/part4-payfi/4-1-settlement-rail.md)）的协议兑现。

## D.1.5 与货币市场的接口

结算引擎为 PayFi 货币市场（[E.1](/axon-finance-docs/huang-pi-shu-e-payfi-xie-yi-ji-zhi/e1-money-market.md)）提供底层记账：浮存金、应收账款融资、清算的资金划转都经结算原语执行，共享同一套余额守恒与最终性保证——货币市场无需重新实现记账，只在其上表达信贷逻辑。

***

*下一节：*[*D.2 预言机与喂价安全*](/axon-finance-docs/huang-pi-shu-d-jie-suan-wei-jia-he-gui/d2-oracle.md)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://axon-finance.gitbook.io/axon-finance-docs/huang-pi-shu-d-jie-suan-wei-jia-he-gui/d1-settlement.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.