I’ve posted a pre-ERC on the code an EOA adopts via SETCODEFROM: an adoption profile, a migration guard, and a reference kernel. Pre-ERC: Adoption Profile and Reference Kernel for EOAs Adopting Code via SETCODEFROM
Several of its failure modes read as general guidance for this EIP, so the thread includes draft text for its Security Considerations (first reply); I’m happy to open a PR. One small related fix: the Security Considerations still says an EIP-8151 rejection returns 32 zero bytes, but since ethereum/EIPs#12540 it returns empty output. One question affects the design: does the public-mempool scan apply to the sender’s own code when it runs as the frame target? (Q2 in the post.)