Update EIP-3155: Move to Review

EIPS/eip-3155.md

@@ -1,26 +1,26 @@
 ---
 eip: 3155
 title: EVM trace specification
 author: Martin Holst Swende (@holiman), Marius van der Wijden (@MariusVanDerWijden)
 discussions-to: https://ethereum-magicians.org/t/eip-3155-create-evm-trace-specification/5007
-status: Stagnant
+status: Review
 type: Standards Track
 category: Interface
 created: 2020-12-07
 ---
 
 
 ## Simple Summary
 Introduce a new JSON standard for EVM traces during execution of state tests. 
 
 ## Motivation
 The Ethereum Virtual Machine executes all smart contract code on ethereum. 
 In order to debug smart contracts and state tests better, a common format was introduced to log every execution step of the EVM. 
 This format was implemented by go-ethereum, parity, nethermind and Besu. 
 Since the common format was not well defined, the implementations differed slightly making it hard to develop adequate tooling which reduces the usefulness of tracing significantly.
 
 This EIP has multiple objectives:
 - Move the specification to a more visible place to encourage new clients to implement it
 - Strictly define corner cases that were not addressed in the previous version
 - Allow for updates to the specification in case new fields are introduced during execution
 - Provide sample output
@@ -31,7 +31,7 @@
 This EIP will enable users to create better differential fuzzing infrastructure to compare the EVM implementations of all major Ethereum clients against each other. 
 This could help to find bugs that are currently present in the client implementations. 
 
 ## Specification
 Clients should be able to execute simple transactions as well as code and return traces. In the following, we will call this client CUT (client under test) and use go-ethereums `evm` binary for code examples. 
 
 ### Datatypes
@@ -75,11 +75,11 @@
 | `returnStack`  | Array of Hex-Numbers  | Array of values, Stack of the called function  |
 
 *Example:* 
 ```
 {"pc":0,"op":96,"gas":"0x2540be400","gasCost":"0x3","memory":"0x","memSize":0,"stack":[],"depth":1,"error":null,"opName":"PUSH1"}
 ```
 
 The `stack`, `memory` and `memSize` are the values _before_ execution of the op. 
 All array attributes (`stack`, `returnStack`, `memory`) MUST be initialized to empty arrays ("stack":[],) NOT to null.
 If the CUT will not output values for `memory` or `storage` then the `memory` and `storage` fields are omitted.
 This can happen either because the CUT does not support tracing these fields or it has been configured not to trace it.
@@ -89,7 +89,7 @@
 
 The CUT MUST NOT output a line for the `STOP` operation if an error occurred:
 *Example:* 
 ```
 {"pc":2,"op":0,"gas":"0x2540be3fd","gasCost":"0x0","memory":"0x","memSize":0,"stack":["0x40"],"depth":1,"error":null,"opName":"STOP"}
 ```
 
@@ -113,16 +113,16 @@
 |---|---|---|
 | `time` |  Number | Time in nanoseconds needed to execute the transaction  |
 | `fork` | String  | Name of the fork rules used for execution  |
 ```
 {"stateRoot":"0xd4c577737f5d20207d338c360c42d3af78de54812720e3339f7b27293ef195b7","output":"","gasUsed":"0x3","successful":"true","time":141485}
 ```
 
 ## Rationale
 This EIP is largely based on the previous non-official documentation for EVM tracing. 
 It tries to cover as many corner cases as possible to enable true client compatibility.
 The datatypes and if a field is optional is chosen to be as compatible with current implementations as possible.
 
 ## Backwards Compatibility
 This EIP is fully backward compatible with ethereum as it only introduces a better tracing infrastructure that is optional for clients to implement.
 
 ### Clients
@@ -152,10 +152,10 @@
 
 
 ## Implementation
 Implementation in [go-ethereum](https://github.com/ethereum/go-ethereum/tree/master/cmd/evm)
 Implementation in [OpenEthereum](https://github.com/openethereum/openethereum/tree/main/bin/evmbin)
 Implementation in [Besu](https://github.com/hyperledger/besu/tree/master/ethereum/evmtool)
 Implementation in [Nethermind](https://github.com/NethermindEth/nethermind/tree/master/src/Nethermind/Nethermind.State.Test.Runner)
 
 
 ## Security Considerations