Uniswap / Uniswap/interface

[Bug] Tick Spacing not Respected from Add Liquidity Link to URL Query Params

Open
#7,939 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
TypeScript
Stars
5.5k
Forks
5.4k
PR merge metrics
No merged PRs in 30d

Description

📱 Interface Affected

Which application are you experiencing issues with?


🧩 App Version

  • Version (if known):
  • 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

  1. Go to this liquidity pool, which is set up with tickspacing = 10: https://app.uniswap.org/explore/pools/base/0x870198ffb454503d5ce1b698c94bc98198c874d61e8a2994dd6e01ee04535f89
  2. Click on 'Add Liquidity'
  3. Inspect the URL's query parameters in the destination URL, expect tickspacing = 10:
https://app.uniswap.org/positions/create/v4
  ?currencyA=0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913
  &currencyB=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

Image

🧾 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.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the Add Liquidity flow from the linked Base pool and inspect how its tick spacing becomes the /positions/create/v4 URL query parameter. Trace the link and query-parameter construction from that entry point; done means the destination URL preserves tickSpacing=10 for this pool instead of using 60.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.