Add more info

Author: bradleycamacho

pages/notices/upgrade-16.mdx

@@ -25,7 +25,7 @@ This page outlines important changes related to Upgrade 16 for chain operators a
 
 Upgrade 16 contains these main changes:
 
-*   **Interop-Ready smart contracts**: Interoperability is critical to realizing the Superchain as a unified network of OP Chains. This upgrade begins the rollout of foundational interoperability features by updating the `OptimismPortal` to handle future cross-chain messaging safely and extensibly.
+*   **Interop-Ready smart contracts**: Interoperability is critical to realizing the Superchain as a unified network of OP Chains. This upgrade begins the rollout of foundational interoperability features by updating the `OptimismPortal` to handle future cross-chain messaging safely and extensibly. This upgrade does not turn on interop yet.
 *   **Stage 1 updates**: Modifications to meet L2Beat's updated Stage 1 requirements from January 2025, including removal of `DeputyGuardianModule` and updates to `DeputyPauseModule`.
 *   **Go 1.23 Support in Cannon**: Updates to Cannon to support Go 1.23, allowing OP Stack to benefit from upstream go-ethereum changes.
 *   **Max gas limit increase**: Update to `MAX_GAS_LIMIT` from 200m to 500m gas after improvements to OP Stack infrastructure and the Cannon proof system.
@@ -41,6 +41,53 @@ Chain operators should be aware that Upgrade 16 involves a one-time invalidation
 
 If this proposal is accepted, multisig ceremonies will be coordinated to execute upgrade transactions. The following transactions will be executed on the respective chains: `OP Mainnet`, `Soneium Mainnet`, `Ink Mainnet`, `Base Mainnet`, `Unichain Mainnet`, `Mode Mainnet`, `Zora Mainnet`, `Arena Z Mainnet`, `Swell Mainnet`, and `Metal Mainnet`. Depending on the current state of the chain the execution times will vary. If your Optimism governed chain is not in this list, please reach out to OP Labs Solutions Engineering to coordinate your upgrade.
 
+<Steps>
+  ### Verify the new absolute prestate
+
+  <Callout type="info">
+    As of upgrade 14, the 64 bit multi-threaded version of cannon is utilized.
+  </Callout>
+
+  The absolute prestate is generated with the [op-program/v1.6.0-rc.2](https://github.com/ethereum-optimism/optimism/tree/op-program/v1.6.0-rc.2). You can use this new absolute prestate (`NEED PRESTATE`) for the following chains:
+
+  *   Sepolia: Base, Creator Chain, OP, Metal, Mode, Zora, Ethernity, Unichain, Ink, and Minato (Soneium)
+
+  You can verify this absolute prestate by running the following [command](https://github.com/ethereum-optimism/optimism/blob/d6fb90dd489e39efa206b55200766ccc075c1d9b/Makefile#L130-L132) in the root of the monorepo on the `op-program/v1.6.0-rc.2` tag:
+
+  ```shell
+  make reproducible-prestate
+  ```
+
+  You should expect the following output at the end of the command:
+
+  ```shell
+  Cannon Absolute prestate hash: 
+  NEED PRESTATE
+  Cannon64 Absolute prestate hash: 
+  0x03682932cec7ce0a3874b19675a6bbc923054a7b321efc7d3835187b172494b6
+  CannonInterop Absolute prestate hash: 
+  0x0399cfb018011977a027d1e7a85eb7ff101aec9bfc7d6500abac944c47a4581f
+  ```
+
+  ### Upload your new preimage file
+
+  During the previous step, you also generated the preimage of the absolute prestate, which is basically the op-program serialized into a binary file. You'll find that new file at `optimism/op-program/bin/prestate-mt64.bin.gz`. Rename that file to have the absolute prestate hash as the filename so it looks like `0x03682932cec7ce0a3874b19675a6bbc923054a7b321efc7d3835187b172494b6.bin.gz`.
+
+  Upload that file to where you're storing your other absolute preimage files. This should be the location where you're pointing your `--cannon-prestates-url` at. The `op-challenger` will grab this file and use it when it needs to challenge games.
+
+  ### Deploy new dispute game contracts
+
+  You will then take the absolute prestate and deploy new `FaultDisputeGame` and `PermissionedDisputeGame` contracts with that value. 
+
+  ### Update the DisputeGameFactory
+
+  You will then need to update the `DisputeGameFactory` to point to the new `FaultDisputeGame` and `PermissionedDisputeGame` contracts by calling `DisputeGameFactory.setImplementation`. 
+
+  ### Execute the upgrade
+
+  Once your `op-challenger` is ready with the new preimage, you can execute the "Set Dispute Game Implementation" transaction. Please simulate and validate that the expected output prior to executing the transaction.
+</Steps>
+
 ## For node operators
 
 WHAT ARE THE NODE OPERATOR STEPS?