You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: examples/l2/README.md
+10-6Lines changed: 10 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -121,7 +121,9 @@ Finally [run the l2](#run-the-l2).
121
121
122
122
## Setup Localnet
123
123
124
-
You can also run this example on a local devnet. To get started, navigate to the root of the Aligned repository and run:
124
+
You can also run this example on a local devnet. To get started, navigate to the root of the Aligned repository
125
+
126
+
- Start Ethereum package and the Batcher
125
127
126
128
```shell
127
129
# This will start the local net
@@ -130,33 +132,35 @@ make ethereum_package_start
130
132
make batcher_start_ethereum_package
131
133
```
132
134
133
-
The remaining steps are the same as for other networks, except you'll be using the `devnet` environment. Specifically, generate the `.env` files for `devnet` using:
135
+
- Generate the env files for contracts
134
136
135
137
```shell
136
138
make gen_env_contract_devnet
137
139
make gen_env_l2_devnet
138
140
```
139
141
140
-
By default and to make things simpler, the `.env` will be generated using a dev rich wallet. You can of course, creaste your own wallet by following the steps on `1.`. Since the L2 requires a keystore, you'll need to generate it via:
142
+
- Generate a pre funded wallet (or create one as specified in the previous readme)
141
143
142
144
```shell
143
145
# This will generate the keystore and fund it on aligned
144
146
make gen_devnet_owner_wallet
145
147
```
146
148
147
-
Finally, generate the program id with:
149
+
- Generate the program ID of the program that is going to be proven:
148
150
149
151
```shell
150
152
make generate_program_id
151
153
```
152
154
153
-
Copy the address to the generated `.env` and deploy the contract:
155
+
- Set the ID on ```contracts/.env```. This will be used to accept only proofs of the desired L2 program
156
+
157
+
- Deploy the contract
154
158
155
159
```shell
156
160
make deploy_contract
157
161
```
158
162
159
-
Pass the output address in the `.env` and [run the l2](#run-the-l2).
163
+
-Pass the output address in the `.env` and [run the l2](#run-the-l2).
0 commit comments