Update eip-1052.md

Author: sky-coderay

EIPS/eip-1052.md

@@ -1,7 +1,8 @@
 ---
 eip: 1052
 title: EXTCODEHASH opcode
-author: Nick Johnson <arachnid@notdot.net>, Paweł Bylica <pawel@ethereum.org>
+description: Returns the keccak256 hash of a contract's code
+author: Nick Johnson (@arachnid), Paweł Bylica (@chfast)
 discussions-to: https://ethereum-magicians.org/t/extcodehash-opcode/262
 status: Final
 type: Standards Track
@@ -19,8 +20,8 @@ code.
 
 Many contracts need to perform checks on a contract's bytecode, but do not
 necessarily need the bytecode itself. For instance, a contract may want to check
-if another contract's bytecode is one of a set of permitted implementations, or
-it may perform analyses on code and whitelist any contract with matching
+if another contract's bytecode is one of a set of permitted implementations,
+or it may perform analyses on code and whitelist any contract with matching
 bytecode if the analysis passes.
 
 Contracts can presently do this using the `EXTCODECOPY` (`0x3c`) opcode, but this
@@ -53,7 +54,7 @@ The gas cost is the same as the gas cost for the `BALANCE` opcode because the
 execution of the `EXTCODEHASH` requires the same account lookup as in `BALANCE`.
 
 Only the last 20 bytes of the argument are significant (the first 12 bytes are
-ignored), similarly to the semantics of the `BALANCE` (`0x31`), `EXTCODESIZE`
+ignored), similarly to the semantics of `BALANCE` (`0x31`), `EXTCODESIZE`
 (`0x3b`), and `EXTCODECOPY` (`0x3c`).
 
 The `EXTCODEHASH` distinguishes accounts without code and non-existing accounts.
@@ -64,6 +65,13 @@ also allows smart contracts to check when an account exists.
 
 There are no backwards compatibility concerns.
 
+## Security Considerations
+
+This opcode does not introduce new security risks beyond those already
+associated with the usage of code-hashing. However, it allows for more efficient
+code checks, so developers should be aware that this may enable cheaper
+verification of contracts, potentially influencing design decisions.
+
 ## Test Cases
 
 1. The `EXTCODEHASH` of the account without code is
@@ -84,11 +92,6 @@ There are no backwards compatibility concerns.
 10. The `EXTCODEHASH` of an empty account that will be cleared by
     the state clearing rule.
 
-## Implementation
+## Reference Implementation
 
 TBD
-
-## Copyright
-
-Copyright and related rights waived via
-[CC0](../LICENSE.md).