The way to unify the order of classification of the Order of Ethereum Mempool
In recent years, there has been a pressing need for a unified classification command in Ethereum memories. For the unknown, Mempool is a critical component of the Ethereum network, responsible for the efficient management of the transactions received and the verification of its legitimacy.
Currently, different developers have proposed various classification orders to optimize performance and reduce latency. However, these proposals generally do not have a crucial aspect: agreement on transactions that give priority to the classification of mepools. In this article, we will explore why the current approach is defective and what is missing to obtain a unified order.
The problem with current approaches
One of the main problems with existing classification orders is the lack of clarity and consistency in the implementations of different developers. For example:
- Classification command proposals : Different proposals suggest rating variations, such as “first first”, “the last first” or even a custom algorithm that combines more factors.
- Priority Agreement : Developers can agree with certain priority rules, but not others, which leads to inconsistencies and possible conflicts to classify memories.
Proposed solution: classification after the first transaction n (80%)
To resolve these issues, we propose an alternative approach:
- Classification Command
: Classify Mempool transactions in the first N (or 80% of transactions) transactions that are at least 10 minutes.
- Confirmation : After classifying, confirming and transmitting the header from all parties involved.
Benefits of this approach
By adopting this unified approach, we can get more benefits:
- Improved Performance : Classification by the first transactions N reduces latency and minimizes the content between the implementations of different developers.
- Increased consistency
: With a single order of classification, developers are more likely to agree with prioritization rules, reducing conflicts and ensuring consistency in different mepool implementations.
- Improved security : By prioritizing transactions at least 10 minutes, we can reduce the likelihood that bad actors aim to try to explore bad classification requests.
The following steps
To change to a unified classification order in Ethereum memories, we recommend:
- Collaborative Development : Encourage developers from different teams and communities to contribute to the discussion and development of a single universally accepted order.
- Implementation guides : Establish clear steering lines for the implementation of the proposed classification order, including the required adjustments or changes in existing code codes.
Working together and adopting this unified approach, we can create a more effective, safer and scalable Ethereum network that will benefit from all stakeholders involved.