Skip to content

Commit a2e4533

Browse files
committed
updated latest release for testnet tutorial
1 parent 9fc51d3 commit a2e4533

File tree

1 file changed

+23
-30
lines changed

1 file changed

+23
-30
lines changed

pages/builders/chain-operators/tutorials/create-l2-rollup.mdx

Lines changed: 23 additions & 30 deletions
Original file line numberDiff line numberDiff line change
@@ -88,6 +88,7 @@ You can either use a node provider like [Alchemy](https://www.alchemy.com/) (eas
8888

8989
You're going to be spinning up your OP Stack chain using pre-built binaries from the latest Optimism release instead of building directly from source.
9090
This simplifies the setup process and ensures you're using the latest stable version.
91+
Although this adds a few extra steps, it means you'll have an easier time modifying the behavior of the stack if you'd like to do so.
9192

9293
<Callout>
9394
You're using the home directory `~/` as the work directory for this tutorial for simplicity.
@@ -111,62 +112,54 @@ git clone https://github.com/ethereum-optimism/optimism.git
111112
```bash
112113
cd optimism
113114
```
115+
{<h3>Check out the correct branch</h3>}
114116

115-
</Steps>
116-
117-
## Download the latest Optimism release
118-
119-
The latest stable releases of `op-node`, `op-batcher`, and `op-proposer` can be found on the [Optimism releases page](https://github.com/ethereum-optimism/optimism/releases).
120-
121-
<Callout>
122-
Always use the latest releases when building your chain.
123-
Using outdated versions may lead to compatibility issues or missing critical features.
117+
<Callout type="info">
118+
You will be using the `tutorials/chain` branch of the Optimism Monorepo to deploy an OP Stack testnet chain during this tutorial.
119+
This is a non-production branch that lags behind the `develop` branch.
120+
You should **NEVER** use the `develop` or `tutorials/chain` branches in production.
124121
</Callout>
125122

126-
<Steps>
123+
```bash
124+
git checkout tutorials/chain
125+
```
127126

128-
{<h3>Navigate to Optimism releases</h3>}
127+
<Callout type="warning">
128+
The components in the `tutorials/chain` branch are outdated and may not work as expected.
129+
To ensure compatibility and stability, you will download the latest releases of `op-node`, `op-batcher`, and `op-proposer` from the Optimism releases page.
130+
These latest versions will override any outdated components in the `tutorials/chain` branch.
131+
</Callout>
129132

130-
Open the Official [Optimism releases page](https://github.com/ethereum-optimism/optimism/releases) in your browser.
133+
{<h3> Download the latest Optimism releases </h3>}
134+
Open the Official [Optimism releases page](https://github.com/ethereum-optimism/optimism/releases) in your browser to download the latest stable releases of `op-node`, `op-batcher`, and `op-proposer`.
131135

132-
{<h3>Identify latest release</h3>}
136+
{<h3>Identify latest release</h3>}
133137

134138
* Look for the most recent version tagged as `vX.Y.Z`.
135-
136139
* Verify release date matches current expectations.
137-
138140
* Check release notes for critical compatibility information.
139141

140142
{<h3> Download required binaries</h3>}
141143

142144
In the *Assets* section of the release, download these files for your operating system:
143-
144145
* `op-node_<version>_<OS>_<arch>.tar.gz`
145146
* `op-batcher_<version>_<OS>_<arch>.tar.gz`
146147
* `op-proposer_<version>_<OS>_<arch>.tar.gz`
147148

148-
<Callout>
149-
**Identify your system**:
150-
* **Windows**: Use `windows` packages.
151-
* **macOS**: `darwin` packages (Intel: `amd64`, Apple Silicon: `arm64`).
152-
* **Linux**: `linux` packages (`amd64` or `arm64`).
153-
</Callout>
154-
155149
{<h3> Verify file integrity</h3>}
156150

157151
1. Open the checksums.txt file in the release assets
158-
2. Compare listed SHA256 values with your downloaded files using:
159-
* Windows: PowerShell Get-FileHash command
160-
* macOS: Terminal shasum command
161-
* Linux: Terminal sha256sum command
152+
2. Compare listed `SHA256` values with your downloaded files using:
153+
* Windows: PowerShell `Get-FileHash` command
154+
* macOS: Terminal `shasum` command
155+
* Linux: Terminal `sha256sum` command
162156

163157
{<h3> Extract binaries</h3>}
164158

165159
Using your system's archive tool:
166-
1. Extract all .tar.gz files
167-
2. Preserve directory structure during extraction
160+
1. Extract all `.tar.gz` files
161+
2. Override any outdated components in the `tutorials/chain` branch during extraction by moving these extracted files to a directory in your system `PATH`:
168162

169-
Move these extracted files to a directory in your system PATH:
170163
* `op-node`
171164
* `op-batcher`
172165
* `op-proposer`

0 commit comments

Comments
 (0)