Skip to content

Suggested edits for tutorials/create-l2-rollup.mdx #1218

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
Jan 6, 2025
Merged

Suggested edits for tutorials/create-l2-rollup.mdx #1218

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d2d1fd6
Switch order of 'Batcher' and 'Proposer' under reccomended ETH balanc…
Red-Pandaz Jan 5, 2025
4ce3c60
Add 'forge install' after navigating to optimism/packages/contracts-b…
Red-Pandaz Jan 5, 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
8 changes: 7 additions & 1 deletion pages/builders/chain-operators/tutorials/create-l2-rollup.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -272,8 +272,8 @@ The exact amount of ETH required depends on the L1 network being used.
It's recommended to fund the addresses with the following amounts when using Sepolia:

* `Admin` — 0.5 Sepolia ETH
* `Proposer` — 0.2 Sepolia ETH
* `Batcher` — 0.1 Sepolia ETH
* `Proposer` — 0.2 Sepolia ETH

**To get the required Sepolia ETH to fund the addresses, we recommend using the [Superchain Faucet](https://console.optimism.io/faucet?utm_source=docs)** together with [Coinbase verification](https://help.coinbase.com/en/coinbase/getting-started/getting-started-with-coinbase/id-doc-verification).

Expand Down Expand Up @@ -342,6 +342,12 @@ cd ~/optimism
cd packages/contracts-bedrock
```

{<h3>Install Foundry dependencies</h3>}

```bash
forge install
```

{<h3>Generate the configuration file</h3>}

Run the following script to generate the `getting-started.json` configuration file inside of the `deploy-config` directory.
Expand Down