Seeing some talks about Tx inclusion under censorship, here’s a quick list of how a Tx may get included on chain under all builder active censoring, today + in the future with ePBS & FOCIL: 1.) Rely on proposers not running MEV-boost, ~4.9% based on my query from the ultrasound relayer 2 weeks ago. The actual number is likely lower since I only checked 1 relayer 2.) Rely on proposers running MEV-Boost with the min-bid flag, the builder’s block must exceed this value, otherwise the proposer will use their local block 3.) Rely on the Tx tip amount, the builder’s bid has to beat the tip value, otherwise the proposer will use their local block with the Tx. This is the default behavior on clients today 4.) Rely on the EL client running censorship heuristics, EL client detects active censorship in the mempool and tells the proposer to default to the local block. Nethermind already has this implemented! though it’s not the default for EL clients today, and maybe default for some CL clients 5.) Rely on the MEV-Boost circuit breaker, if 3 slots are missed in a row or 5 in a single epoch, the proposer will default to building a local block. Not ideal to rely on, but worth mentioning 6.) With FOCIL, rely on at least one honest IL committee member and assume the chain isn’t under a 51% attack, the Tx as high probability of inclusion list unless the block is full 7.) Bonus: with ePBS, every node can detect when a block is built by a censoring builder through new payload engine api call, allowing faster censorship detection and quicker fallback to a local block(terence)