> 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/qian-bao-yu-an-quan.md).

# 钱包与安全

### 托管模式

本产品使用**托管钱包**。用户可以在 Telegram 中创建新钱包或导入已有私钥，系统必须在用户授权交易时解密私钥并完成签名。因此这不是非托管钱包，也不能表述为系统永远无法接触私钥。

每位用户最多可创建五个钱包。每个钱包独立配置备注、目标、模式、金额、费率上限和仓位规则。

### 私钥如何保存

私钥不会以明文写入数据库。保存前使用服务器本机主密钥加密，每条记录包含独立随机参数与完整性校验。标准查询和日志不会输出明文私钥或原始签名交易。

### 创建与导入

* **创建钱包：**系统生成新的链上地址和私钥，加密后保存。
* **导入钱包：**用户提交私钥后，系统校验地址并加密保存；导入行为意味着该私钥会进入托管环境。
* **查看余额：**通过 Robinhood Chain RPC 读取地址余额，不需要私钥。
* **导出私钥：**仅在用户主动请求时临时展示，并应在短时间后自动删除消息。任何已看到或保存该内容的人都可控制钱包。

导入私钥的 Telegram 消息会尽可能删除。导出消息采用剧透遮罩，并自动删除。

### 使用建议

* 只存入策略需要的资金和 Gas 余额。
* 不要导入存放主要资产、长期持仓或其他链资产的钱包。
* 导出私钥后，在安全环境中离线备份；不要截图、转发或发送给客服。
* 停止使用后，将剩余资产转出。

### 通知与学习

实盘先由指定学习钱包验证。学习钱包买入和卖出确认后，可释放全部托管钱包的交易闸门。

群组只接收 CA 通知及学习钱包的交易和手续费结果。其他用户的执行结果仅私聊本人。

{% hint style="danger" %}
不要分享私钥、Bot Token、RPC URL、管理员密码或私人运营地址。
{% endhint %}


---

# 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/qian-bao-yu-an-quan.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.