Skip to content
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

contracts: update standard version to v1.6.0, CGT to v2.0.0-beta.3 #895

Merged
merged 3 commits into from
Sep 12, 2024
+10 −6
Merged

contracts: update standard version to v1.6.0, CGT to v2.0.0-beta.3 #895

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
3770dd4
contracts: update recommended deploy version to v1.6.0
bitwiseguy Sep 12, 2024
ca3cbe5
contracts: fixes around recommended v1.6.0
bitwiseguy Sep 12, 2024
ff196f8
contracts: update CustomGasToken to v2.0.0-beta.3
bitwiseguy Sep 12, 2024
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
2 changes: 1 addition & 1 deletion pages/builders/chain-operators/deploy/smart-contracts.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -83,7 +83,7 @@ single contract.
Production users should deploy their L1 contracts from a contracts release.
All contracts releases are on git tags with the following format:
`op-contracts/vX.Y.Z`. If you're deploying a new standard chain, you should
deploy the [Multi-Chain Prep (MCP) L1 release](https://github.com/ethereum-optimism/optimism/releases/tag/op-contracts%2Fv1.3.0).
deploy the [Fault Proof Fixes release](https://github.com/ethereum-optimism/optimism/releases/tag/op-contracts%2Fv1.6.0).
bitwiseguy marked this conversation as resolved.
Show resolved Hide resolved
We're working on writing more documentation to prepare OP Stack chain operators
bitwiseguy marked this conversation as resolved.
Show resolved Hide resolved
to run a fault proof chain effectively.
bitwiseguy marked this conversation as resolved.
Show resolved Hide resolved

Expand Down
Loading