Onchain Infra · Blockspace · 04 / 22
Blockspace & Ordering
Who gets in, in what order
Every block has limited room. Mempools, builders and sequencers decide which transactions go in and in what order, which is where MEV lives.
Where it connects
How It Works
- 01CollectPending transactions wait in a mempool or go to a sequencer.
- 02BuildA builder picks and orders them to fill the block.
- 03ProposeThe validator or sequencer publishes the block.
Designs
01
Proposer-builder separation
Specialist builders bid for the right to order.
02
Centralized sequencer
One operator orders an L2; fast, trusted.
03
Reserved lanes
Room set aside for a class of traffic, like payments.
Who Builds It
Across ecosystems, not one chain.
MEMEV-BoostEthereumFlashbots relay market for blocks
JiJitoSolanaBlock engine and bundles
EsEspressoRollupsShared sequencing and confirmations
ShShutterEthereum, GnosisEncrypted mempool against front-running
FlFlashblocksBaseSub-second preconfirmations
What to Compare
01
Who controls ordering
02
MEV exposure for users
03
Inclusion guarantees under load
On Tempo
On Tempo · In the protocol
Payment lanes reserve most of every block for transfers, so other traffic can't crowd payments out.
500M
Gas per block
≥420M
Reserved for payments
30M
General cap
Block #4,217,000
500M gasPayments ≥420M
General ≤30M
Shared 50M
NFT mint spike
Capped0 txs waiting for general space
Payroll run
Unaffected0
of ~10,000 transfers per block
Payment lane
Non-payment traffic capped so transfers always fit
Stateless classification
TIP-1045Payments detected from payload alone
Extended block format
System txs settle fees at block edges
Stripe
DoorDash
Felix Pago
Coastal Bank
Karta
ARQ
KAST
MoneyGram