Update EIP-7523: Move to Review

EIPS/eip-7523.md

@@ -4,7 +4,7 @@ title: Empty accounts deprecation
 description: Prohibit empty accounts on post-merge networks
 author: Peter Davies (@petertdavies)
 discussions-to: https://ethereum-magicians.org/t/eip-7523-empty-accounts-deprecation/15870
-status: Draft
+status: Review
 type: Standards Track
 category: Core
 created: 2023-09-19
@@ -32,9 +32,13 @@ An empty account is an account with has **no code** and **zero nonce** and **zer
 On networks that undergo the merge transition, the pre state of the merge block may not contain any empty accounts. For networks that are merged at genesis, none of the genesis accounts may be empty accounts.
 
 Rather than performing a scan of the state, clients MAY assume the following chains have no post-merge empty accounts:
+
 1. The Mainnet chain whose merge block has hash `0x56a9bb0302da44b8c0b3df540781424684c3af04d0b7a38d72842b762076a664`.
+
 2. Any chain which:
+
   - has no empty accounts in the genesis.
+
   - had a post Spurious Dragon fork at genesis.
 
 The Ethereum specification is declared to be undefined in the presence of an empty account in a post-merge context. Any testcase involving post-merge empty accounts is invalid.
@@ -44,8 +48,10 @@ The Ethereum specification is declared to be undefined in the presence of an emp
 This EIP was drafted to be the simpliest possible way of eliminating the long term technical debt imposed by empty accounts. The Merge was chosen as a natural easily identifiable cutoff point.
 
 Alternative approaches include:
-* Using an earlier cutoff point, such as block `14049881`.
-* Identifying a wider range of edge case behaviour that never happened.
+
+- Using an earlier cutoff point, such as block `14049881`.
+
+- Identifying a wider range of edge case behaviour that never happened.
 
 These approaches were rejected as being unnecessarily complicated.