钱包交易模拟警告披露雷达
本文正文暫以英文原文展示，翻譯版本需完成來源複核後再發布。
已验证事实边界
1. MetaMask says transaction simulations enhance security alerts but do not guarantee detection of all threats. 2. MetaMask describes URL, JSON-RPC method, chain ID and transaction data as data points used for security checks when alerts are on. 3. Phantom developer documentation says a connected web application can prompt the user for permission to send transactions on the user's behalf. 4. Phantom wallet skill guidance requires simulation-before-signing explanations for warnings, blocking conditions and expected asset changes. 5. Trust Wallet describes built-in risk monitoring tools, including Security Scanner, as part of its security posture. 6. A clean simulation or absent warning does not prove a signature cannot transfer assets, grant permissions or create a later loss path.
收起完整分析
决策矩阵
文章表格：可橫向滑動，或聚焦表格區域後使用方向鍵。
| Check | What it means | Practical action | Unknown to keep explicit |
|---|---|---|---|
| Domain identity | warnings often start from the web domain or dApp identity | verify domain through official channels before connecting | new legitimate domains that lack review history |
| Method scope | the JSON-RPC method tells whether the wallet is signing, sending or granting approval | write down the method and chain before confirmation | wallet UI differences across chains |
| Asset change | simulation may estimate balance or approval changes | compare expected and simulated asset movement | red-pill or conditional behavior that differs at execution |
| Warning severity | warning, malicious and unreviewed states require different stop rules | define which severity stops the action automatically | false positives and appeal process |
| Provider data | security checks can share transaction-related data with security providers | decide privacy tolerance before turning on alerts | which provider receives non-secret metadata on each chain |
| Manual stop rule | wallet warnings inform the user but cannot recover a signed loss | stop when approvals, authorities or spending limits are unclear | whether an already-signed approval must be revoked elsewhere |
来源地图
- MetaMask Help Center：How to manage security alerts to protect your wallet（metamask-security-alerts）
- Phantom Developer Documentation：Sending a Transaction（phantom-send-transaction-docs）
- Phantom Connect SDK：Phantom wallet skill guidance（phantom-wallet-skill-guidance）
- Trust Wallet：Security at Trust Wallet（trust-wallet-security）
控制说明
1. Domain identity
这一项要求读者先把公开来源翻译成操作规则。这里的含义是：warnings often start from the web domain or dApp identity。可执行动作是：verify domain through official channels before connecting。仍然未知的是：new legitimate domains that lack review history。因此本文不会把未知部分包装成收益承诺、牌照承诺、审批保证、恢复保证、结算保证、可用性保证、价格暗示或平台排名。
2. Method scope
这里的含义是：the JSON-RPC method tells whether the wallet is signing, sending or granting approval。可执行动作是：write down the method and chain before confirmation。仍然未知的是：wallet UI differences across chains。
操作测试也必须很窄。这就是本节保留边界的原因。
3. Asset change
这里的含义是：simulation may estimate balance or approval changes。可执行动作是：compare expected and simulated asset movement。仍然未知的是：red-pill or conditional behavior that differs at execution。
操作测试也必须很窄。这就是本节保留边界的原因。
4. Warning severity
这里的含义是：warning, malicious and unreviewed states require different stop rules。可执行动作是：define which severity stops the action automatically。仍然未知的是：false positives and appeal process。
操作测试也必须很窄。这就是本节保留边界的原因。
5. Provider data
这里的含义是：security checks can share transaction-related data with security providers。可执行动作是：decide privacy tolerance before turning on alerts。仍然未知的是：which provider receives non-secret metadata on each chain。
操作测试也必须很窄。这就是本节保留边界的原因。
6. Manual stop rule
这里的含义是：wallet warnings inform the user but cannot recover a signed loss。可执行动作是：stop when approvals, authorities or spending limits are unclear。仍然未知的是：whether an already-signed approval must be revoked elsewhere。
操作测试也必须很窄。这就是本节保留边界的原因。
仍需明确的未知项
- new legitimate domains that lack review history
- wallet UI differences across chains
- red-pill or conditional behavior that differs at execution
- false positives and appeal process
- which provider receives non-secret metadata on each chain
- whether an already-signed approval must be revoked elsewhere
实用结论
钱包交易模拟应被视为警告层，而不是签名安全保证。MetaMask 文档说明 security alerts 与 transaction simulation 帮助用户做决策，但不保证检测所有威胁；Phantom developer documentation 显示已连接应用可以通过钱包请求签名和发送交易，Phantom wallet skill guidance 要求在签名前模拟并解释 warnings 与 expected asset changes；Trust Wallet 描述 Security Scanner 等内置风险监控工具。实用结论是：签名前应记录 dApp domain、chain、method、simulated asset change、warning severity、shared data 与 manual stop rule，尤其是请求会改变 approval、authority、delegation 或 spending permission 时。 本文停在证据边界内，帮助读者决定下一步核验什么，而不是把公开文档改写成私人账户、钱包、回调、政策框架、结算路径或流动性头寸在任何未来条件下都能成功的承诺。