Uniswap v4 hooks、权限逻辑与池子风险披露雷达
本文正文暫以英文原文展示，翻譯版本需完成來源複核後再發布。
已验证事实边界
1. Uniswap v4 documentation describes v4 as a protocol architecture with hooks and singleton-related design. 2. Uniswap hooks documentation explains hook-based custom logic in the pool lifecycle. 3. Uniswap PoolManager documentation is a source for the core manager surface. 4. Uniswap create-pool documentation is a source for pool creation flow and developer context. 5. A hook-enabled pool can require a different disclosure checklist than a simple token-pair comparison. 6. A radar should separate hook address, permission behavior, approval surface, route, warning, code evidence and stop rule.
收起完整分析
决策矩阵
文章表格：可橫向滑動，或聚焦表格區域後使用方向鍵。
| Check | What it means | Practical action | Unknown to keep explicit |
|---|---|---|---|
| Hook identity | the hook address is part of the pool's operating logic | record hook address and source page before approval | whether a front end hides or abbreviates the hook |
| Lifecycle point | custom logic can run at defined points in the pool lifecycle | state which lifecycle event changes user risk | whether later hook upgrades or wrappers change behavior |
| Approval surface | wallet approvals can expose assets before the user understands hook behavior | stop before unlimited approval until the route is documented | whether approval is routed through an aggregator |
| PoolManager route | core routing matters for state and settlement assumptions | map PoolManager, pool key and hook route | whether the route shown in UI matches transaction calldata |
| Disclosure quality | TVL and fee data do not prove hook safety | require source code, audit or verified warning evidence | whether code verification covers the deployed address |
| Evidence hygiene | wallet and transaction evidence can expose private addresses | retain public contract address, tx hash if needed and stop rule only | whether screenshots reveal balances or strategy timing |
来源地图
- Uniswap Developers：Uniswap v4 Protocol Overview（uniswap-v4-overview）
- Uniswap Developers：Uniswap v4 Hooks（uniswap-v4-hooks）
- Uniswap Developers：PoolManager（uniswap-v4-poolmanager）
- Uniswap Developers：Create a Pool（uniswap-v4-quickstart）
控制说明
1. Hook identity
这一项要求读者把公开来源翻译成操作规则。这里的含义是：the hook address is part of the pool's operating logic。可执行动作是：record hook address and source page before approval。仍然未知的是：whether a front end hides or abbreviates the hook。因此本文不会把未知部分包装成收益承诺、牌照承诺、审批保证、安全保证、恢复保证、平台排名或价格暗示。
2. Lifecycle point
这里的含义是：custom logic can run at defined points in the pool lifecycle。可执行动作是：state which lifecycle event changes user risk。仍然未知的是：whether later hook upgrades or wrappers change behavior。
操作测试也必须很窄。这就是本文坚持以清单形式呈现的原因。
3. Approval surface
这里的含义是：wallet approvals can expose assets before the user understands hook behavior。可执行动作是：stop before unlimited approval until the route is documented。仍然未知的是：whether approval is routed through an aggregator。
操作测试也必须很窄。这就是本文坚持以清单形式呈现的原因。
4. PoolManager route
这里的含义是：core routing matters for state and settlement assumptions。可执行动作是：map PoolManager, pool key and hook route。仍然未知的是：whether the route shown in UI matches transaction calldata。
操作测试也必须很窄。这就是本文坚持以清单形式呈现的原因。
5. Disclosure quality
这里的含义是：TVL and fee data do not prove hook safety。可执行动作是：require source code, audit or verified warning evidence。仍然未知的是：whether code verification covers the deployed address。
操作测试也必须很窄。这就是本文坚持以清单形式呈现的原因。
6. Evidence hygiene
这里的含义是：wallet and transaction evidence can expose private addresses。可执行动作是：retain public contract address, tx hash if needed and stop rule only。仍然未知的是：whether screenshots reveal balances or strategy timing。
操作测试也必须很窄。这就是本文坚持以清单形式呈现的原因。
仍需明确的未知项
- whether a front end hides or abbreviates the hook
- whether later hook upgrades or wrappers change behavior
- whether approval is routed through an aggregator
- whether the route shown in UI matches transaction calldata
- whether code verification covers the deployed address
- whether screenshots reveal balances or strategy timing
实用结论
Uniswap v4 通过 hooks 让池子逻辑更可扩展，因此有用的雷达不能停在 token pair、fee tier 或 TVL。Uniswap 文档把 v4 描述为带有 singleton architecture 与 hook-based custom logic 的协议，hooks 文档说明 hook 可以在池子生命周期的特定点运行。决策雷达需要在钱包把某个池子当成普通 AMM 流动性前，识别 hook address、permissioned behavior、PoolManager route、approval surface、面向用户的 warning、source code 或 audit evidence，以及暂停条件。 本文停在证据边界内，帮助读者决定下一步核验什么，而不是把公开文档改写成私人账户、钱包、API key、池子路径、稳定币余额、代币化资产或政策框架在任何未来条件下都能成功的承诺。
相關專題與工具:任選兩家交易所比較Uniswap 平台檔案與費率