> For the complete documentation index, see [llms.txt](https://docs.jaspervault.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jaspervault.io/zhong-wen-wen-dang/faq/yong-xu-he-yue-bao-hu-ppfaq.md).

# 永续合约保护（PP）FAQ

### 永续合约保护（PP）是什么？

永续合约保护（PP）是 Jasper Vault 的核心保护功能，用户可以在永续合约仓位上开启保护，以更清楚地管理部分下行风险。

***

### 永续合约保护（PP）是保险吗？

不是传统保险。

它是一种风险管理工具，不保证盈利，也不保证完全避免亏损。

***

### 永续合约保护（PP）能避免爆仓吗？

不保证。

永续合约保护（PP）可以帮助管理部分风险，但用户仍需关注保证金、杠杆、强平价格和市场波动。

***

### 永续合约保护（PP）和止损有什么区别？

止损通常是在价格触发后直接平仓。

永续合约保护（PP）的目标是在用户继续持仓时提供保护。

其中「扫损无忧」场景可以帮助用户在止损价附近开启保护，而不是简单被扫损离场。

***

### 紧急护盾适合什么情况？

紧急护盾适合短时间突发行情、插针、数据公布或用户临时无法盯盘时使用。

***

### 扫损无忧适合什么情况？

扫损无忧适合用户担心止损价被短线插针触发，但仍希望保留仓位机会的情况。

***

### 夜间守护适合什么情况？

夜间守护适合睡觉、休息或长时间无法盯盘前使用。

***

### 重亏拯救适合什么情况？

重亏拯救适合仓位已经出现较大浮亏，但用户暂时不想立刻止损或平仓的情况。

***

### 为什么永续合约保护（PP）有时候很贵？

保护费用可能受到市场波动、保护期限、保护强度、仓位大小和流动性影响。

市场波动越大，保护成本可能越高。


---

# 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://docs.jaspervault.io/zhong-wen-wen-dang/faq/yong-xu-he-yue-bao-hu-ppfaq.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.