# MEV Committee -- Oct/Nov Report **URL:** \ **Category:** dYdX Chain\ **Created:** [November 27, 2024, 5:28pm UTC](https://dydx.forum/t/mev-committee-oct-nov-report/3191 "2024-11-27T17:28:26Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![Govmos](https://dub1.discourse-cdn.com/flex013/user_avatar/dydx.forum/govmos/32/820_2.png) [@Govmos](https://dydx.forum/u/Govmos)\ **Post date:** [December 4, 2024, 7:34am UTC](https://dydx.forum/t/mev-committee-oct-nov-report/3191/3 "2024-12-04T07:34:45Z")
> [@mev\_council](#): > > In October and November, the Committee continued its monitoring of block discrepancies across validators, identifying potential performance issues and some potential malicious activity. Our findings suggest that empty blocks were a result of misconfiguration at the node level, and we are seeing improvements following changes. Order matching trends indicate possible issues with peering. The initiative to monitor and evaluate performance and execution reliability is truly invaluable, particularly as it stems from a community-funded effort. These are the kinds of advanced features typically associated with a maturing ecosystem. By focusing on the finer details that validators might not always prioritize but are crucial for long-term efficiency, you’ve highlighted the importance of independent monitoring. This episode clearly demonstrates the necessity of such oversight—not only to address potential malicious activity but also to enhance the chain’s operational precision, as evidenced by the improvements made here. Thank you for your continued commitment. Govmos [![pro-delegators-sign](https://europe1.discourse-cdn.com/flex013/uploads/dydx/original/1X/3d138289b87945115dfe59a6604e139bf36aeb94.png)](https://dydx.forum/t/validator-introduction-pro-delegators/1487) --- _[View the full topic](https://dydx.forum/t/mev-committee-oct-nov-report/3191)._