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 1cc8482..770127e 100644
--- a/MEV_by_chains/MEV_on_Arbitrum/gmx/oracle_abuse.md
+++ b/MEV_by_chains/MEV_on_Arbitrum/gmx/oracle_abuse.md
@@ -8,16 +8,8 @@
 <br>
 
 
-* october'22 oracle abuse: 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.
-* a new oracle oracle has been deployed (XGET), which allows for information to be verified on-chain while providing frontrunning resistance (by having nodes sign a combination of blockhashes and values).
-
-
-<br>
-
-### tl; dr 
-
-<br>
-
+* october'22 oracle abuse: [the thesis](https://twitter.com/joshua_j_lim/status/1571554171395923968) was that while the gmx team runs bots to update prices by making calls to SetPriceWithBit(), mev operators can observe these price updates in the mempool before they are on-chain.
+* also in october'22, a [new oracle was deployed (XGET)](https://twitter.com/Kalcrypto1/status/1576977723016085505), allowing for information to be verified on-chain while providing frontrunning resistance (by having nodes sign a combination of blockhashes and values).
 
 
 <br>
@@ -30,3 +22,4 @@
 
 * [chainsight twitter](https://twitter.com/ChainsightLabs/status/1580208615654584321?s=20&t=-FG5kQ_7kAKhLnbuk05wSg)
 * [another twitter](https://twitter.com/wilburforce_/status/1571891338097860608)
+* [a gmx oracle manipulator bot](https://mirror.xyz/steinkirch.eth/e-gsChe2GxfadHeBnMDsWe_4eQar9JJHJKlWqIE-jKY)