交易所 API Key IP 白名单与不活跃过期披露雷达

决策矩阵

来源地图

• OKX：OKX API Guide（s1）
• OKX：OKX API Agreement（s2）
• Binance Support：How to Create API Keys on Binance?（s3）
• Bitget API：REST API Documentation（s4）
• Kraken Support：API Key Security（s5）

控制说明

1. IP-bound trade and withdraw keys

这一项要求读者先把公开来源翻译成操作规则。这里的含义是：venues disclose different controls for keys that can trade, transfer or withdraw。可执行动作是：tag every venue record with permission type and whether IP binding is documented。仍然未知的是：private account exceptions and unsupported regional account variants。因此本文不会把未知部分包装成安全承诺、收益承诺、官方背书、审批保证、可用性保证或注册诱导。

2. Inactivity expiry

这里的含义是：OKX explicitly describes inactivity-expiry behavior for certain unbound keys。可执行动作是：schedule stale-key reviews rather than waiting for a production failure。仍然未知的是：whether other venues have undocumented or account-specific expiry rules。

3. Rotation evidence

这里的含义是：API agreements and help pages often make rotation a user-side duty after suspected compromise。可执行动作是：record the delete, disable and recreate path for every connected venue。仍然未知的是：whether old keys remain in CI secrets, local env files or third-party bots。

4. Radar scoring

这里的含义是：the radar should score disclosure completeness rather than hidden operational quality。可执行动作是：mark missing public evidence as unknown instead of fail or pass。仍然未知的是：future documentation changes after the radar snapshot。

5. Publication boundary

这里的含义是：this is original synthesis from public docs, not private penetration testing。可执行动作是：publish only source-mapped facts and avoid credential collection。仍然未知的是：user balances, API secrets, IP addresses and account-level security state。

仍需明确的未知项

• private account exceptions and unsupported regional account variants
• whether other venues have undocumented or account-specific expiry rules
• whether old keys remain in CI secrets, local env files or third-party bots
• future documentation changes after the radar snapshot
• user balances, API secrets, IP addresses and account-level security state

实用结论

本文最有价值的地方是克制。实用的交易所 API 雷达应在自动化上线前追踪三类公开披露字段：提现或交易 Key 是否需要 IP 绑定、未绑定 IP 的不活跃 Key 是否会过期、以及平台是否说明泄露后如何轮换或删除 Key。真正有用的输出是带日期的控制清单，而不是宣称某个平台最安全。 用户应获得一个更清楚的核验路径，而不是一个看似肯定、实则无法由公开证据承担的承诺。