What I’m pointing out is that when the builders are registered at the CL, we can just reveal the builder whenever we want. It doesn’t need to be an epoch before. It can be right before the slot. And the randomness can use information from the CL proposer right up to the involved slot ( or one before ). So it’s simple to enable preconfs by just revealing the next builder after the last payload (or CL block) is revealed . All of this is already implemented and existing code in the CL. As a form of optimization we just fix the proposers a couple of epochs in advance. But there used to be some efforts to hide this right until the time of proposal. This is what WHISK does and it was merged into the CL spec repo until not long ago Whisk: A practical shuffle-based SSLE protocol for Ethereum . Those efforts were a little hindered by the proposer lookahead in Fulu in EIP-7919 but we can keep the CL proposer lookahead and still use those techniques to hide the builder until the last moment. All of these are already available in the CL. I’m not pointing to anything new, I’m just pointing that we have most of this available and implemented and it enables MEV burn as soon as Glamsterdam is we wanted to.