Bad

I wonder what the engagement value of 115792089237316195423570985008687907853269984665640564039457584007913129639935 is in dollars. Praying for your payout ser

As promised @PatrickAlphaC, my official application to come work with you, or someone. My resignation letter to current job is already in the post. Looking forward to hearing from you.

And we receive an address as expected:

This now compiled in forge (yay). I spun up a super complex test:

No sane human would manually step through, so I reached out to my good friend Foundry. Loaded up the contract locally, patched it a ‘little’ bit to run in a newer version of Solidity. This included change byte to bytes1, and then modifying the bytes to string function:

There's an obvious function that we, the deployer, would want to use to make $$$. start() Reading this, the immediate sus is the fact this instantly sets up a transfer... The address defined appeared to be an MEV function... okay?

Loading the code locally, first thing we see, is the Sol version - ignore that. Imports can often indicate the external code interacted with. In this case, Uniswap.

I made $6.9 Trillion with this MEV BOT and you can too!!! ⛳️⛳️ Nah just kidding, read on to see why 🧵

As devs, we all contemplate our code a few weeks after launch where it's too late to do anything so I thought I'd look back and think on what I'd do differently next time.

From my previous work on loops, I chose to use a do/while loop here (gas save). Some basic external checks are done first. As I knew this iterator was unlikely to overflow, the increment was unchecked. Some quick math is done to calculate the reward and away we go.