chore(main): prerelease v1.8.0 (#563)

* chore: update subproject commit reference for gaiko

* fix: allow non-zero exist code

* fix: downgrade itertools version to 0.11.0 for compatibility

* fix: update dependencies for reth packages to latest commit

* fix: update proc-macro-crate version and adjust taiko-reth dependencies

* fix: refactor gramine command handling and improve input serialization for proof

* fix: update subproject commit reference for gaiko

* update mainnet pacaya fork height & its reth dependency

* fix: update subproject commit reference for gaiko

* fix: update dependencies for sgx-prover and improve configuration handling (#564)

* update pacaya verifier address

* fix: update subproject commit reference for gaiko

* chore: update release notes for v1.8.0-edmm and v1.8.0

* add zk image id

* update chainspec

* fix: update subproject commit reference for gaiko

* fix: update mrenclave references for gaiko and raiko in release notes

* update zk image ID

* docs update (#565)

---------

Co-authored-by: smtmfft <[email protected]>
Co-authored-by: Roger <[email protected]>

Author: 3 people

Cargo.lock

@@ -1,6 +1,64 @@
+# v1.8.0
+
+## image
+
+us-docker.pkg.dev/evmchain/images/raiko:1.8.0
+
+## gaiko
+
+- mrenclave: fda8bb1fc9938700c25353c0a5fabc96a238e69ce8e35f08e558831a20db33a6
+- mrsigner: ca0583a715534a8c981b914589a7f0dc5d60959d9ae79fb5353299a4231673d5
+
+## raiko
+
+- mrenclave: dcd483d3406d9b1871bb92420f5a080c4372e0d6b8522a4a2cb91a0f736669c6
+- mrsigner: ca0583a715534a8c981b914589a7f0dc5d60959d9ae79fb5353299a4231673d5
+
+# v1.8.0-edmm
+
+## image
+
+us-docker.pkg.dev/evmchain/images/raiko:1.8.0-edmm
+
+## gaiko
+
+- mrenclave: fda8bb1fc9938700c25353c0a5fabc96a238e69ce8e35f08e558831a20db33a6
+- mrsigner: ca0583a715534a8c981b914589a7f0dc5d60959d9ae79fb5353299a4231673d5
+
+## raiko
+
+- mrenclave: 3b589538b775ddbfc5fb028167ff846116159e6687aef9f849ca5a70a7871ea5
+- mrsigner: ca0583a715534a8c981b914589a7f0dc5d60959d9ae79fb5353299a4231673d5
+
+# v1.8.0-zk
+
+-risc0
+risc0 elf image id: 49c8f13fdfbec7c03fc8516ef7d32d8fa43fa4f495d62e9ff6bf63710df402d4
+"/opt/raiko/provers/risc0/guest/target/riscv32im-risc0-zkvm-elf/release/risc0-aggregation"
+
+risc0 elf image id: 052010a130f9957a9d218a173242070c47af1c5d2c3ccae1d8e8d85ce6c7d78e
+"/opt/raiko/provers/risc0/guest/target/riscv32im-risc0-zkvm-elf/release/risc0-batch"
+
+risc0 elf image id: 2548c096b0c3f17c5c879dd9524da88d68cfeb4ddcaeb72561c880801497a776
+"/opt/raiko/provers/risc0/guest/target/riscv32im-risc0-zkvm-elf/release/risc0-guest"
+
+-sp1
+"/opt/raiko/provers/sp1/guest/target/riscv32im-succinct-zkvm-elf/release/sp1-aggregation"
+sp1 elf vk bn256 is: 0x00380861a3c05aa16421c66921e7b952005ddad5b91b81e56d1a5f92a88db099
+sp1 elf vk hash_bytes is: 1c0430d17016a8590438cd241e7b952002eed6ad646e07955a34bf25288db099
+
+"/opt/raiko/provers/sp1/guest/target/riscv32im-succinct-zkvm-elf/release/sp1-batch"
+sp1 elf vk bn256 is: 0x00745853e47349fb2ddb364dae473e099c19890da8c786490da83066a0959689
+sp1 elf vk hash_bytes is: 3a2c29f21cd27ecb3b66c9b56473e09960cc486d231e19241b5060cd20959689
+
+"/opt/raiko/provers/sp1/guest/target/riscv32im-succinct-zkvm-elf/release/sp1-guest"
+sp1 elf vk bn256 is: 0x0034ec939d3130695cae1cbc4e8cc5fe729a99ded3370a3e1a4d53a23043cea3
+sp1 elf vk hash_bytes is: 1a7649ce4c4c1a5715c3978968cc5fe714d4cef64cdc28f8349aa7443043cea3
+
 # v1.7.4-zk
 
 ## zk image
+
 "/opt/raiko/provers/risc0/guest/target/riscv32im-risc0-zkvm-elf/release/risc0-aggregation"
 risc0 elf image id: 02ca31a77475bbef11606b3a35464b0d94d5042f33cb483c4ba10de924a204fb
 "/opt/raiko/provers/risc0/guest/target/riscv32im-risc0-zkvm-elf/release/risc0-batch"

RELEASE.md

@@ -284,15 +284,15 @@ mkdir ~/.config/raiko/config
 mkdir ~/.config/raiko/secrets
 ```
 
-5. Now, clone raiko and check out the `tags/v1.7.3` branch and navigate to the `docker` folder. From here you can pull the images from our registry.
+5. Now, clone raiko and check out the `tags/v1.8.0` branch and navigate to the `docker` folder. From here you can pull the images from our registry.
 
 ```
 git clone https://github.com/taikoxyz/raiko.git
 cd raiko/docker
-git checkout tags/v1.7.3
+git checkout tags/v1.8.0
 ```
 
-> **_NOTE:_** For Taiko Alethia AND Hekla: You will need to modify your raiko `docker-compose.yml` to use the images you pull. If you are using a SGX2 machine, please use `1.7.3-edmm`. If you are using a SGX1 machine, please use `1.7.3`.
+> **_NOTE:_** For Taiko Alethia AND Hekla: You will need to modify your raiko `docker-compose.yml` to use the images you pull. If you are using a SGX2 machine, please use `1.8.0-edmm`. If you are using a SGX1 machine, please use `1.8.0`.
 
 In your `docker-compose.yml` file, search for `raiko:latest` and change all instances to `raiko:{TAG}`. Use the following commands to pull the respective images.
 
@@ -320,7 +320,7 @@ cp .env.sample .env
 ```
 
 If you are running Raiko for Taiko Hekla, ensure `SGXGETH=true`, `NETWORK=taiko_a7` and `L1_NETWORK=holesky` in `.env`.
-If you are running Raiko for Taiko Alethia, **delete `SGXGETH=true` line entirely**, and ensure `NETWORK=taiko_mainnet` and `L1_NETWORK=ethereum` in `.env`.
+If you are running Raiko for Taiko Alethia, ensure `SGXGETH=true`, `NETWORK=taiko_mainnet` and `L1_NETWORK=ethereum` in `.env`.
 
 8. Bootstrap Raiko with the following command:
 
@@ -336,17 +336,14 @@ ls ~/.config/raiko/config
 
 You've now prepared your machine for running Raiko through Docker. Now, you need to perform On-Chain Remote Attestation to receive TTKOh from moderators and begin proving for Taiko!
 
-> **_NOTE:_** If you are running Raiko for Taiko Alethia, you can ignore `bootstrap.gaiko.json`. You will only use `bootstrap.json` for the following steps.
-
 ## On-Chain RA
 
-1. Clone [taiko-mono](https://github.com/taikoxyz/taiko-mono/tree/main), checkout the appropriate tag and navigate to the protocol directory.
+1. Clone [taiko-mono](https://github.com/taikoxyz/taiko-mono/tree/main) and navigate to the protocol directory.
 
 ```
 cd ~
 git clone https://github.com/taikoxyz/taiko-mono.git
 cd taiko-mono
-git checkout tags/taiko-alethia-protocol-v2.3.0
 cd packages/protocol
 ```
 
@@ -366,7 +363,7 @@ pnpm install
 pnpm compile
 ```
 
-3. If you've followed the Raiko Docker guide, you will have bootstrapped raiko and obtained two bootstrap.json files. Both will look like the following:
+3. If you've followed the Raiko Docker guide, you will have bootstrapped raiko and obtained two bootstrap.json files. (`bootstrap.json` and `bootstrap.gaiko.json`) Both will look like the following:
 
 ```
 "public_key": "0x02ab85f14dcdc93832f4bb9b40ad908a5becb840d36f64d21645550ba4a2b28892",
@@ -380,11 +377,9 @@ You can find it with `cat ~/.config/raiko/config/bootstrap.json` or  `cat ~/.con
 
 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.
 
-`NETWORK` will be `hekla-pacaya<sgxreth|sgxgeth>` or `mainnet` depending on which verifier you are registering to.
-
- You will have to do this step twice for Hekla: once for SgxGeth and once for Pacaya. Please use the quote in `bootstrap.gaiko.json` to register for `hekla-pacaya-sgxgeth` and the quote from `bootstrap.json` to register for `hekla-pacaya-sgxreth`. Keep both instance IDs.
+`NETWORK` will be `hekla-pacaya<sgxreth|sgxgeth>` or `mainnet-pacaya<sgxreth|sgxgeth>` depending on which verifier you are registering to.
 
- For Taiko Alethia, you only need to do this step once. Copy the quote from `bootstrap.json` and use `--env mainnet` for the script.
+ You will have to do this step twice: once for SgxGeth and once for Pacaya. Please use the quote in `bootstrap.gaiko.json` to register for `<mainnet|hekla>-pacaya-sgxgeth` and the quote from `bootstrap.json` to register for `<mainnet|hekla>-pacaya-sgxreth`. Keep both instance IDs.
 
 6. If you've been successful, you will get a SGX instance `id` which can be used to run Raiko!
 
@@ -492,7 +487,7 @@ Remove your previously autogenerated priv.key:
 
 2. Checkout the relevant tag/branch
 
-`git checkout tags/v1.7.3` (SGX1) or `git checkout tags/v1.7.3-edmm` (SGX2) for the upcoming Mainnet upgrade.
+`git checkout tags/v1.8.0` for the upcoming Mainnet upgrade.
 
 3. Copy the sample `.env` and make the following changes:
 
@@ -504,33 +499,38 @@ vi .env
 - L1_NETWORK=ethereum
 ```
 
-4. Build the image locally or pull the image from our registry:
+4. Pull the image from our registry or build the image locally:
+
+Pull the image from the registry, use `docker compose pull us-docker.pkg.dev/evmchain/images/raiko:{TAG}`
 
-You can build the image with the following command: `docker compose build raiko`.
+`TAG` should be `1.8.0` if you are using SGX1, `1.8.0-edmm` if you are using SGX2.
 
-If you want to pull the image from the registry, use `docker compose pull us-docker.pkg.dev/evmchain/images/raiko:{TAG}`
+If you prefer, you can build the image with the following command: `docker compose build raiko`.
 
 5. Modify your docker-compose.yml file to use the image.
 
 `vi docker-compose.yml`
-set all instances of raiko image to raiko:1.7.3 or raiko:1.7.3-edmm
+
+set all instances of raiko image to raiko:1.8.0 or raiko:1.8.0-edmm
 
 6. Bootstrap your instance
 
 `docker compose up init`
-If there are no errors, you will use ~/.config/raiko/config/bootstrap.json to do the following steps. You can safely ignore ~/.config/raiko/config/bootstrap.gaiko.json.
+
+If there are no errors, please use `ls ~/.config/raiko/config` to check that the files `bootstrap.json` and `bootstrap.gaiko.json` exist.
 
 7. Navigate to `taiko-mono` and register your instance.
 
-If you haven't done so yet, clone `taiko-mono`. Checkout `taiko-alethia-protocol-v2.3.0`.
+If you haven't done so yet, clone `taiko-mono`. Checkout `main`.
 
 ```bash
 cd packages/protocol
 export PRIVATE_KEY=0x{YOUR_PRIVATE_KEY}
 export FORK_URL={ETH_RPC_URL}
-./script/layer1/provers/config_dcap_sgx_verifier.sh --env mainnet --quote {QUOTE_FROM_BOOTSTRAP.JSON}
+./script/layer1/provers/config_dcap_sgx_verifier.sh --env mainnet-sgxreth --quote {QUOTE_FROM_BOOTSTRAP.JSON}
+./script/layer1/provers/config_dcap_sgx_verifier.sh --env mainnet-sgxgeth --quote {QUOTE_FROM_BOOTSTRAP.GAIKO.JSON}
 ```
-You will use the instance id for the next step.
+You will use the instance ids for the next step.
 
 8. Navigate back to Raiko and modify .env again.
 
@@ -539,13 +539,12 @@ cd raiko/docker
 vi .env
 ```
 
-Set SGX_ONTAKE_INSTANCE_ID= the instance id from previous step. 
+Set `SGX_PACAYA_INSTANCE_ID` to the instance id from the sgxreth run, and `SGXGETH_PACAYA_INSTANCE_ID` to the instance id from the sgxgeth run.
 
 9. Start your Raiko instance again
 
 `docker compose up raiko -d`. You can verify if it's running properly with the tests described in the guide below.
 
-
 ## Verify that your Raiko instance is running properly
 
 Once your Raiko instance is running, you can verify if it was started properly as follows:

docs/README_Docker_and_RA.md

@@ -125,7 +125,7 @@
     {
         "name": "taiko_mainnet",
         "chain_id": 167000,
-        "max_spec_id": "ONTAKE",
+        "max_spec_id": "PACAYA",
         "hard_forks": {
             "HEKLA": {
                 "Block": 0
@@ -134,7 +134,7 @@
                 "Block": 538304
             },
             "PACAYA": {
-                "Block": 99999999
+                "Block": 1166000
             },
             "CANCUN": "TBD"
         },
@@ -160,9 +160,10 @@
                 "RISC0": "0x55902b2D3DF2A65370A89C86Ae9dd71Ecd508edc"
             },
             "PACAYA": {
-                "SGX": "0xb0f3186FC1963f774f52ff455DC86aEdD0b31F81",
-                "SP1": "0x5c44f2239925b0d86d2BFEe539f19CD0A08Af452",
-                "RISC0": "0x55902b2D3DF2A65370A89C86Ae9dd71Ecd508edc"
+                "SGX": "0x9e322fC59b8f4A29e6b25c3a166ac1892AA30136",
+                "SP1": "0xbee1040D0Aab17AE19454384904525aE4A3602B9",
+                "RISC0": "0x73Ee496dA20e5C65340c040B0D8c3C891C1f74AE",
+                "SGXGETH": "0x7e6409e9b6c5e2064064a6cC994f9a2e95680782"
             }
         },
         "genesis_time": 0,