Can't choose WETH when adding back liquidity to a ETH/X position, forced to use ETH
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.5k
- Forks
- 5.4k
- PR merge metrics
- No merged PRs in 30d
Description
Is your feature request related to a problem? Please describe.
I'm pretty sure (I've tested with position creation) WETH is cheaper to use than ETH. Even if it's only by a small margin, it's worth it to let the users use WETH instead of ETH.
So you can create a position using WETH but not add liquidity back to it...
Describe the solution you'd like
Add an option to use WETH instead of ETH when injecting liquidity into an already existing position.
Describe alternatives you've considered
None
Additional context
Gas crisis :-D every bit counts
thanks
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 tracing the existing position-creation and add-liquidity flows described in the issue, then compare how ETH and WETH are handled in each flow. Identify the entry point for adding liquidity to an existing position and the related tests, if present. Done means users can choose WETH instead of ETH when replenishing an eligible ETH/X position, with the existing flow still working.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- blockchain, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100