Skip to content

adding op-deployer callouts #1016

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 2 commits into from
Oct 22, 2024
Merged

adding op-deployer callouts #1016

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
dbbe614
adding op-deployer callouts
sbvegan Oct 22, 2024
df0ee41
fix broken links
sbvegan Oct 22, 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/configuration/rollup.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1005,7 +1005,7 @@ gas on L2.
Alt-DA Mode enables seamless integration of various Data Availability (DA)
Layers, regardless of their commitment type, into the OP Stack. This allows
any chain operator to launch an OP Stack chain using their favorite DA Layer
for sustainably low costs. Learn more [here](/stack/protocol/features/alt-da-mode).
for sustainably low costs. Learn more [here](/stack/beta-features/alt-da-mode).

***

Expand Down
5 changes: 5 additions & 0 deletions pages/builders/chain-operators/deploy/genesis.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,11 @@ import { Callout } from 'nextra/components'

# OP Stack genesis creation

<Callout type="warning">
This page is out of date and shows the legacy method for genesis file creation.
For the latest recommended method, use [op-deployer](/builders/chain-operators/tools/op-deployer).
</Callout>

The following guide shows you how to generate the L2 genesis file `genesis.json`. This is a JSON
file that represents the L2 genesis. You will provide this file to the
execution client (op-geth) to initialize your network. There is also the rollup configuration file, `rollup.json`, which will be
Expand Down
5 changes: 5 additions & 0 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 @@ -8,6 +8,11 @@ import { Callout } from 'nextra/components'

# OP Stack smart contract deployment

<Callout type="warning">
This page is out of date and shows the legacy method for smart contract deployment.
For the latest recommended method, use [op-deployer](/builders/chain-operators/tools/op-deployer).
</Callout>

The following guide shows you how to deploy the OP Stack L1 smart contracts.
The primary development branch is `develop`, however **you should only deploy
official contract releases**. You can visit the see the [smart contract overview](/stack/smart-contracts#official-releases)
Expand Down
Loading