Solana's SIMD-0649 batch ordering rule closed without merging on Sept. 25
CryptoSlate reported that Solana's SIMD-0649 pull request, which would enforce fee-priority order inside transaction batches, closed on Sept. 25 without merging.
Why it matters
Traders trying to predict where an order will land still face leader discretion, because the check that would have made within-batch order inspectable and enforceable did not merge. With one reporting outlet and no published batch-size data, the immediate significance is limited to Solana's validator community.
Key facts
The SIMD-0649 pull request closed on Sept. 25 without merging.
Reported by CryptoSlate
Under the draft, non-exempt transactions in each entry batch would have to appear in non-increasing priority order.
Reported by CryptoSlate
A validator replaying a block would compare recorded transaction priorities and treat a violation as an invalid block.
Reported by CryptoSlate
Block producers, known as leaders, would still choose which transactions to include and how to divide them into batches.
Reported by CryptoSlate
The proposed consensus check would not establish one priority queue for an entire slot.
Reported by CryptoSlate
The check would not reshuffle transactions into the correct sequence after a leader received them.
Reported by CryptoSlate
Batch-size data was not available, leaving the rule's effect on actual trading outcomes unresolved.
Reported by CryptoSlate
What happened
CryptoSlate reported that Solana's SIMD-0649 pull request, a draft rule for transaction ordering, closed on Sept. 25 without merging. The draft would have required non-exempt transactions in each entry batch to be recorded in non-increasing priority order, and a validator replaying a block would compare their recorded priorities and treat a violation as an invalid block. CryptoSlate said block producers, known as leaders, would still pick which transactions enter a block and where each batch begins and ends, so the rule would not create one priority queue across an entire slot, and it would not reshuffle transactions into the right sequence after receiving them. CryptoSlate also noted that no batch-size data was available, which leaves the rule's effect on where orders actually land unresolved. No other outlet in the desk's set has reported the closure.
How the story developed
- Resolution
SIMD-0649 pull request closed without merging
The proposed within-batch fee-priority ordering rule did not reach the Solana ledger, and CryptoSlate said the narrower trade-off goes back for further discussion.
- First report
First report by CryptoSlate
Solana’s plan for fairer trades stalls as block producers still choose which orders get in
- Update
CryptoSlate reports the closure
The only outlet in the desk's set on this story, describing the draft's scope, what leaders would keep, and the missing batch-size data.
Affected entities
Original sources
| Publisher | Report | Role | Published |
|---|---|---|---|
| CryptoSlate Crypto media | Solana’s plan for fairer trades stalls as block producers still choose which orders get in | Original |