Исследование с проверкой источников: Curve Stableswap NG VS
Текст статьи показан в проверенном английском оригинале. Перевод будет добавлен после проверки источников.
Verified Fact Boundary
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.
Свернуть
Decision Matrix
Таблица статьи: прокрутите по горизонтали или установите фокус на области таблицы и используйте клавиши со стрелками.
| 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 |
Source Map
- 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)
Control Notes
1. Pool object
Pool object is the point where public documentation must become an operating rule. In this package, it means Curve centers a deployed pool implementation while Uniswap v4 centers PoolManager plus pool parameters and optional hooks. The practical action is to identify the exact pool contract, hook address and router path before signing. The unresolved edge is whether the user interface exposes every relevant control, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, safety guarantee, recovery promise, platform ranking or price implication.
2. Asset fit
Asset fit is the point where public documentation must become an operating rule. In this package, it means Stableswap-NG is documented for stable and rate-linked asset patterns, while hooks can attach custom behavior to v4 pools. The practical action is to map token type, rate oracle, rebasing behavior and hook behavior. The unresolved edge is whether a token upgrade or wrapper changes risk after deposit, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, safety guarantee, recovery promise, platform ranking or price implication.
The operating test is narrow.
3. Execution guard
Execution guard is the point where public documentation must become an operating rule. In this package, it means minimum output and pool-specific callbacks are practical loss controls. The practical action is to set nonzero slippage bounds and read hook or pool behavior before approval. The unresolved edge is whether an aggregator overrides or hides the bound, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, safety guarantee, recovery promise, platform ranking or price implication.
The operating test is narrow.
4. Oracle and fee path
Oracle and fee path is the point where public documentation must become an operating rule. In this package, it means Curve mentions built-in oracles and dynamic fees while v4 hooks can alter pool behavior around swaps. The practical action is to record the source of price, fee and callback logic. The unresolved edge is whether moving averages lag during a market break, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, safety guarantee, recovery promise, platform ranking or price implication.
The operating test is narrow.
5. Wallet approval
Wallet approval is the point where public documentation must become an operating rule. In this package, it means both paths can expose token approvals or Permit flows before the swap or liquidity action. The practical action is to limit approvals and revoke unused permissions after testing. The unresolved edge is whether a router or hook can pull tokens later, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, safety guarantee, recovery promise, platform ranking or price implication.
The operating test is narrow.
6. Recovery evidence
Recovery evidence is the point where public documentation must become an operating rule. In this package, it means a transaction receipt alone may not explain why output differed from expectation. The practical action is to store route, pool, hook, input, minimum output and event logs. The unresolved edge is whether support or protocol tooling can interpret the events, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, safety guarantee, recovery promise, platform ranking or price implication.
The operating test is narrow.
Known Unknowns
- 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
Practical Takeaway
Curve Stableswap-NG and Uniswap v4 solve different pool-control problems. Curve documentation frames Stableswap-NG as an AMM implementation for stable or rate-linked assets, with pool variants, built-in oracles, dynamic fees, exchange functions and warnings around minimum output values. Uniswap v4 documentation frames hooks and the singleton PoolManager as an extensible execution surface where each pool can attach custom hook behavior. The useful outcome is not to ask which AMM is better in the abstract, but to verify asset type, invariant, hook or pool logic, oracle behavior, fee path, minimum output, approval route and recovery path before using a pool. The article stops at the evidence boundary. It helps the reader decide what to inspect next without converting public documentation into a promise that a private account, wallet, API key, pool route, stablecoin balance, tokenized asset or policy framework will work under every future condition.
Темы и инструменты:Сравнить две биржиUniswap: профиль и комиссии