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
Right now, the only way to understand what MEV reward was received is to look for it manually inside the mev-geth logs. This method of data retrieval doesn't scale and is not really an idiomatic way. What I propose is to store each MEV block reward in the database, and make it retrievable remotely via RPC.
Implementation
Ideally, the MEV block reward should be accessible via these two options:
eth_getBlock request -> contains mevReward field.
mev_getReward RPC method -> returns the MEV reward for specific block. (I like this option more)
Also, it is crucial to have the correct reward recorded across all network nodes. This will require not just logging the reward on the mining node, but also implementing a standardized network-wide way to know the MEV reward of the block, so the MEV reward can be synced.
The text was updated successfully, but these errors were encountered:
We've discussed how we could do this but have not found any quick fix that would make it possible to isolate mevReward from other fees. This is something we will add to our long term roadmap.
Rationale
Right now, the only way to understand what MEV reward was received is to look for it manually inside the mev-geth logs. This method of data retrieval doesn't scale and is not really an idiomatic way. What I propose is to store each MEV block reward in the database, and make it retrievable remotely via RPC.
Implementation
Ideally, the MEV block reward should be accessible via these two options:
eth_getBlock
request -> containsmevReward
field.mev_getReward
RPC method -> returns the MEV reward for specific block. (I like this option more)Also, it is crucial to have the correct reward recorded across all network nodes. This will require not just logging the reward on the mining node, but also implementing a standardized network-wide way to know the MEV reward of the block, so the MEV reward can be synced.
The text was updated successfully, but these errors were encountered: