Issues adding LQ single bip range to active range
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.5k
- Forks
- 5.4k
- PR merge metrics
- No merged PRs in 30d
Description
Bug Description
UI not allowing adding both side to single bip on 0.01% while in range, it's forcing single sided. Also seems to have issues even setting up 1 bip ranges
used usdc/dai as example, but seems persistent
Steps to Reproduce
- Go to ...
or https://app.uniswap.org/#/add/0x6B175474E89094C44Da98b954EedeAC495271d0F/0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48/100?chain=mainnet - try to add a single bip range that is in range
...
Expected Behavior
UI would allow both sides in range during a single bip add, as well as no issues setting single bip range in UI
Additional Context
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 from the two linked add-liquidity URLs, using the listed single-bip in-range steps on Polygon and mainnet. Trace the add-liquidity UI flow to determine why both sides are forced into a single-sided position and why one-bip ranges fail; done means both sides can be added for an in-range single-bip position without setup errors.
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
- 30/100