Measures how Solana mainnet leaders order our own transactions in a block, by client: fee vs send order, 2,000+ live txs, spend capped, offline reproducible
-
Updated
Nov 4, 2026 - Python
Measures how Solana mainnet leaders order our own transactions in a block, by client: fee vs send order, 2,000+ live txs, spend capped, offline reproducible
Conflict-aware transaction reordering for Hyperledger Fabric, extended from the Serializer research.
Which sort key each Solana validator uses to order transactions in its block, and how strictly in time. Mainnet probes after Alpenglow: 16 validators, 8 clients, all raw data, one-command reproduction.
Inside the Block: How Solana Validators Order Transactions (Empirical & Architectural Research)
Empirical investigation of transaction ordering rules across Solana validator client forks (Agave, Jito, Firedancer, BAM) on Mainnet-Beta post-Alpenglow.
To associate your repository with the transaction-ordering topic, visit your repo's landing page and select "manage topics."