Uniswap / Uniswap/interface

allow users to send transactions via flashbots or other private transaction service

Open
#2,202 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

improvement p1
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.
user transactions can be frontrun, resulting in them receiving a worse price than quoted up to their slippage tolerance

Describe the solution you'd like
users should be able to submit transactions to private mempools where the fee is negotiated directly with the private mempool in order to avoid their trades being sandwiched when they go into the public mempool

Additional context
this protection is not perfect. some transactions can still be sandwiched due to reorgs after the transaction is included. this will also likely need a router change. https://github.com/Uniswap/uniswap-v3-periphery/issues/165

see https://hackmd.io/@flashbots/use-cases

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

The issue names no files, tests, or entry points. Start by tracing the interface's transaction submission path and read the linked Uniswap v3 periphery issue; done means supporting private-mempool submission while accounting for the stated reorg limitation.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
blockchain
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.