[Bug] Tick Spacing not Respected from Add Liquidity Link to URL Query Params
๐ฑ Interface Affected
Which application are you experiencing issues with?
- [x] Web (app.uniswap.org)
- [ ] Wallet Extension (wallet.uniswap.org)
- [ ] Wallet Mobile App
- [ ] iOS
- [ ] Android
- [ ] Both
๐งฉ App Version
- Version (if known):
- [x] Production build
- [ ] Development build
๐ป System / Environment Info
Please provide details about your environment:
- Browser (name + version): Chrome
- OS / Platform (e.g. iOS 17, Windows 11, Android 14):
- Device (e.g. iPhone 14 Pro, Pixel 7, MacBook Pro 2023):
- Wallet used (e.g. Uniswap Wallet, MetaMask, Rainbow): Metamask
- Network (e.g. Ethereum Mainnet, Arbitrum, Base, etc.): Base
๐ Steps to Reproduce
- Go to this liquidity pool, which is set up with tickspacing = 10: https://app.uniswap.org/explore/pools/base/0x870198ffb454503d5ce1b698c94bc98198c874d61e8a2994dd6e01ee04535f89
- Click on 'Add Liquidity'
- Inspect the URL's query parameters in the destination URL, expect tickspacing = 10:
https://app.uniswap.org/positions/create/v4
?currencyA=0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913
¤cyB=0xb1599cde32181f48f89683d3c5db5c5d2c7c93cc
&chain=base
&hook=0xBc5F29A583a8d3ec76e03372659e01a22feE3A80
&fee={"feeAmount":1000,"tickSpacing":60,"isDynamic":true}
&priceRangeState={"priceInverted":false,"fullRange":true,"minPrice":"","maxPrice":"","initialPrice":""}
&depositState={"exactField":"TOKEN0","exactAmounts":{}}
โ Expected Behavior
Tick Spacing is correctly set to 10:
&fee={"feeAmount":1000,"tickSpacing":10,"isDynamic":true}
โ Actual Behavior
Tick Spacing set to 60:
&fee={"feeAmount":1000,"tickSpacing":60,"isDynamic":true}
๐ธ Screenshots or Screen Recording
๐งพ Additional Context
I still think this correctly adds to the USDC/DCA pool with Tick Spacing 10 since all of my other tools and smart contracts show that it is doing that. My concern is that someone makes a tick spaced pool of 60 and then suddenly liquidity is getting fractured across 2 different pools.
โ ๏ธ Please redact or avoid sharing sensitive data such as private keys, seed phrases, or personally identifying info.
I'll also add that I don't feel comfortable making LPs through the UI with tickspacing=10 like I need since I can't have an assurance that argument will be respected for dynamic pools.