Uniswap v4 to launch in Q3 following Ethereum’s Dencun upgrade

The Uniswap Foundation — the organization supporting the decentralized finance (DeFi) protocol Uniswap — announced the launch date to the protocol’s v4 after the upcoming Dencun upgrade on Ethereum. 
In a post on X, the foundation shared a roadmap containing its plans for the new rollout. The organization highlighted that, at the moment, it is in the “Code Freeze” phase, where it is doing core code completion, testing, gas optimization, security enhancements and finalization of the periphery.
Uniswap Foundation team will rely on audit firms and a community audit contest to check v4’s code. The team believes Uniswap v4 should be the “most rigorously audited code ever deployed on Ethereum.” Simultaneously, the decentralized exchange will be deployed to the testnet as the team makes final adjustments.
According to the Uniswap Foundation, the third phase pushes Uniswap v4 into the Ethereum mainnet in the third quarter of 2024. The organization highlighted that this was a tentative date, depending on the status of the upcoming Dencun upgrade on Ethereum.
As Cointelegraph previously reported, the Ethereum network’s Dencun upgrade was activated on the Goerli testnet on Jan. 17. The upgrade introduces several Ethereum Improvement Proposals (EIPs), such as EIP-4844, which allows proto-danksharding, a featured aimed at reducing layer2 transaction fees.
The Goerli deployment for the Dencun upgrade experienced a four-hour delay. However, the upgrade’s deployment on the Sepolia testnet — the second of three Ethereum testnets — was completed without incident on Jan. 31. Following the second testnet, the Dencun upgrade finished the third phase of testing after its deployment to the Holesky testnet on Feb. 7.
On Feb. 8, Ethereum developer Tim Beiko announced that the upgrade is coming to the mainnet at “slot 8626176.” Blockchain research firm Nethermind highlighted that this will be on March 13, 2024, at 1:55:35 pm UTC. The date was decided by Ethereum developers in a call on Feb. 8, following the successful deployment to the Holesky testnet.