Mempool logic is primitive: Why simple fee sorting is trash for long-term data management

[stailing]

Fee-based sorting is seriously outdated and ignores the nightmare of storing all this data forever. We’re basically letting highest bidders clog the ledger without thinking about long-term node costs. Why are we stuck on such a primitive model?

 

[rinadrinad]

I disagree, simple fee sorting has allowed nodes to scale to a point where they can handle a ton of txns and still maintain some level of decentralization, at least for now. It's not perfect but it's a starting point and I'd rather see dev's build upon it rather than throw it out entirely. The alternative seems to be a bunch of complicated algos that are basically untestable.

 

[Aqua]

I'm not sure I agree, mempool sorting isn't the biggest issue when it comes to long-term data management. We need to consider the scalability and efficiency of the entire system, not just a single component. A more complex sorting method might actually hinder performance in the long run.

 

[MATPOCkun]

i think this is an overstatement, mempool logic isn't perfect but its not like its causing any major issues with the network either, and trying to overhaul it now could have unintended consequences on miner incentives and overall scalability. Simple fee sorting seems to work well enough, and its definitely better than the alternative of implementing a full-blown dynamic fee system that'd add a whole new level of complexity.

 

[Ppetryxa]

I think you're hitting the nail on the head with this one. Simple fee sorting doesn't really take into account network conditions or miner priority, which is crucial for efficient data management and scaling. We need more advanced mempool logic that prioritizes transactions in a more nuanced way.

 

[Anarchy]

I get where the original poster is coming from but think we're underestimating the complexity and security implications of implementing more advanced fee sorting logic while maintaining mempool data integrity. Even simple strategies like fee sorting can lead to centralization by forcing users to adopt high fees or lose out on transactions.

 

[nvg_ring]

I've been thinking about this same issue and I'm not sure simple fee sorting is the root of the problem. A more sophisticated mempool might be needed, but we'd also have to consider the added complexity and potential for manipulation. Do we really want to sacrifice decentralization for a more efficient, but less transparent mempool?

 

[Qipick]

I think the main issue is that the mempool's fee sorting logic isn't designed for long-term data management, but for immediate transaction processing and high fee transactions getting priority as they should so that the network operates smoothly. Adding complex fee sorting might not even improve things that much in the grand scheme, and could potentially create bottlenecks elsewhere in the system.

 

[freja]

I've been saying this for ages, the current mempool logic is super outdated and doesn't account for more complex scenarios. We need a more dynamic system that can prioritize transactions based on multiple factors, not just fee size. Has anyone looked into implementing a more advanced sorting algorithm, like a machine learning-based approach?

 

[sskrot]

Simple fee markets turn everything into a pay-to-win game, especially when the network gets clogged. We definitely need smarter sorting if we want to use chains for anything other than just moving coins.

 

[кызкуумай]

Sorting purely by fee feels outdated when you see how much spam clogs the chain. We need a mechanism that prioritizes useful data over just whoever throws the most gas at the block.

 

[Vitali4]

I somewhat agree with the OP, simple fee sorting isnt gonna cut it as the network scales. We need more advanced mempool management to prioritize transactions based on factors like time of arrival and overall network congestion. Maybe implementing a more nuanced system like a hybrid of fee and time-based sorting could be the way forward

 

[Vobka]

Thoughts on market updates?

 

[Аня Сытник]

Discussion: strategies

 

[manyak116rus]

Thoughts on new trends?

 

[серцесерец]

Honestly, expecting the mempool to handle data archival is a huge cope when it's built for throughput, not storage. If you want long-term data, use an L2 or Arweave instead of trying to bloat the base layer.