Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ethereum MEV capabilities #151

Open
douglasgalico opened this issue Nov 27, 2024 · 1 comment
Open

Ethereum MEV capabilities #151

douglasgalico opened this issue Nov 27, 2024 · 1 comment

Comments

@douglasgalico
Copy link

In order to support Flashbots / MEV-Share , there are some endpoints that can be integrated to near-ca in order to make them works from near-ca:

  • eth_callBundle - for simulation
  • mev_simBundle - for simulation using MEV-Share new bundle spec
  • mev_sendBundle - for MEV-Share submission
  • eth_sendBundle - for Flashbots integration (older bundle format)
  • eth_sendPrivateTransaction - Submitting into private mempool
  • eth_sendPrivateRawTransaction - Submitting raw transaction to private mempool.

To think: cancel endpoints are needed from near-ca ?

Also expanding ethereum to some L2s , can other private mempools be supported as well? Like Merkle for Base and FastLane for Polygon? (Maybe also Jito for Solana in future)

@bh2smith
Copy link
Collaborator

Shouldn't forget MEV Blocker

One thing to note is that this library's CLI capabilities are not really the primary use case. This is intended to be a library for other front ends and is also the primary dependency of Near Safe: https://github.com/BitteProtocol/near-safe

So the front end user of this library rarely calls "eth_sendRawTransaction" to a public mempool, but rather sends to whatever RPC they want.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants