adding fix steps

Author: sbvegan

pages/notices/blob-fee-bug.mdx

@@ -91,3 +91,40 @@ The following chains are in the Superchain Registry and are not opted into the h
 
   If your Pectra Blob Schedule fix activation time is not in the Superchain Registry, decide on a hardfork activation time, and open a PR update the Superchain Registry with the activation time. See this [PR](https://github.com/ethereum-optimism/superchain-registry/pull/941) as an example.
 </Steps>
+
+## Fixing diverged nodes 
+
+If you upgraded your node binary to `op-node/v1.12.1` or `op-node/v1.12.0` and did not set the Pectra Blob Schedule Fix activation time your node will have forked from the rest of the network.
+
+To fix this, you can either restore your node from a snapshot and configure the Pectra Blob Schedule Fix activation time. Or you can use [`op-wheel`](https://github.com/ethereum-optimism/optimism/tree/develop/op-wheel) to roll back your node to a block before you diverged from the network.
+
+<Steps>
+  ### Stop the node 
+
+  *   Stop op-node: This component is stateless, so you can simply terminate the process.
+  Stop op-geth: It's crucial to use `Ctrl+C` to stop op-geth gracefully to avoid database corruption. An unclean shutdown can lead to various problems when restarting.
+
+  ### Query `op-geth` for a block to reorg to
+
+  ```
+  cast block --rpc-url=http://localhost:8545 6185373
+  #hash: 0x8b39f479198a5e658bbb28b1ce80790ca863ac39206c36152ba5c38db68989b2
+  #timestamp: 1735565082
+  # 6185373 in hex is 0x5E619D
+  ```
+
+  ### Reorg the chain 
+
+  ```
+  cast rpc --rpc-url=http://localhost:8545 debug_setHead 0x5E619D
+  ```
+  ### Explicitly set the forkchoice to the new head 
+
+  For example: 
+
+  ```
+  go run ./op-wheel/cmd engine set-forkchoice --engine=http://localhost:8551 --engine.jwt-secret=.jwt_secret.txt --finalized=6185373 --safe=6185373 --unsafe=6185373
+  ```
+
+</Steps>
+