Skip to content

Commit 2c77491

Browse files
committed
updated bas command
1 parent acebb69 commit 2c77491

File tree

3 files changed

+13
-6
lines changed

3 files changed

+13
-6
lines changed

pages/builders/chain-operators/deploy/smart-contracts.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -108,7 +108,7 @@ Follow the instructions provided in the [configure your chain](/builders/chain-o
108108
The next step is to deploy the L1 smart contracts, by running the following command:
109109

110110
```bash
111-
./bin/op-deployer apply --workdir .deployer --l1-rpc-url <rpc-url> --private-key <private key>
111+
./bin/op-deployer apply --workdir .deployer --l1-rpc-url <rpc-url> --private-key <private key hex>
112112
```
113113
* Replace `<rpc-url>` with your L1 RPC URL.
114114
* Replace `<private key>` with the private key of the account used for deployment.

pages/builders/chain-operators/tools/op-deployer.mdx

Lines changed: 11 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,14 @@ import {Callout, Steps} from 'nextra/components'
1515

1616
The recommended way to install `op-deployer` is to download the latest release from the monorepo's
1717
[release page](https://github.com/ethereum-optimism/optimism/releases). To install a release, download the binary
18-
for your platform then extract it somewhere on your `PATH`. The rest of this tutorial will assume that you have
18+
for your platform then extract it somewhere on your `PATH`.
19+
20+
Run the following commad:
21+
```bash
22+
cd op-deployer && just build
23+
```
24+
25+
The rest of this tutorial will assume that you have
1926
installed `op-deployer` using this method.
2027

2128
## Deployment usage
@@ -100,7 +107,7 @@ Now that you've created your intent file, you can apply it to your chain to depl
100107
```
101108
./bin/op-deployer apply --workdir .deployer --l1-rpc-url <rpc-url> --private-key <private key hex>
102109
```
103-
* Replace `<rpc-url>` with your `L1 RPC URL` and `<private key>` with your private key
110+
* Replace `<rpc-url>` with your `L1_RPC_URL` and `<private key>` with your private key
104111

105112
This command will deploy the OP Stack to L1. It will deploy all L2s specified in the intent file. Superchain
106113
configuration will be set to the Superchain-wide defaults - i.e., your chain will be opted into the [Superchain pause](https://specs.optimism.io/protocol/superchain-config.html#pausability)
@@ -116,8 +123,8 @@ address as other chains on the Superchain.
116123
Inspect the `state.json` file by navigating to your working directory. With the contracts deployed, generate the genesis and rollup configuration files by running the following commands:
117124

118125
```
119-
op-deployer inspect genesis --workdir .deployer <l2-chain-id> > .deployer/genesis.json
120-
op-deployer inspect rollup --workdir .deployer <l2-chain-id> > .deployer/rollup.json
126+
./bin/op-deployer inspect genesis --workdir .deployer <l2-chain-id> > .deployer/genesis.json
127+
./bin/op-deployer inspect rollup --workdir .deployer <l2-chain-id> > .deployer/rollup.json
121128
```
122129

123130
Now that you have your `genesis.json` and `rollup.json` you can spin up a node on your network. You can also use the following inspect subcommands to get additional data:

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -446,7 +446,7 @@ Follow the instructions provided in the [configure your chain](/builders/chain-o
446446
The next step is to deploy the L1 smart contracts, by running the following command:
447447

448448
```bash
449-
./bin/op-deployer apply --workdir .deployer --l1-rpc-url <rpc-url> --private-key <private key>
449+
./bin/op-deployer apply --workdir .deployer --l1-rpc-url <rpc-url> --private-key <private key hex>
450450
```
451451
* Replace `<rpc-url>` with your L1 RPC URL.
452452
* Replace `<private key>` with the private key of the account used for deployment.

0 commit comments

Comments
 (0)