Uniswap / Uniswap/interface

UI Bug: Conflicting price unit display (DOGE/LINK) leads to incorrect LP range setting

Open
#7,990 0 comments 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
✅ Web (app.uniswap.org)

🧩 App Version
✅ Production build

💻 System / Environment Info
Browser: [Chrome 120.0]

OS / Platform: [Windows 11]

Device: [Desktop PC]

Wallet used: [any]

Network: Ethereum Mainnet

🔁 Steps to Reproduce
Go to app.uniswap.org

Navigate to "Pool" → "New Position"

Select DOGE as Token 1 and LINK as Token 2

Observe the price displays in the range setup section

✅ Expected Behavior
Price should be displayed consistently in one unit format (either LINK/DOGE or DOGE/LINK) throughout the interface with clear labels.

❌ Actual Behavior
Interface shows price in conflicting units simultaneously:

"New price 96,900135 DOGE = 1 LINK" (DOGE per LINK)

"Current price 0,01032 DOGE/LINK" (DOGE per LINK, different value)

"Current price 96,9001 LINK/DOGE" (LINK per DOGE)

This creates confusion when setting price ranges, as users cannot determine which unit to use for min/max price inputs.

📸 Screenshots or Screen Recording

Image Image

🧾 Additional Context
Risk: This UI bug can lead to financial loss. If users input price ranges in the wrong unit format, their liquidity may become inactive or be instantly arbitraged.

First reported by: maxim_zvuchit_solidno 303204316393766923 on Dec 9, 2025
GitHub username: torgrin-lab

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 issue in app.uniswap.org through Pool → New Position with DOGE and LINK selected, then trace the New Position price display and range inputs. Compare the displayed units and input interpretation; done means all price values use one clearly labeled format and range setting no longer mixes reciprocal units.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.