A draft Solana protocol change aimed at improving transaction fairness was not adopted in late September. The proposal, documented in a closed pull request, sought to make block production more transparent by requiring validators to verify that transactions within each batch followed a specific priority order. It would not have altered how validators selected transactions or divided them into batches. Instead, it would have allowed observers to check whether the recorded sequence matched a calculated priority score. The score, based on fees and rewards, would have been an integer derived from a formula involving a multiplier and a one-unit guard in the denominator. Equal-priority transactions could still appear in either order, and simple vote transactions were exempt. The draft did not establish a single priority queue for an entire slot but focused on within-batch consistency. Validators would have been able to detect violations during block replay but would not have been required to reshuffle transactions. The proposal also did not prevent leaders from prioritizing their own transactions by paying priority fees to themselves. The change was discussed in the context of preventing overly small batches that would limit meaningful comparisons. A minimum batch size of 64 data shreds was suggested for all but the final batch, though this threshold was not guaranteed to alter existing behavior. Without data on current batch distributions, the practical impact remained unclear. The proposal also raised concerns about added latency during batch formation. The draft was ultimately closed without merging, leaving the question of transaction ordering unresolved for further discussion.