# 介紹

## AutoSAFU (平台保險機制) <a href="#autosafu-protocol-insurance" id="autosafu-protocol-insurance"></a>

Autofarm团队决定，将经由[币安MVB计划](https://www.binance.com/zh-CN/blog/421499824684901587/%E5%B8%81%E5%AE%89%E5%90%AF%E5%8A%A8%E6%9C%80%E5%85%B7%E4%BB%B7%E5%80%BC%E5%BC%80%E5%8F%91%E8%80%85MVB%E5%8A%A0%E9%80%9F%E5%99%A8%E8%AE%A1%E5%88%92)所提供的[Gas瓦斯费返回奖励](https://www.binance.org/en/leaderBoard)，全数投入到Autofarm 平台协议保险AutoSAFU中，而这些金额将会在Autofarm使用者资金受到意外损失的时候，用来补偿平台使用者。Autofarm目前在[二三月的奖励计划中中排名第二](https://www.binance.org/en/blog/buidl-reward-program-updates-with-3-59-million-dollar-distributed-as-february-reward/)。\
‌\
AutoSAFU资金将会透过Gnosis Safe Multisig进行监管。 [**Gnosis Safe Multisig**](https://gnosis-safe.io/) 可以要求钱包内的资产进行转移时，必须经过多重签章核准，以提供数位资产更多严格的保护。保险多重签章制度已经启用，目前交由以下使用者保管:  Autofarm Treasury,  [Autofarm Deployer](https://twitter.com/_mildgiraffe?s=21) (@\_mildgiraffe), [@fmnxl](https://twitter.com/fmnxl?s=21), and [@spenguin16](https://twitter.com/spenguin16).

AutoSAFU的使用(如对外投资以赚取利息)以及保险当有需要进行分配补偿的时候，将会需要5名使用者中的3名进行核准同意才能执行。(细节执行流程将在拟定后公告)

这个计划将成为其余外部平台保护之外的更多一层保障，详情也可以参阅我们的[公开文章](https://medium.com/autofarm-network/cn-%E5%BB%BA%E7%AB%8B%E6%9B%B4%E5%AE%89%E5%85%A8%E7%9A%84autofarm%E5%B9%B3%E5%8F%B0-424951dee555)。

[**Gnosis Safe Multisig**](https://gnosis-safe.io/)**应用已经启动于以下钱包连结:**[ **0x41360098859C1351D6a65c4965b1FcF3A6aB5010**](https://bscscan.com/address/0x41360098859C1351D6a65c4965b1FcF3A6aB5010)

{% embed url="<https://medium.com/autofarm-network/cn-%E5%BB%BA%E7%AB%8B%E6%9B%B4%E5%AE%89%E5%85%A8%E7%9A%84autofarm%E5%B9%B3%E5%8F%B0-424951dee555>" %}


---

# Agent Instructions: 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:

```
GET https://autofarm.gitbook.io/autofarm-network/chinese/autosafu/jie-shao.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
