
Uniswap needs no introduction and its upcoming version, Uniswap v4, reignites the protocol as a premier platform for developers. Uniswap v4 introduces Hooks, allowing developers to plug arbitrary solidity logic inside the swap lifecycle. Whether itβs pool creation, swaps, or liquidity modifications, developers can elect to execute solidity logic before and after an operation has happened.
Beyond hooks, v4 also introduces dynamic fees, flash accounting, ERC-6909 balances, and a singleton design β all to enable gas-efficient complex operations. As well, Position Manager in v4 was designed for complex operations and safe-staking.
From token-based fee discounts to MEV minimization, v4 provides an wide opportunity for researchers and developers β regardless of skillset.
Implement a hook, leveraging-first class features
Dynamic Fees - showcase potential hooks that rely on dynamic fees to reward LPs or swappers
Custom Curves - showcase hooks swapping on a custom curve
Hook Fees - showcase novel hook fee designs
Asynchronous Swaps / App-level sequencing - perform asynchronous swaps where output tokens are given a few blocks later
General Hooks - use of hook functions
Liquidity managing hooks - hooks which automate or streamline liquidity management
A proper interface is not required. Evidence of working code is more than sufficient, such as:
The category is for integrations with Uniswap v4 such as periphery contracts, developer infrastructure, user abstractions. Some ideas include, but are not limited to:
Pool Operators - contracts which unlock and call PoolManager
Batched liquidity operations - contracts which leverage Position Manager's command system for complex liquidity sequences
Liquidity Staking (Subscribers)
Developer tooling
User abstractions
A proper interface is not required. Evidence of working code is more than sufficient, such as:
An open track for innovation related to v4. The catch-all category for projects that do not fit above. Examples include, but are not limited to:
A proper interface is not required. Evidence of working code is more than sufficient, such as: