Uniswap / Uniswap/interface

Add a warning for Fee on transfer and Rebasing tokens when migrating or adding liquidity to V3

Open
#1,840 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

improvement
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.
With the issues of FoT or Rebase tokens breaking in V3 , People who don't know are migrating and having issues

Describe the solution you'd like
when a user attempts to add Liquidity or Migrate their V2 LP tokens, A red pop up warning should show Stating something like

"Fee-on-transfer and Rebasing tokens will not function correctly on v3. If you do not know if your token is one of these Do not create a pool or Migrate prior to finding out. Migrating or creating a pool with one of these tokens can cause a loss of funds."

Describe alternatives you've considered
Prefer the pop up, but even a short red text on the add and migrate pages would at least serve as a warning.

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

Start by locating the add-liquidity and V2 LP migration pages in the interface. Review how those pages display user warnings, then add the requested red warning and verify that it appears when users add liquidity or migrate, with wording that covers fee-on-transfer and rebasing tokens and the risk of loss.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
blockchain, frontend
Issue type
Feature
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.