Curve Stableswap-NG 与 Uniswap v4 池子控制清单
已验证事实边界
1. Curve documents Stableswap-NG as a StableSwap AMM implementation with plain pools, metapools, rate-oracle support, rebasing-token support, ERC4626 support, dynamic fees and built-in oracles. 2. Curve plain-pool documentation warns production users not to set minimum output values such as _min_dy or _min_amount to zero or arbitrary numbers because MEV can frontrun or sandwich a transaction. 3. Uniswap v4 documentation says each liquidity pool can have its own hook contract attached to it. 4. Uniswap v4 documentation says the PoolManager is the singleton contract that holds pool state and coordinates swaps, liquidity and hook execution. 5. A Curve stable pool document does not prove the selected token pair is low risk, and a Uniswap hook document does not prove the attached hook is safe or simple. 6. The safe comparison separates asset type, invariant, hook or pool logic, oracle input, fee behavior, approval path, minimum output and post-transaction reconciliation.
收起完整分析
决策矩阵
文章表格：可横向滑动，或聚焦表格区域后使用方向键。
| Check | What it means | Practical action | Unknown to keep explicit |
|---|---|---|---|
| Pool object | Curve centers a deployed pool implementation while Uniswap v4 centers PoolManager plus pool parameters and optional hooks | identify the exact pool contract, hook address and router path before signing | whether the user interface exposes every relevant control |
| Asset fit | Stableswap-NG is documented for stable and rate-linked asset patterns, while hooks can attach custom behavior to v4 pools | map token type, rate oracle, rebasing behavior and hook behavior | whether a token upgrade or wrapper changes risk after deposit |
| Execution guard | minimum output and pool-specific callbacks are practical loss controls | set nonzero slippage bounds and read hook or pool behavior before approval | whether an aggregator overrides or hides the bound |
| Oracle and fee path | Curve mentions built-in oracles and dynamic fees while v4 hooks can alter pool behavior around swaps | record the source of price, fee and callback logic | whether moving averages lag during a market break |
| Wallet approval | both paths can expose token approvals or Permit flows before the swap or liquidity action | limit approvals and revoke unused permissions after testing | whether a router or hook can pull tokens later |
| Recovery evidence | a transaction receipt alone may not explain why output differed from expectation | store route, pool, hook, input, minimum output and event logs | whether support or protocol tooling can interpret the events |
来源地图
- Curve Knowledge Hub：Stableswap-NG: Overview（curve-ng-overview）
- Curve Knowledge Hub：Stableswap-NG Plain Pools（curve-plainpool）
- Uniswap Developers：Uniswap v4 Hooks（uniswap-v4-hooks）
- Uniswap Developers：Uniswap v4 PoolManager（uniswap-v4-poolmanager）
控制说明
1. Pool object
这一项要求读者把公开来源翻译成操作规则。这里的含义是：Curve centers a deployed pool implementation while Uniswap v4 centers PoolManager plus pool parameters and optional hooks。可执行动作是：identify the exact pool contract, hook address and router path before signing。仍然未知的是：whether the user interface exposes every relevant control。因此本文不会把未知部分包装成收益承诺、牌照承诺、审批保证、安全保证、恢复保证、平台排名或价格暗示。
2. Asset fit
这里的含义是：Stableswap-NG is documented for stable and rate-linked asset patterns, while hooks can attach custom behavior to v4 pools。可执行动作是：map token type, rate oracle, rebasing behavior and hook behavior。仍然未知的是：whether a token upgrade or wrapper changes risk after deposit。
操作测试也必须很窄。这就是本文坚持以清单形式呈现的原因。
3. Execution guard
这里的含义是：minimum output and pool-specific callbacks are practical loss controls。可执行动作是：set nonzero slippage bounds and read hook or pool behavior before approval。仍然未知的是：whether an aggregator overrides or hides the bound。
操作测试也必须很窄。这就是本文坚持以清单形式呈现的原因。
4. Oracle and fee path
这里的含义是：Curve mentions built-in oracles and dynamic fees while v4 hooks can alter pool behavior around swaps。可执行动作是：record the source of price, fee and callback logic。仍然未知的是：whether moving averages lag during a market break。
操作测试也必须很窄。这就是本文坚持以清单形式呈现的原因。
5. Wallet approval
这里的含义是：both paths can expose token approvals or Permit flows before the swap or liquidity action。可执行动作是：limit approvals and revoke unused permissions after testing。仍然未知的是：whether a router or hook can pull tokens later。
操作测试也必须很窄。这就是本文坚持以清单形式呈现的原因。
6. Recovery evidence
这里的含义是：a transaction receipt alone may not explain why output differed from expectation。可执行动作是：store route, pool, hook, input, minimum output and event logs。仍然未知的是：whether support or protocol tooling can interpret the events。
操作测试也必须很窄。这就是本文坚持以清单形式呈现的原因。
仍需明确的未知项
- whether the user interface exposes every relevant control
- whether a token upgrade or wrapper changes risk after deposit
- whether an aggregator overrides or hides the bound
- whether moving averages lag during a market break
- whether a router or hook can pull tokens later
- whether support or protocol tooling can interpret the events
实用结论
Curve Stableswap-NG 与 Uniswap v4 解决的是不同池子控制问题。Curve 文档把 Stableswap-NG 描述为面向稳定资产或带 rate oracle 资产的 AMM 实现，包含多种池型、内置 oracle、动态费用、交换函数，以及围绕 minimum output 的风险提示。Uniswap v4 文档则把 hooks 和 singleton PoolManager 描述为可扩展执行表面，每个池子可以附加自定义 hook 行为。实用结论不是抽象判断哪个 AMM 更好，而是在使用池子前核验 asset type、invariant、hook 或 pool logic、oracle behavior、fee path、minimum output、approval route 与 recovery path。 本文停在证据边界内，帮助读者决定下一步核验什么，而不是把公开文档改写成私人账户、钱包、API key、池子路径、稳定币余额、代币化资产或政策框架在任何未来条件下都能成功的承诺。
相关专题与工具:任选两家交易所对比Uniswap 平台档案与费率