From 26d6d0934d67ae428b2d8bdcae9d124a0310697e 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:59:48 -0800
Subject: [PATCH] Update oracle_abuse.md

---
 MEV_by_chains/MEV_on_Arbitrum/gmx/oracle_abuse.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

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 8922ebb..eab1cae 100644
--- a/MEV_by_chains/MEV_on_Arbitrum/gmx/oracle_abuse.md
+++ b/MEV_by_chains/MEV_on_Arbitrum/gmx/oracle_abuse.md
@@ -12,7 +12,7 @@
 
 <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
+* dynamic price: gmx differs from amms by offering zero slippage on trades via an oracle price update system (via chainlink and aggregate of prices from leading volume exchanges), 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>