A protocol change enabling validators to automatically share block revenue (priority fees and MEV tips) with their delegators through an on-chain mechanism. Validators set a commission rate for block revenue, and the protocol distributes the remainder to delegators at epoch boundaries based on their stake proportion. Available in Agave 3.0+.
Start with the shortest useful explanation before going deeper.
A protocol change enabling validators to automatically share block revenue (priority fees and MEV tips) with their delegators through an on-chain mechanism. Validators set a commission rate for block revenue, and the protocol distributes the remainder to delegators at epoch boundaries based on their stake proportion. Available in Agave 3.0+.
Use the quick analogy first so the term is easier to reason about when you meet it in code, docs, or prompts.
Think of it as part of the chain machinery that keeps ordering, execution, or consensus moving.
Place the term inside its Solana layer so the definition is easier to reason about.
Consensus, leader rotation, slots, epochs, and the runtime.
Turn the term from vocabulary into something operational for product and engineering work.
This term unlocks adjacent concepts quickly, so it works best when you treat it as a junction instead of an isolated definition.
Use this compact block when you want to give an agent or assistant grounded context without dumping the entire page.
SIMD-123 (Block Revenue Sharing) (simd-123) Category: Core Protocol Definition: A protocol change enabling validators to automatically share block revenue (priority fees and MEV tips) with their delegators through an on-chain mechanism. Validators set a commission rate for block revenue, and the protocol distributes the remainder to delegators at epoch boundaries based on their stake proportion. Available in Agave 3.0+. Aliases: Block Revenue Sharing Related: Validator, Delegator, Priority Fee, MEV (Maximal Extractable Value)
Use glossary context, relationships, mental models, and builder paths to get structured answers instead of generic chat output.
Optional: paste Anchor, Solana, or Rust code so the Copilot can map primitives back to glossary terms.
The Copilot will answer using the current term, related concepts, mental models, and the surrounding glossary graph.
These branches show which concepts this term touches directly and what sits one layer beyond them.
A node that participates in the Solana network by validating transactions, voting on blocks, and (when selected as leader) producing new blocks. Validators run the Agave, Firedancer, or Jito client software, require significant hardware (128+ GB RAM, high-core CPU, NVMe SSD), and earn rewards from inflation and transaction fees.
A SOL holder who delegates tokens to a validator's stake without running a node themselves. Delegators earn a share of inflation rewards proportional to their stake, minus the validator's commission (typically 0-10%). Delegation is non-custodial—the delegator retains the ability to redelegate or withdraw at any time.
An optional additional fee paid on top of the base fee to increase the likelihood that a transaction is processed quickly by the current leader, expressed as a price in micro-lamports per compute unit (CU). The total priority fee equals (compute unit price × compute unit limit) / 1,000,000 lamports. Leaders sort transactions in their queue by fee-per-CU, so setting a competitive priority fee is the primary mechanism for ensuring reliable transaction landing during congestion.
The profit a block producer (leader) or sophisticated trader can extract by controlling the ordering, inclusion, or exclusion of transactions within a block — including strategies like front-running, back-running, sandwich attacks, and arbitrage. On Solana, MEV dynamics differ from Ethereum because there is no public mempool; transactions are forwarded directly to the current leader, making latency and validator relationships central to MEV capture. The Jito infrastructure provides the dominant MEV marketplace on Solana through bundles and tips.
These are the next concepts worth opening if you want this term to make more sense inside a real Solana workflow.
These entries are easy to mix up when you are reading quickly, prompting an LLM, or onboarding into a new layer of Solana.
A formal specification document describing proposed and accepted changes to the Solana protocol, analogous to Ethereum's EIPs. SIMDs are categorized as Standard (Core, Networking, Interface) or Meta, and require supermajority validator stake-weighted voting (66.67%) to pass. Notable SIMDs include SIMD-33 (Timely Vote Credits), SIMD-123 (Block Revenue Sharing), SIMD-228 (Market-Based Emissions), and SIMD-326 (Alpenglow).
A set of entries produced by a leader during a single slot. A block contains transactions bundled into entries, each with a PoH hash proving ordering. Blocks are broken into shreds for network propagation via Turbine. Maximum block size is limited by compute units (48M CU cap per block) rather than byte size.
The number of blocks produced in the ledger since the genesis block. Block height increments only for slots that successfully produce a block (skipped slots do not increment it), so block height is always less than or equal to the current slot number. Block height is accessible via the getBlockHeight RPC method and the Clock sysvar.
Glossary entries become useful when they are connected. These links are the shortest path to adjacent ideas.
A node that participates in the Solana network by validating transactions, voting on blocks, and (when selected as leader) producing new blocks. Validators run the Agave, Firedancer, or Jito client software, require significant hardware (128+ GB RAM, high-core CPU, NVMe SSD), and earn rewards from inflation and transaction fees.
A SOL holder who delegates tokens to a validator's stake without running a node themselves. Delegators earn a share of inflation rewards proportional to their stake, minus the validator's commission (typically 0-10%). Delegation is non-custodial—the delegator retains the ability to redelegate or withdraw at any time.
An optional additional fee paid on top of the base fee to increase the likelihood that a transaction is processed quickly by the current leader, expressed as a price in micro-lamports per compute unit (CU). The total priority fee equals (compute unit price × compute unit limit) / 1,000,000 lamports. Leaders sort transactions in their queue by fee-per-CU, so setting a competitive priority fee is the primary mechanism for ensuring reliable transaction landing during congestion.
The profit a block producer (leader) or sophisticated trader can extract by controlling the ordering, inclusion, or exclusion of transactions within a block — including strategies like front-running, back-running, sandwich attacks, and arbitrage. On Solana, MEV dynamics differ from Ethereum because there is no public mempool; transactions are forwarded directly to the current leader, making latency and validator relationships central to MEV capture. The Jito infrastructure provides the dominant MEV marketplace on Solana through bundles and tips.
These entries live beside the current term and help the page feel like part of a larger knowledge graph instead of a dead end.
A clock mechanism that cryptographically proves the passage of time between events. PoH uses a sequential SHA-256 hash chain where each output becomes the next input, creating a verifiable ordering of events without requiring consensus. The leader produces ~400,000 hashes per slot (~400ms), and any validator can verify the sequence in parallel, enabling Solana's high throughput by removing the need for validators to agree on time.
Solana's custom BFT consensus algorithm built on top of Proof of History. Tower BFT uses PoH as a clock to reduce communication overhead in traditional PBFT from O(n²) to O(n). Validators vote on forks with exponentially increasing lockout periods—each consecutive vote doubles the lockout, making rollbacks progressively more expensive. A fork is finalized when it reaches supermajority (66.7%+ of stake).
A time window during which a designated leader validator can produce a block. Each slot lasts approximately 400 milliseconds. Slots are numbered sequentially from genesis and grouped into epochs of 432,000 slots (~2-3 days). Not every slot produces a block—a skipped slot means the leader was offline or too slow.
A set of entries produced by a leader during a single slot. A block contains transactions bundled into entries, each with a PoH hash proving ordering. Blocks are broken into shreds for network propagation via Turbine. Maximum block size is limited by compute units (48M CU cap per block) rather than byte size.