From aa0008dd45cc25a4c37e41999908c123ffc63573 Mon Sep 17 00:00:00 2001
From: Rachel-Eichenberger
 <60412342+Rachel-Eichenberger@users.noreply.github.com>
Date: Fri, 22 Mar 2024 10:46:13 -0700
Subject: [PATCH] fix: Remove old OP oracle info

Removing outdated oracle information for the Optimism network
---
 docs/concepts/protocol/oracle.md | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/docs/concepts/protocol/oracle.md b/docs/concepts/protocol/oracle.md
index 47a97f889e..64b266c758 100644
--- a/docs/concepts/protocol/oracle.md
+++ b/docs/concepts/protocol/oracle.md
@@ -86,8 +86,4 @@ With a tick reading of `100_000`, we can find the value of `token1` (USDC) in te
 
 Ticks are signed integers and can be expressed as a negative number, so for any circumstances where `token0` is of a lower value than `token1`, a negative tick value will be returned by `tickCumulative` and a relative value of `< 0` will be returned by a calculation of `token0` in terms of `token1`.
 
-## Oracles Integrations on Layer 2 Rollups
 
-### Optimism
-
-On Optimism, every transaction is confirmed as an individual block. The `block.timestamp` of these blocks, however, reflect the `block.timestamp` of the last L1 block ingested by the Sequencer. For this reason, Uniswap pools on Optimism are not suitable for providing oracle prices, as this high-latency `block.timestamp` update process makes the oracle much less costly to manipulate. In the future, it's possible that the Optimism `block.timestamp` will have much higher granularity (with a small trust assumption in the Sequencer), or that forced inclusion transactions will improve oracle security. For more information on these potential upcoming changes, please see the [Optimistic Specs repo](https://github.com/ethereum-optimism/optimistic-specs/discussions/23). For the time being, usage of the oracle feature on Optimism should be avoided.