Compare
Four documents, the same five questions.
No throughput league table and no yield. The cells are what this library is willing to say about the text.
| Question | Uniswap v4 Core |
|---|---|
| What the text proposes | One contract holds many pools. Hooks are code that runs before and after swaps and liquidity changes. Flash accounting settles balances at the end of a lock. A hook can change the rules v3 users took for granted. |
| Who may write | Hayden Adams and the Uniswap v4 authors |
| What is settled | A PoolManager singleton. |
| Load-bearing assumption | A pool with a hook is not the v3 invariant. Read the hook or you do not know the product. |
| What this library says afterwards | Hooks can be upgraded if their own admin allows it. Immutability is a property of that hook, not of the word v4. |
| Rights | Official external source only |