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: docs/README_Docker_and_RA.md
+7-28
Original file line number
Diff line number
Diff line change
@@ -368,30 +368,7 @@ pnpm install
368
368
pnpm compile
369
369
```
370
370
371
-
3. Ensure the values in the `script/layer1/provers/config_dcap_sgx_verifier.sh` script match whichever network you are registering for.
372
-
373
-
> **_NOTE:_** You will have to do this step twice for Hekla: once for the Ontake addresses and once for the Pacaya addresses. Please keep both SGX_INSTANCE_IDs.
These values are already in the script, it defaults to Hekla; please comment those lines out and uncomment the Mainnet ones if performing RA on Mainnet.
391
-
392
-
4. In the `script/layer1/provers/config_dcap_sgx_verifier.sh` script, replace `--fork-url https://any-holesky-rpc-url/` with the RPC URL of the hekla/mainnet network. Alternatively, export it like so: `export FORK_URL="https://any-holesky-rpc-url/"`.
393
-
394
-
5. If you've followed the Raiko Docker guide, you will have bootstrapped raiko and obtained a quote:
371
+
3. If you've followed the Raiko Docker guide, you will have bootstrapped raiko and obtained a quote:
@@ -401,11 +378,13 @@ These values are already in the script, it defaults to Hekla; please comment tho
401
378
402
379
You can find it with `cat ~/.config/raiko/config/bootstrap.json` as shown above.
403
380
404
-
Copy your quote and use in the following step.
381
+
4. Export an RPC url for the L1 network you are registering for. i.e. `FORK_URL=https://any_holesky_rpc_url/` for Hekla.
382
+
383
+
5. Call the script with `PRIVATE_KEY=0x{YOUR_PRIVATE_KEY} ./script/layer1/provers/config_dcap_sgx_verifier.sh --env {NETWORK} --quote {YOUR_QUOTE_HERE}`. "YOUR_QUOTE_HERE" comes from above step 5.
405
384
406
-
6. Call the script with `PRIVATE_KEY=0x{YOUR_PRIVATE_KEY} ./script/layer1/config_dcap_sgx_verifier.sh --quote {YOUR_QUOTE_HERE}`. "YOUR_QUOTE_HERE" comes from above step 5.
385
+
`NETWORK` will be `hekla-<ontake|pacaya|pivot>` or `mainnet` depending on which verifier you are registering to.
407
386
408
-
> **_NOTE:_** You can use the same command for registering both verifiers, just comment out the Ontake addresses and uncomment the Pacaya ones in the script and re-run.
387
+
> **_NOTE:_** You will have to do this step twice for Hekla: once for Ontake and once for Pacaya. Please keep both SGX_INSTANCE_IDs.
409
388
410
389
7. If you've been successful, you will get a SGX instance `id` which can be used to run Raiko!
411
390
@@ -424,7 +403,7 @@ Once you've completed the above steps, you can actually run a prover.
424
403
425
404
Raiko now supports more configurations, which need to be carefully checked to avoid errors.
426
405
427
-
> **_NOTE:_** We have deprecated `SGX_INSTANCE_ID`, if you only register with the Ontake addresses please export to `SGX_ONTAKE_INSTANCE_ID`.
406
+
> **_NOTE:_** We have deprecated `SGX_INSTANCE_ID`, if you only register for Pacaya please export to `SGX_PACAYA_INSTANCE_ID`.
428
407
429
408
- SGX_ONTAKE_INSTANCE_ID: SGX registered ID for ontake fork. (if raiko start before/in ontake, set this one)
430
409
- SGX_PACAYA_INSTANCE_ID: SGX registered ID for pacaya fork. (if raiko start before/in pacaya, set this one)
0 commit comments