Bybit SMP Trade Group 与订单控制准备清单
本文正文暫以英文原文展示，翻譯版本需完成來源複核後再發布。
已验证事实边界
1. Bybit self-match-prevention documentation describes execution policies including cancel maker, cancel taker and cancel both. 2. Bybit SMP documentation describes SMP Trade Group behavior and UID-level relationships. 3. Bybit changelog records updates to SMP behavior for compliant sites and derivative or spot contexts. 4. Bybit user-setting configuration documentation exposes smpType as a trade-behaviour field. 5. Bybit place-order documentation includes smpType and client order identity fields in the order-control surface. 6. The public documentation does not prove a private account's institution status, group membership, live order cleanup, future site behavior or final execution outcome.
收起完整分析
决策矩阵
文章表格：可橫向滑動，或聚焦表格區域後使用方向鍵。
| Check | What it means | Practical action | Unknown to keep explicit |
|---|---|---|---|
| SMP policy | self-match prevention is an execution policy with several possible outcomes, not one universal cancel rule | write the intended maker/taker/cancel-both policy before order placement | whether the live match path will encounter the intended counterparty condition |
| Trade-group boundary | SMP group membership can change the matching relationship across UIDs and subaccounts | record UID, group assumption and standing-order cleanup before changing groups | private institutional eligibility and support-managed group changes |
| Site-specific behavior | Bybit documentation records compliant-site behavior that can differ from global assumptions | record account site and product type before applying a default smpType | future regional rollout and product availability |
| Order identity | smpType interacts with ordinary order controls such as orderLinkId and order-state reporting | store non-secret client order id, request id and final order-state evidence separately | race conditions, rejected orders and later order-book state |
| Stop condition | SMP cannot be treated as reliable if group, site, product and standing-order state are unknown | pause automation until account site, UID scope, default policy and cleanup rule are written | private account status, support outcome and future API revisions |
来源地图
- Bybit API Documentation：Self Match Prevention（bybit-smp）
- Bybit API Documentation：V5 Changelog（bybit-v5-changelog）
- Bybit API Documentation：Get Trade Behaviour Config（bybit-user-setting-config）
- Bybit API Documentation：Place Order（bybit-place-order）
控制说明
1. SMP policy
这一项要求读者把公开来源翻译成操作规则。这里的含义是：self-match prevention is an execution policy with several possible outcomes, not one universal cancel rule。可执行动作是：write the intended maker/taker/cancel-both policy before order placement。仍然未知的是：whether the live match path will encounter the intended counterparty condition。因此本文不会把未知部分包装成收益承诺、牌照承诺、审批保证、安全保证、恢复保证、平台排名或价格暗示。
2. Trade-group boundary
这里的含义是：SMP group membership can change the matching relationship across UIDs and subaccounts。可执行动作是：record UID, group assumption and standing-order cleanup before changing groups。仍然未知的是：private institutional eligibility and support-managed group changes。
操作测试也必须很窄。这就是本文坚持以清单形式呈现的原因。
3. Site-specific behavior
这里的含义是：Bybit documentation records compliant-site behavior that can differ from global assumptions。可执行动作是：record account site and product type before applying a default smpType。仍然未知的是：future regional rollout and product availability。
操作测试也必须很窄。这就是本文坚持以清单形式呈现的原因。
4. Order identity
这里的含义是：smpType interacts with ordinary order controls such as orderLinkId and order-state reporting。可执行动作是：store non-secret client order id, request id and final order-state evidence separately。仍然未知的是：race conditions, rejected orders and later order-book state。
操作测试也必须很窄。这就是本文坚持以清单形式呈现的原因。
5. Stop condition
这里的含义是：SMP cannot be treated as reliable if group, site, product and standing-order state are unknown。可执行动作是：pause automation until account site, UID scope, default policy and cleanup rule are written。仍然未知的是：private account status, support outcome and future API revisions。
操作测试也必须很窄。这就是本文坚持以清单形式呈现的原因。
仍需明确的未知项
- whether the live match path will encounter the intended counterparty condition
- private institutional eligibility and support-managed group changes
- future regional rollout and product availability
- race conditions, rejected orders and later order-book state
- private account status, support outcome and future API revisions
实用结论
Bybit 的 self-match-prevention 文档把 SMP 变成账户与订单控制问题，而不是泛化安全标签。Bybit 描述了 SMP execution policies、UID-level 与 trade-group behavior、user setting configuration，以及 smpType 等 order parameters；其 changelog 也记录了特定站点的 SMP 行为更新。实际清单是：依赖 SMP 防止 self-trading 前，先记录 account site、UID group、default smpType、orderLinkId policy、standing-order cleanup rule 与 WebSocket order-state evidence。 本文停在证据边界内，帮助读者决定下一步核验什么，而不是把公开文档改写成私人账户、钱包、API key、池子路径、稳定币余额、代币化资产或政策框架在任何未来条件下都能成功的承诺。