Ethereum core developer Tim Beiko said that at the 166th Ethereum core developer executive meeting, developers discussed the current status of Dencun's upgrade devnets: devnet-7 is still running, and work on tool support is also in progress, especially having a blob browser that includes all blobs since genesis. Also, a small Sepolia shadow fork was done and some client bugs were found. The client is moving to devnet-8 work, which will also include non-4844 functionality. Currently, Nethermind has everything implemented, but some EIPs are still under review; Erigon is implementing 4844, 1153, 5656, 4788 are also in the works, and SELFDESTRUCT removal (6780) is also backlog. Hyperledger Besu is ready except for 4788 and 6780, EthereumJS is also ready. CL developers say they are reviewing Lighthouse and Lodestar implementations, and Teku is almost ready. In terms of testing, 4844, 6780 and 5656 are all ready and the team is currently focusing on 4788 and 1153 coverage. The developers then discussed some potential specification changes for Dencun. One, a proposal to add a parent beacon block root to the execution payload, received significant support, and it will be up to the consensus meeting to decide whether to include this change in devnet-8. Second, the developers discussed how to clarify some edge cases related to EIP-6780, and there was a lot of discussion about the opcode not destroying ETH if the contract was not destroyed. The developers also discussed more API interface changes, agreeing to add a new endpoint and remove mining-related endpoints from the specification. The meeting also discussed setting a standard file location for jwt tokens used by EL and CL clients for mutual authentication, but there was not enough consensus. On the issue of splitting the EIP and ERC code bases, both the client team and the researchers were in favor, but Greg Colvin was against it, proposing to have Ethereum/EIPs as a separate repository for editorial purposes and a list of "valid" drafts, and then create a new repository for pre-draft EIPs/ERCs. Finally, the developers discussed the naming of the next upgrade of Ethereum, that is, EL will use Prague (Prague), and CL will use Electra.