[Bug] v4 position on Base cannot be closed or managed when out of range
Nobody has claimed this yet.
- 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?
- Web (app.uniswap.org)
- Wallet Extension (wallet.uniswap.org)
- Wallet Mobile App
- iOS
- Android
- Both
🧩 App Version
- Version (if known):
- Production build
- Development build
💻 System / Environment Info
Please provide details about your environment:
- Browser (name + version): Chrome (macOS)
- OS / Platform: macOS
- Device: MacBook (Desktop)
- Wallet used: MetaMask
- Network: Base
🔁 Steps to Reproduce
- Open app.uniswap.org
- Connect wallet and open an existing v4 position on Base
- Wait until the position goes out of range
- Try to remove liquidity or close the position via the UI
- Observe that the action cannot be completed
✅ Expected Behavior
It should be possible to remove liquidity or close a v4 position even when it is out of range.
❌ Actual Behavior
What actually happened?
When the position is out of range, the UI does not allow removing liquidity or closing the position.
The position only becomes manageable again once the price re-enters the range.
📸 Screenshots or Screen Recording
Please upload any relevant screenshots or recordings to help us understand the issue better.
🧾 Additional Context
Any extra details? (e.g. logs, error messages, recent updates, beta flags enabled, etc.)
⚠️ Please redact or avoid sharing sensitive data such as private keys, seed phrases, or personally identifying info.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue through app.uniswap.org with an existing v4 position on Base, using the listed Chrome/macOS and MetaMask setup. Trace the web flow for removing liquidity or closing an out-of-range position; done means both actions work while the position remains out of range.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- blockchain, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100