Web3 is centralized and inefficient

Re:Web3 is centralized and inefficient by landemva on Wednesday March 23, 2022 @03:17PM (#30782180)

Running your own node neither counters nor prevents front running your transactions. If you send tx to standard mempool, the tx can be seen and front run.

There are existing solutions for the narrow use case you seem to have - flashbots and a few others. And they have cost savings to you of not running your tx (saving eth gas fees) if your tx submission does not win.

[ Parent | on HN ]

Re:Web3 is centralized and inefficient by TheCowboy on Wednesday March 23, 2022 @10:51PM (#30785957)

I explained in my other comment, but I see no mention any of those aspects of countering a sandwich botter.

[ Parent | on HN ]

Re:Web3 is centralized and inefficient by landemva on Thursday March 24, 2022 @12:11AM (#30786309)

Front run + back run is sandwich. Front running has also been called miner extractable value. This is now called maximal extractable value.

You may want to look a little further, or not.

https://github.com/flashbots/pm

'... mitigating the negative externalities of Maximal Extractable Value ...'

[ Parent | on HN ]