Skip to content

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

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
Sep 12, 2024
Merged

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

Show file tree
Hide file tree
Changes from all commits
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
10 changes: 7 additions & 3 deletions 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,9 +83,13 @@ 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).
We're working on writing more documentation to prepare OP Stack chain operators
to run a fault proof chain effectively.
deploy the [Fault Proof Fixes release](https://github.com/ethereum-optimism/optimism/releases/tag/op-contracts%2Fv1.6.0) with the permissioned game type
enabled.
Starting with permissioned fault proofs gives chain operators time to get comfortable
running the additional infrastructure requirements: [op-challenger](https://github.com/ethereum-optimism/optimism/tree/develop/op-challenger) and
[monitoring](https://github.com/ethereum-optimism/monitorism/tree/main). There are also
additional changes to the economics of operating a permissionless fault proof that chain
operators should have a firm understanding of.

## Next Steps

Expand Down
4 changes: 2 additions & 2 deletions pages/builders/chain-operators/features/custom-gas-token.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ An OP Stack chain that uses the custom gas token feature enables an end user to
<Steps>
### Deploying Your Contracts

* Checkout the [`v2.0.0-beta.2` of the contracts](https://github.com/ethereum-optimism/optimism/tree/op-contracts/v2.0.0-beta.2) and use the commit to deploy.
* Checkout the [`v2.0.0-beta.3` of the contracts](https://github.com/ethereum-optimism/optimism/tree/op-contracts/v2.0.0-beta.3) and use the commit to deploy.

<Callout type="error">
Be sure to check out this tag or you will not deploy a chain that uses custom gas token!
Expand Down Expand Up @@ -47,7 +47,7 @@ An OP Stack chain that uses the custom gas token feature enables an end user to
You will NOT be able to change the address of the custom gas token after it is set during deployment.
</Callout>

* The [`v2.0.0-beta.2` release](https://github.com/ethereum-optimism/optimism/tree/op-contracts/v2.0.0-beta.2)
* The [`v2.0.0-beta.3` release](https://github.com/ethereum-optimism/optimism/tree/op-contracts/v2.0.0-beta.3)
enables fee withdrawals to L1 and L2. For more details on these values, see the [Withdrawal Network](/builders/chain-operators/configuration/rollup.mdx#withdrawal-network)
section of the docs.

Expand Down
2 changes: 1 addition & 1 deletion pages/stack/smart-contracts.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@ Contract releases have a component name of `op-contracts` and therefore are tagg

<Callout type="info">
Note: While these are a governance approved contract release, the recommended
release for new production chains is `op-contracts/v1.3.0`.
release for new production chains is `op-contracts/v1.6.0`.
</Callout>

The Safe Extensions protocol upgrade is intended to increase the security and
Expand Down
Loading