From 72a4b7cedad65968a330d184270b8b24a3abd9b4 Mon Sep 17 00:00:00 2001
From: "Dr. Mia von Steinkirch"
 <1130416+F4DELEGATECALL@users.noreply.github.com>
Date: Wed, 19 Oct 2022 19:34:05 -0700
Subject: [PATCH] =?UTF-8?q?=F0=9F=8E=82=20the=20mempool=20(the=20dark=20fo?=
 =?UTF-8?q?rest)?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 MEV_on_Ethereum/MEMPOOL.md | 17 ++++++++---------
 1 file changed, 8 insertions(+), 9 deletions(-)

diff --git a/MEV_on_Ethereum/MEMPOOL.md b/MEV_on_Ethereum/MEMPOOL.md
index 7badeec..281ee2f 100644
--- a/MEV_on_Ethereum/MEMPOOL.md
+++ b/MEV_on_Ethereum/MEMPOOL.md
@@ -1,15 +1,14 @@
-## 🎂 the mempool
+## 🎂 the mempool (the dark forest)
+
+
+### tl;dr
 
 <br>
 
-### the dark forest tl;dr
-
-<br>
-
-* whenever you make a transaction in the Ethereum network (you sign the transaction), you have to wait until it to be confirmed in the blockchain. 
-* during that period, it sits in the memory pool. 
-* anyone can listen to these transactions, and their details, while they are there, and even modify them. 
-* if someone pays a higher gas price, their modification will be included a block first.
+* the mempool is the ethereum memory pool, where pending new txs wait to be confirmed, i.e., validated and included into new blocks.
+* ethereum has a public mempool and many private mempool spaces (such as the ones provided by flashbot’s protect or rook’s coordinator).
+* this means that nodes and associated entities are entitled to configure their own rules for their mempool by allowing private (exclusive) order flow to
+* txs to be included in blocks, while not visible in the public mempool.
 
 
 <br>