잠깐… 나만의 읽기 환경을 만들어 보세요.
글꼴과 테마는 화면 설정에서 설정하세요. 눈의 편안함도 중요합니다.
다음 장을 불러오고 있습니다…
A version of the Uniswap automated market maker architecture built around a shared pool manager and optional hooks that customize pool behavior.
브라우저의 읽어주기 지원을 확인하는 중…
이 읽기 자료는 현재 영어로 제공됩니다. 인터페이스에는 선택한 언어가 적용됩니다.
영어 원문 읽기 →Uniswap v4's architecture places pool management in a singleton contract rather than requiring a wholly separate core contract for each pool. Its hook system allows additional logic at defined points in a pool's lifecycle. The official documentation and core repository describe these components. This means that naming the protocol version does not fully describe a pool: a particular hook and its permissions can materially change the trading or liquidity experience.
A user interacts with a pool identified by its assets and configuration, potentially including a hook. Shared accounting can net obligations across operations before final settlement, reducing unnecessary intermediate transfers. As an illustrative example, a hook might alter fee behavior or add checks around an operation. The exact behavior comes from the deployed code and configuration; it should not be inferred solely from a familiar token pair or from the interface branding.
A well-understood core does not automatically make every extension safe. Review the hook's code, upgradeability, permissions, external dependencies, and expected effects on swaps and withdrawals. Also distinguish liquidity-provider revenue from token-holder rights or company revenue. Documentation for v3 cannot be applied mechanically to v4 because architectural and integration details differ. For reproducible research, record the network, pool identifier, deployment addresses, and software version rather than linking only to an undated protocol homepage.