Ban 0x583163c...49d094 from the pool

Smooth
1

After the acceptance of the new Terms of Service, user 0x583163cbe883c26053e4d327f1da8c33ae49d094 has not proposed a single MEV block.

This link details the blocks proposed and their MEV differential.
https://mryukonc.gitlab.io/Results/Accounts/0x583163cbe883c26053e4d327f1da8c33ae49d094.json

This user owes 1.0020694 ETH to the pool as calculated by the MEV differential between blocks proposed and MEV available that block.

The user will be able to be unbanned after returning this amount to the pool as per the Terms of Service.

1 Like
2

Good stuff.

Quick note regarding the VanillaETH and LostMEV values - the amount actually lost/owed to the pool is the difference between those two. It’s not stored in the json file because it’s a calculated value.

"VanillaETH": 0.21490946,
"LostMEV": 1.0020694,

Amount owed to the pool is: 1.0020694 - 0.21490946 = 0.78715994 ETH

That number is shown on the various stats pages under the LostΞ column:

https://mryukonc.gitlab.io/Results/LostMEV.html

1 Like
3

Thanks for the correction!

4

Actually, you know what – I was wrong about that.

The LostMEV is actually the amount beyond the vanilla amount that was lost.

So it’s not the difference between the two numbers, as I incorrectly said. It’s the value that payload.de reports as the Difference / Offset which is indeed the amount beyond the basic vanilla block.