You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
The text was updated successfully, but these errors were encountered:
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.
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:
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)
The text was updated successfully, but these errors were encountered: