Solana SIMD-0649 Proposal Fails to Resolve Transaction Order Dispute

Solana (SOL) developer discussions around the SIMD-0649 proposal, intended to enhance transaction processing fairness, have not reached agreement. The Solana Foundation announced on August 27 that a proposed change requiring mandatory priority sorting within transaction batches was under discussion. The goal is to make transaction ordering within a slot more predictable.
The core of SIMD-0649 would allow validators to invalidate blocks if higher-fee transactions are recorded after lower-fee ones within the same batch. However, this does not determine whether transactions are included in a block. Block producers retain authority over which transactions to include, where to place them in batches, and where to split batches.
The proposal also requires each batch excluding the last one to contain at least two FEC sets (equivalent to 64 data shards), aiming to reduce overly small batches that could render verification merely formal. Public measurements of actual batch sizes on the network are unavailable, and it remains unclear how this minimum standard would affect block producer behavior.
Concerns were raised during review that block producers might close batches at favorable times to separate conflicting transactions, though no evidence shows such practices have been used on mainnet. CryptoSlate reported on September 25 that the relevant pull request was closed without merging, while GitHub indexing still shows it as open.
The Solana Foundation has separately required some validators under delegated criteria to use FIFO or fee-based scheduling within 50 milliseconds of transaction arrival in TPU, prohibiting censorship or delays beyond allowed batch times. This operational standard differs from protocol-level consensus rules that would uniformly fix transaction inclusion and batch boundaries for all block producers.
A Reddit post described the proposal as a philosophical shift toward deterministic transaction ordering similar to traditional exchanges, though this reflects individual community opinion rather than official validator or industry stance. No announcement confirms SIMD-0649's implementation on mainnet, with key metrics like batch size distribution, frequency of competing transactions in the same batch, and impact on latency remaining unquantified.
The discussion highlights a separation between post-processing verification mechanisms for transaction order and block producers' authority to choose which transactions to include. Blockchain fairness discussions often depend on who determines transaction sequence and who captures revenue from that process. Even if SIMD-0649 is revived, the proposal's unchanged authority for block producers over transaction inclusion and batch boundaries makes it difficult to interpret as a guarantee of best execution or MEV prevention.
Korean Source
This article is an English localization of a Korean-language crypto news report. Original headline: 솔라나 SIMD-0649, 배치 순서만 검증…생산자 권한은 그대로