Update evm-differences.md

removed the commented out part

Author: EmpieichO

docs/zkEVM/spec/evm-differences.md

@@ -30,47 +30,3 @@ The following differences have no impact on the developer's experience on the zk
    - Interacting with libraries, like Web3.js and Ethers.js.
    - Deploying contracts seamlessly on the zkEVM without any overhead.
 
-
-<!-- 
-### Opcodes
-
-Below is a list of the changes we have made to opcodes in zkEVM in comparison to the EVM.
-   
-   - **SELFDESTRUCT** &rarr; removed and replaced by **SENDALL**.
-
-   - `EXTCODEHASH` returns the hash of the contract bytecode from the zkEVM state tree without checking if the account is empty.
-
-   - **DIFFICULTY** &rarr;  returns "0" instead of a random number as in the EVM.
-
-   - **BLOCKHASH** &rarr; returns all previous block hashes instead of just the last 256 blocks.
-
-   > **BLOCKHASH** is the state root at the end of a processable transaction and is stored on the system smart contract.
-
-   - **NUMBER** &rarr; returns the number of processable transactions.
-
-
-### Precompiled contracts
-
-Among Ethereum's precompiled contracts, the zkEVM currrently supports: [`ecRecover`](https://www.evm.codes/precompiled?fork=shanghai) and [`identity`](https://www.evm.codes/precompiled?fork=shanghai).
-
-Other precompiled contracts have no effect on the zkEVM state tree and are treated as reverts, returning all gas to the previous context and setting the `success` flag to "0".
-
-
-## Additions
-
-**zk-counters** &rarr; batch resources are available, linked to state-machine components, as a supplementary addition to gas computation.
-
-
-## Other minor differences
-   
-   - zkEVM doesn't clean storage when a contract is deployed at an address due to the zkEVM state tree specification.
-
-   - `JUMPDEST` is allowed in push bytes to avoid runtime bytecode analysis.
-
-   - The zkEVM implements [EIP-3541](https://eips.ethereum.org/EIPS/eip-3541) from the [London hardfork](https://ethereum.org/en/history/#london).
-
-   - [EIP-2718](https://eips.ethereum.org/EIPS/eip-2718) which defines the Typed Transaction Envelope, is not supported
-
-   - [EIP-2930](https://eips.ethereum.org/EIPS/eip-2930), which defines the Optional Access Lists transaction type, is not supported.
-
-   - [`BASEFEE`](https://ethereum-org-fork.netlify.app/en/developers/docs/gas#base-fee) opcode is not supported. The zkEVM implements the Berlin hardfork, but not the London hardfork. -->