> For the complete documentation index, see [llms.txt](https://docs.stonksnipebot.best/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stonksnipebot.best/cn/an-quan-yu-gui-ze/feng-xian-yu-chang-jian-wen-ti.md).

# 风险与常见问题

### 核心风险

任何识别方法都不能保证项目真实性、合约安全、成交或盈利。每笔新代币交易都可能造成全部损失。

### 交易风险

* 滑点过低可能导致交易失败；滑点过高可能造成严重不利成交。
* 流动性刚建立时，报价和可买数量可能迅速变化。
* 公开交易可能受到抢先交易、夹击或其他 MEV 行为影响。
* 延迟、流动性变化、代币税、Hook、外部控制器和 MEV 仍然存在。
* RPC、WSS 或网络故障可能造成延迟、漏报或确认状态不一致。
* 失败的链上交易通常仍会消耗 Gas。

### 常见问题

#### 安全 CA 是否保证交易？

不保证。还需要已就绪验证路由、有效报价、模拟、gas、余额、签名、广播与回执确认。

#### 程序已部署是否表示实盘已就绪？

不表示。正式 Launcher/V3 路由必须先通过官方前端与链上证据验证。

#### 系统能保证项目真实吗？

不能。验证只能降低不确定性，不能消除合约、市场或发行方风险。

#### 为什么交易会失败？

常见原因包括流动性变化、余额或 gas 不足、滑点、代币税、Hook、外部控制器、MEV、revert 和广播失败。

#### 系统是否保存私钥？

会以 AES-256-GCM 加密形式保存。系统为了签名具备解密能力，因此属于托管钱包。

#### 在哪里管理钱包？

仅在私聊中管理。群组通知不会公开钱包操作或其他用户的执行结果。


---

# 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.stonksnipebot.best/cn/an-quan-yu-gui-ze/feng-xian-yu-chang-jian-wen-ti.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.