Update ethereum.md

blockchains/ethereum.md

@@ -1,36 +1,28 @@
-## the ethereum blockchain
+## the ethereum blockchain tl; dr
 
 <br>
 
-#### evm execution tl; dr
+* **[the ethereum yellow paper](https://ethereum.github.io/yellowpaper/paper.pdf)**
+* the ethereum roadmap:
+
+<br>
+<p align="center">
+<img width="400"  src="https://user-images.githubusercontent.com/1130416/234419153-76ab9f89-00e8-48e7-93c4-c8d880ec2007.png">
+</p>
+<br>
+
+----
+### mnemonics
+
+##### evm execution tl; dr
 
 * in native execution, evm will load the bytecode and execute the opcodes in the bytecodes one by one from the beginning.
 * each opcode can be thought as doing the following steps:
   1. read elements from stack, memory, or storage.
   2. perform some computation on these elements.
   3. write back results to stack, memory, or storage.
 
-<br>
-
-
-#### light clients tl; dr
+##### light clients tl; dr
 
 * light clients receive the block headers, which contain a merkle root (more on this later) that can be used to query full nodes to verify if a transaction is included in a particular block.
 
-<br>
-
-#### ethereum roadmap
-
-<br>
-<img width="600"  src="https://user-images.githubusercontent.com/1130416/234419153-76ab9f89-00e8-48e7-93c4-c8d880ec2007.png">
-<br>
-
-----
-
-### external resources
-
-<br>
-
-* **[geth code for stateDB](https://github.com/ethereum/go-ethereum/blob/d4d288e3f1cebb183fce9137829a76ddf7c6d12a/core/state/statedb.go#L64)**
-* **[understanding trie databases, by d. brickwood](https://medium.com/shyft-network/understanding-trie-databases-in-ethereum-9f03d2c3325d)**
-* **[possible futures of the ethereum protocol, part 1: the merge, by vb](https://vitalik.eth.limo/general/2024/10/14/futures1.html)**