Skip to content

create-l2-rollup: fix script path #1340

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
Feb 18, 2025
Merged

create-l2-rollup: fix script path #1340

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
b450c7b
create-l2-rollup: fix script path
asymmetric Feb 10, 2025
4188924
Merge branch 'main' into patch-4
krofax Feb 18, 2025
2ab440c
fix conflict
krofax Feb 18, 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: 6 additions & 0 deletions pages/operators/chain-operators/tutorials/create-l2-rollup.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -422,8 +422,14 @@ Once you've configured your network, it's time to deploy the L1 contracts necess
The `op-deployer` tool simplifies the creation of genesis and rollup configuration files (`genesis.json` and `rollup.json`).
These files are crucial for initializing the execution client (`op-geth`) and consensus client (`op-node`) for your network.

```bash

forge script scripts/deploy/Deploy.s.sol:Deploy --private-key $GS_ADMIN_PRIVATE_KEY --broadcast --rpc-url $L1_RPC_URL --slow

```
The recommended flow for creating a genesis file and rollup configuration file on the OP Stack is as follows:


1. **Deploy the L1 contracts** using [op-deployer](/operators/chain-operators/tools/op-deployer).
2. **Generate** both the L2 genesis file (`genesis.json`) and the rollup configuration file (`rollup.json`) using op-deployer's `inspect` commands.
3. **Initialize** your off-chain components (e.g., execution client, consensus client).
Expand Down