From d0e5116fd1b7e2dfd355a28df18ec9d3119ca337 Mon Sep 17 00:00:00 2001
From: "dr. mia von steinkirch, phd"
 <1130416+mvonsteinkirch@users.noreply.github.com>
Date: Wed, 8 Feb 2023 10:51:42 -0800
Subject: [PATCH] Update oracle_abuse.md

---
 MEV_by_chains/MEV_on_Arbitrum/gmx/oracle_abuse.md | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/MEV_by_chains/MEV_on_Arbitrum/gmx/oracle_abuse.md b/MEV_by_chains/MEV_on_Arbitrum/gmx/oracle_abuse.md
index a3d53a8..8922ebb 100644
--- a/MEV_by_chains/MEV_on_Arbitrum/gmx/oracle_abuse.md
+++ b/MEV_by_chains/MEV_on_Arbitrum/gmx/oracle_abuse.md
@@ -1,11 +1,19 @@
 ## gmx oracle abuse
 
+
 <br>
 
 ### tl; dr
 
+
 <br>
 
+### tl; dr october'22 event
+
+<br>
+
+* gmx differs from amms by offering zero slippage on trades via an oracle price update system, while amms like uniswap rely on arb bots to balance prices in the pools
+* gmx team-run bots make calls to `SetPriceWithBit()` to update asset prices. mev operators can observe these prices updates in the mempool before land on chain.
 
 <br>
 
@@ -13,4 +21,6 @@
 
 ### resources
 
+<br>
+
 * [chainsight twitter](https://twitter.com/ChainsightLabs/status/1580208615654584321?s=20&t=-FG5kQ_7kAKhLnbuk05wSg)