Could an inclusion list guarantee your Ethereum transaction gets in?
What are inclusion lists in Ethereum? FOCIL could require builders to include valid public-mempool transactions, subject to block space and fork status.
Onchain Daily Newsroom4 min read

FOCIL inclusion lists could give a valid, fee-paying public-mempool transaction a route into a block when builders ignore it, provided the block has room. Fork-choice rules make attesters reject blocks that fail to include listed transactions. To go further on how transaction inclusion connects to MEV, visit Flashbots.
What is an inclusion list in Ethereum?
An inclusion list is a set of pending transactions that validators ask a block to include. Under FOCIL, short for Fork-choice enforced Inclusion Lists, a committee of 16 validators per slot builds lists from its members’ views of the public mempool.
The lists give validators a way to constrain block builders. Builders assemble transaction payloads, but under the proposal they would have to account for the committee’s lists when preparing a block. The inclusion rule would apply through Ethereum’s fork-choice process, which determines which blocks attesters support.
Say your transaction has a valid nonce and enough balance to pay its fee, and it sits in the public mempool. A builder leaves it out. If committee members see it and list it, the next block must include it if it remains valid and there is enough room. Attesters reject a block that leaves out a valid listed transaction when it could fit.
How does FOCIL make builders include listed transactions?
EIP-7805 specifies FOCIL as a fork-choice rule: attesters only vote for a block that satisfies the inclusion lists they have stored. That rule gives list makers’ observations force in consensus, even when the builder would prefer to omit a transaction.
The committee creates and broadcasts its lists in one slot. The following slot’s proposer or builder uses the collected lists while constructing the execution payload. Attesters check whether listed transactions appear in the block, and whether any missing transaction could validly be added at the end. If a valid transaction fits and is absent, the block does not satisfy the lists.
In practice, FOCIL targets censorship by a block builder. A transaction that a builder ignores can still be surfaced by committee members and required for the block to receive attester votes. The mechanism depends on those members having the transaction in their public-mempool view and on the transaction meeting the inclusion conditions.
What can an inclusion list still leave uncertain?
FOCIL would enforce inclusion, not transaction position. A builder could place a listed transaction anywhere in the block, so the list would not promise that it executes first or ahead of competing transactions.
Available block space also matters. If the block is full, or a listed transaction cannot validly be appended given the state after the other transactions, the block can omit it and still satisfy the rule. Nonce and balance checks determine whether a transaction remains valid in that context.
Private routing creates a different limit. FOCIL list makers build from their own views of the public mempool. A transaction sent privately through Flashbots Protect is hidden from those list makers, so it receives no inclusion-list protection. Privacy and censorship resistance pull in opposite directions here: private submission can keep a transaction out of public view, while that same lack of visibility removes the route by which committee members could list it.
FOCIL is specified in EIP-7805, which the EIP page labels as a draft. It would require a protocol upgrade before applying on Ethereum mainnet. Until it is activated, a user should treat the inclusion guarantee as a proposed rule and check the current fork status before relying on it.
What should you check before relying on FOCIL?
When will FOCIL go live on Ethereum mainnet?
EIP-7805 is currently marked as a draft and gives no mainnet activation date. Check Ethereum’s current fork status for confirmation that the upgrade has been scheduled and activated before relying on the rule.
How are inclusion list committee members chosen?
EIP-7805 specifies a committee of 16 validators for each slot. The proposal describes the committee size and list duties; check the final specification and fork implementation for the selection details in force when it activates.
Do inclusion lists affect validator rewards?
EIP-7805 specifies no explicit reward for committee members who create inclusion lists. The proposal relies on at least one honest committee member for the mechanism to work as intended, so validators should consult the active protocol rules for any reward changes adopted with an upgrade.
Could builders still front-run a listed transaction?
FOCIL sets an inclusion requirement, not an ordering rule. A builder may place the transaction anywhere in the block, so inclusion alone does not determine which transactions execute before it. Check the block’s ordering if execution position matters to your transaction.