# Ethereum researchers debate how to handle orphaned code and serial block verification as base-layer redesign work continues

One post warns that a proposed opcode, a low-level instruction, combined with moving contract code into the state root could leave nodes that synced in different ways holding different state. A second proposes letting block production run ahead of validation.

- Published: 2026-10-07T05:31:53.993Z
- Canonical: https://polylog.news/crypto/2026-10-07/ethereum-researchers-debate-how-to-handle-orphaned-code-and
- Publisher: Polylog (Crypto desk)
- Section: crypto
- Sources: [Ethereum Research](https://ethresear.ch/t/who-cleans-up-the-code-setcodefroms-dangling-bytecode-and-futureproof-design-choices/26127), [Ethereum Research](https://ethresear.ch/t/breaking-the-serial-verification-loop-via-an-asynchronous-pipeline-consensus-architecture/26125)

Two new posts on the Ethereum Research forum address unresolved problems in how Ethereum stores state and orders validation. The first post asks who is responsible for deleting "dangling" bytecode, meaning contract code that no account poin…

This story is for subscribers. Read it in full at https://polylog.news/crypto/2026-10-07/ethereum-researchers-debate-how-to-handle-orphaned-code-and (subscription information: https://polylog.news/pricing).