> 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/shi-yong-zhi-nan/ju-ji-ce-le.md).

# 狙击策略

### 模式

每个钱包选择激进或稳妥模式。模式决定已验证候选何时可以创建交易意图。

| 模式 | 触发条件                         |
| -- | ---------------------------- |
| 激进 | 安全 CA，以及可交易且具有有效流动性的主 ETH 池。 |
| 稳妥 | 满足激进模式条件，并等待主池 LP 永久锁定。      |

### Launcher 狙击费率

每个托管钱包分别设置“最高 Launcher 买入附加费”和“最高 Launcher 卖出费”。费率不是固定值。

当前可选上限为 0%、5%、10%、20%、50% 和 100%。默认值为 0%，表示只接受读取到的 0% Launcher 费率。

真实交易前，系统必须读取实时费率。无法读取费率，或费率超过该钱包上限时，系统不签名、不广播。

以下成本和限制彼此独立：

* Launcher 买入附加费和 Launcher 卖出费。
* AMM 池费和滑点。
* token tax 和 1% 平台手续费。

学习钱包完成已验证的真实买卖后，系统会从可验证 getter 与成交结果持续采样买入和卖出费率。采样用于积累早期附加费衰减曲线。

能否得到完整曲线取决于正式 Launcher 暴露的数据和实际样本。发布前不作保证。

{% hint style="warning" %}
费率上限是风控阈值。它不保证最终成交价格或交易成功率。
{% endhint %}

### 从信号到执行

合格信号会为每个已启用钱包创建独立意图。它不会绕过钱包限额。

每次执行都要求已就绪的验证路由、固定 codehash、费率上限、报价、滑点上限、`eth_call` 模拟、gas 估算、ETH 余额、签名、广播和回执确认。

没有路由就没有交易。

### 仓位控制

买入金额设定预期 ETH 输入额。滑点限制可接受的报价变化。

gas 倍数调整预估 gas。止损与分档止盈按钱包生效。

止盈比例基于剩余仓位，不基于初始仓位。

{% hint style="warning" %}
激进模式可能早于主池 LP 永久锁定。它承担更高的池子和发行风险。
{% 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/shi-yong-zhi-nan/ju-ji-ce-le.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.