Block Packing
Core Protocol · Abyss
The process by which the leader validator assembles transactions into a block during its leader slots, subject to the 48M compute unit cap per block, the 12,500 non-vote transaction limit, and account-level write-lock constraints. The scheduler prioritizes transactions by fee-per-CU, attempts to maximize parallelism across non-conflicting account sets, and packs entries until the compute budget or slot time is exhausted. Block packing efficiency directly determines a leader's fee revenue and the network's effective throughput.