Skip to content

Update upgrade-op-contracts-1-3-1-8.mdx #1692

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jul 16, 2025
Merged

Update upgrade-op-contracts-1-3-1-8.mdx #1692

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
4d757b7
Update upgrade-op-contracts-1-3-1-8.mdx
Wazabie Jul 16, 2025
dd536d6
Update upgrade-op-contracts-1-3-1-8.mdx
Wazabie Jul 16, 2025
2307d76
Apply suggestion from @Copilot
krofax Jul 16, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions pages/stack/smart-contracts/upgrade-op-contracts-1-3-1-8.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,6 +27,8 @@ This guide provides specific instructions for upgrading the OP Stack's Layer 1 c

The Holocene upgrade is a protocol upgrade. Learn more about it in the [Holocene notice page](https://docs.optimism.io/notices/holocene-changes). This guide shows you how to take your OP Stack chain from the L2 Output Oracle System to a permissioned Fault Proof System contract version associated with the Holocene upgrade.

After upgrading to OP Stack contracts v1.8.0 and enabling permissioned fault proofs, all pending (unfinalized) withdrawal proofs created on L1 are invalidated. This means that withdrawals must be manually reproven by users after the upgrade; the process is not automatic.

### Formatting config files

You need your chain's `deployments.json` and `deploy-config.json`
Expand Down Expand Up @@ -99,7 +101,7 @@ Ensure both files are correctly formatted, using the exact field names shown in
"proxyAdminOwner": "0xb0cCdbD6fe09D2199171BE19450aF249250518A0",
"l2OutputOracleChallenger": "0xcA4571b1ecBeC86Ea2E660d242c1c29FcB55Dc72",

- add the below values if not in the config file already, making sure they are correct for your chain
- add the below default values, if you expect different values for your chain reach out to OP Labs support for clarification before proceeding
"useFaultProofs": true,
"faultGameMaxDepth": 73,
"faultGameSplitDepth": 30,
Expand All @@ -110,7 +112,7 @@ Ensure both files are correctly formatted, using the exact field names shown in
- You can update this to the latest absolute prestate hash in the Superchain Registry; however, the permissioned Fault Proof System doesn't use this. This comes into play when you upgrade your chain to the permissionless Fault Proof System.
"faultGameAbsolutePrestate": "0x03925193e3e89f87835bbdf3a813f60b2aa818a36bbe71cd5d8fd7e79f52bafe",

- add the below values if not in the config file already, making sure they are correct for your chain
- add the below default values, if you expect different values for your chain, reach out to OP Labs support for clarification before proceeding
"faultGameGenesisBlock": 0,
"faultGameGenesisOutputRoot": "0xdead000000000000000000000000000000000000000000000000000000000000",
"respectedGameType": 1,
Expand Down