From f139530c6bf365440968c26688d81caffc84383e Mon Sep 17 00:00:00 2001 From: Ayaan Date: Wed, 28 Feb 2024 18:07:48 +0900 Subject: [PATCH 1/8] feat: upgrade Kroma sepolia to v1.3.2 --- .env.sepolia | 6 +++--- envs/sepolia/geth.env | 3 ++- upgrades/v1.3.2.md | 41 +++++++++++++++++++++++++++++++++++++++++ 3 files changed, 46 insertions(+), 4 deletions(-) create mode 100644 upgrades/v1.3.2.md diff --git a/.env.sepolia b/.env.sepolia index e37d66d..7940020 100644 --- a/.env.sepolia +++ b/.env.sepolia @@ -1,9 +1,9 @@ # Network to run the node on ("sepolia") NETWORK_NAME=sepolia -IMAGE_TAG__KROMA_GETH=v0.4.3 -IMAGE_TAG__KROMA_NODE=v1.3.0 -IMAGE_TAG__KROMA_VALIDATOR=v1.3.0 +IMAGE_TAG__KROMA_GETH=v0.4.4 +IMAGE_TAG__KROMA_NODE=v1.3.2 +IMAGE_TAG__KROMA_VALIDATOR=v1.3.2 IMAGE_TAG__KROMA_PROVER_PROXY=v0.1.2 IMAGE_TAG__KROMA_PROVER=v0.1.4 diff --git a/envs/sepolia/geth.env b/envs/sepolia/geth.env index 3c56452..71b3c84 100644 --- a/envs/sepolia/geth.env +++ b/envs/sepolia/geth.env @@ -1,2 +1,3 @@ CHAIN_ID=2358 -BOOT_NODES=${KROMA_GETH__BOOT_NODES} \ No newline at end of file +BOOT_NODES=${KROMA_GETH__BOOT_NODES} +GETH_MINER_RECOMMIT=100ms \ No newline at end of file diff --git a/upgrades/v1.3.2.md b/upgrades/v1.3.2.md new file mode 100644 index 0000000..762b0cc --- /dev/null +++ b/upgrades/v1.3.2.md @@ -0,0 +1,41 @@ +# Kroma `v1.3.2` Upgrade Instructions + +This document provides instructions to upgrade from Kroma `v1.3.1` to `v1.3.2`. +**No changes in flags have been made on this release, so you can simply change the tag for upgrade.** +For more details about `v1.3.2`, please refer the [release note](https://github.com/kroma-network/kroma/releases/tag/v1.3.2). + +## Guides for upgrade + +### Stop Kroma + +For upgrade, stop your Kroma full node or validator. +```bash +# for full node +docker compose --profile fullnode down + +# for validator +docker compose --profile validator down +``` + +### Common + +You need to update your `.env` file. + +First, update the tag of `kroma-node` and `kroma-validator` docker image. +``` +IMAGE_TAG__KROMA_GETH=v0.4.4 +IMAGE_TAG__KROMA_NODE=v1.3.2 +IMAGE_TAG__KROMA_VALIDATOR=v1.3.2 +``` + +### Start Kroma + +You can now start Kroma full node or validator with a new version. + +```bash +# for full node +docker compose --profile fullnode up -d + +# for validator +docker compose --profile validator up -d +``` \ No newline at end of file From 1c4ecb9ac87bf6a4b9fad92638b47b6c26ae42b9 Mon Sep 17 00:00:00 2001 From: Hansol Lee <38912532+0xHansLee@users.noreply.github.com> Date: Wed, 6 Mar 2024 17:58:21 +0900 Subject: [PATCH 2/8] feat: upgrade mainnet to v1.3.2 (#28) --- .env.mainnet | 6 +++--- envs/mainnet/geth.env | 1 + upgrades/v1.3.2.md | 3 ++- 3 files changed, 6 insertions(+), 4 deletions(-) diff --git a/.env.mainnet b/.env.mainnet index 1c7f78b..2fc53ae 100644 --- a/.env.mainnet +++ b/.env.mainnet @@ -1,9 +1,9 @@ # Network to run the node on ("mainnet") NETWORK_NAME=mainnet -IMAGE_TAG__KROMA_GETH=v0.4.3 -IMAGE_TAG__KROMA_NODE=v1.3.1 -IMAGE_TAG__KROMA_VALIDATOR=v1.3.1 +IMAGE_TAG__KROMA_GETH=v0.4.4 +IMAGE_TAG__KROMA_NODE=v1.3.2 +IMAGE_TAG__KROMA_VALIDATOR=v1.3.2 IMAGE_TAG__KROMA_PROVER_PROXY=v0.1.2 IMAGE_TAG__KROMA_PROVER=v0.1.4 diff --git a/envs/mainnet/geth.env b/envs/mainnet/geth.env index 67b652b..255e95c 100644 --- a/envs/mainnet/geth.env +++ b/envs/mainnet/geth.env @@ -1,2 +1,3 @@ CHAIN_ID=255 BOOT_NODES=${KROMA_GETH__BOOT_NODES} +GETH_MINER_RECOMMIT=100ms diff --git a/upgrades/v1.3.2.md b/upgrades/v1.3.2.md index 762b0cc..966c670 100644 --- a/upgrades/v1.3.2.md +++ b/upgrades/v1.3.2.md @@ -3,6 +3,7 @@ This document provides instructions to upgrade from Kroma `v1.3.1` to `v1.3.2`. **No changes in flags have been made on this release, so you can simply change the tag for upgrade.** For more details about `v1.3.2`, please refer the [release note](https://github.com/kroma-network/kroma/releases/tag/v1.3.2). +This upgrade mainly includes activation of KromaZKTrie for better performance in terms of block processing. ## Guides for upgrade @@ -38,4 +39,4 @@ docker compose --profile fullnode up -d # for validator docker compose --profile validator up -d -``` \ No newline at end of file +``` From 97f2d8ed4dbc27c4f5eeafcb8f71d5c3cfc82534 Mon Sep 17 00:00:00 2001 From: Hansol Lee <38912532+0xHansLee@users.noreply.github.com> Date: Wed, 13 Mar 2024 19:21:35 +0900 Subject: [PATCH 3/8] feat: rollback mainnet to v1.3.1 (#29) * feat: rollback mainnet to v1.3.1 * Update rollback.sh --------- Co-authored-by: Techwoo --- .env.mainnet | 6 +++--- envs/mainnet/geth.env | 1 - envs/sepolia/geth.env | 2 +- rollback.sh | 23 +++++++++++++++++++++++ upgrades/rollback.md | 36 ++++++++++++++++++++++++++++++++++++ 5 files changed, 63 insertions(+), 5 deletions(-) create mode 100644 rollback.sh create mode 100644 upgrades/rollback.md diff --git a/.env.mainnet b/.env.mainnet index 2fc53ae..1c7f78b 100644 --- a/.env.mainnet +++ b/.env.mainnet @@ -1,9 +1,9 @@ # Network to run the node on ("mainnet") NETWORK_NAME=mainnet -IMAGE_TAG__KROMA_GETH=v0.4.4 -IMAGE_TAG__KROMA_NODE=v1.3.2 -IMAGE_TAG__KROMA_VALIDATOR=v1.3.2 +IMAGE_TAG__KROMA_GETH=v0.4.3 +IMAGE_TAG__KROMA_NODE=v1.3.1 +IMAGE_TAG__KROMA_VALIDATOR=v1.3.1 IMAGE_TAG__KROMA_PROVER_PROXY=v0.1.2 IMAGE_TAG__KROMA_PROVER=v0.1.4 diff --git a/envs/mainnet/geth.env b/envs/mainnet/geth.env index 255e95c..67b652b 100644 --- a/envs/mainnet/geth.env +++ b/envs/mainnet/geth.env @@ -1,3 +1,2 @@ CHAIN_ID=255 BOOT_NODES=${KROMA_GETH__BOOT_NODES} -GETH_MINER_RECOMMIT=100ms diff --git a/envs/sepolia/geth.env b/envs/sepolia/geth.env index 71b3c84..2e56345 100644 --- a/envs/sepolia/geth.env +++ b/envs/sepolia/geth.env @@ -1,3 +1,3 @@ CHAIN_ID=2358 BOOT_NODES=${KROMA_GETH__BOOT_NODES} -GETH_MINER_RECOMMIT=100ms \ No newline at end of file +GETH_MINER_RECOMMIT=100ms diff --git a/rollback.sh b/rollback.sh new file mode 100644 index 0000000..a7dd5f7 --- /dev/null +++ b/rollback.sh @@ -0,0 +1,23 @@ +#!/bin/bash + +SNAPSHOT_ORIGIN=https://snapshot.kroma.network/rollback/snapshot.tar.gz +KROMA_DB_PATH=/.kroma/db/geth +SNAPSHOT_PATH=.snapshot_rollback + +mkdir -p ${SNAPSHOT_PATH} +wget -P ./${SNAPSHOT_PATH} ${SNAPSHOT_ORIGIN} +tar xvzf ${SNAPSHOT_PATH}/snapshot.tar.gz -C ${SNAPSHOT_PATH}/ +rm -rf ${SNAPSHOT_PATH}/snapshot.tar.gz ${SNAPSHOT_PATH}/nodekey + +docker stop kroma-node + +docker exec -it kroma-geth sh -c "mv ${KROMA_DB_PATH}/nodekey ../nodekey" +docker exec -it kroma-geth sh -c "rm -rf ${KROMA_DB_PATH}/*" +docker exec -it kroma-geth sh -c "mv ../nodekey ${KROMA_DB_PATH}/nodekey" + +docker cp ${SNAPSHOT_PATH}/. kroma-geth:${KROMA_DB_PATH}/ +rm -rf ${SNAPSHOT_PATH} + +docker restart kroma-geth +sleep 5 +docker start kroma-node diff --git a/upgrades/rollback.md b/upgrades/rollback.md new file mode 100644 index 0000000..2b10789 --- /dev/null +++ b/upgrades/rollback.md @@ -0,0 +1,36 @@ +# Rollback Instructions to `v1.3.1` + +The mainnet has experienced a fork starting from block #8171899 due to the recent upgrade to version `v1.3.2`. This +update included an enhanced ZKTrie component with the geth version `v0.4.4`. + +To prevent further complications and potential damage, we have decided to undertake a rollback of our nodes including +the sequencer and the validator node to block #8171899. This rollback will also involve downgrading our client to the +previous version, v1.3.1. + +This document provides an instruction for rollback to `v1.3.1`. + +## Pull the latest version of kroma-up + +For rollback, pull the latest version of kroma-up + +```bash +git pull origin main +``` + +## Downgrade the version + +Also, downgrade the version of kroma and kroma-geth in `.env` file. + +``` +IMAGE_TAG__KROMA_GETH=v0.4.3 +IMAGE_TAG__KROMA_NODE=v1.3.1 +IMAGE_TAG__KROMA_VALIDATOR=v1.3.1 +``` + +## Rollback the node + +Then, rollback the node by executing the below script. + +```bash +./rollback.sh +``` From 5b4d8f391f3372940c400c6c318167ca56aa0d73 Mon Sep 17 00:00:00 2001 From: amis13 <119992979+amis13@users.noreply.github.com> Date: Thu, 14 Mar 2024 05:16:41 +0100 Subject: [PATCH 4/8] Update rollback.md (#30) Adding execution permissions to rollback.sh --- upgrades/rollback.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/upgrades/rollback.md b/upgrades/rollback.md index 2b10789..fcc3ab0 100644 --- a/upgrades/rollback.md +++ b/upgrades/rollback.md @@ -29,7 +29,11 @@ IMAGE_TAG__KROMA_VALIDATOR=v1.3.1 ## Rollback the node -Then, rollback the node by executing the below script. +First grant execution permissions. +```bash +chmod +x rollback.sh +``` +Then, rollback the node by executing the below script. ```bash ./rollback.sh From 89e76f9b02df54a4c0649ec54010faced94ac572 Mon Sep 17 00:00:00 2001 From: Jinn Date: Tue, 19 Mar 2024 18:14:10 +0900 Subject: [PATCH 5/8] chore: improve snapshot speed --- rollback.sh | 22 ++++++++-------------- sync_block.sh | 19 ++++--------------- 2 files changed, 12 insertions(+), 29 deletions(-) mode change 100644 => 100755 rollback.sh diff --git a/rollback.sh b/rollback.sh old mode 100644 new mode 100755 index a7dd5f7..b7a8ac9 --- a/rollback.sh +++ b/rollback.sh @@ -2,22 +2,16 @@ SNAPSHOT_ORIGIN=https://snapshot.kroma.network/rollback/snapshot.tar.gz KROMA_DB_PATH=/.kroma/db/geth -SNAPSHOT_PATH=.snapshot_rollback - -mkdir -p ${SNAPSHOT_PATH} -wget -P ./${SNAPSHOT_PATH} ${SNAPSHOT_ORIGIN} -tar xvzf ${SNAPSHOT_PATH}/snapshot.tar.gz -C ${SNAPSHOT_PATH}/ -rm -rf ${SNAPSHOT_PATH}/snapshot.tar.gz ${SNAPSHOT_PATH}/nodekey docker stop kroma-node +docker exec -it kroma-geth sh -c "rm -rf ${KROMA_DB_PATH}/LOCK" +docker exec -it kroma-geth sh -c "rm -rf ${KROMA_DB_PATH}/blobpool" +docker exec -it kroma-geth sh -c "rm -rf ${KROMA_DB_PATH}/chaindata" +docker exec -it kroma-geth sh -c "rm -rf ${KROMA_DB_PATH}/lightchaindata" +docker exec -it kroma-geth sh -c "rm -rf ${KROMA_DB_PATH}/nodes" +docker exec -it kroma-geth sh -c "rm -rf ${KROMA_DB_PATH}/transactions.rlp" -docker exec -it kroma-geth sh -c "mv ${KROMA_DB_PATH}/nodekey ../nodekey" -docker exec -it kroma-geth sh -c "rm -rf ${KROMA_DB_PATH}/*" -docker exec -it kroma-geth sh -c "mv ../nodekey ${KROMA_DB_PATH}/nodekey" - -docker cp ${SNAPSHOT_PATH}/. kroma-geth:${KROMA_DB_PATH}/ -rm -rf ${SNAPSHOT_PATH} - +docker exec -it kroma-geth sh -c "cd /.kroma/db/geth && wget -O - ${SNAPSHOT_ORIGIN} | tar -xvz" docker restart kroma-geth sleep 5 -docker start kroma-node +docker start kroma-node \ No newline at end of file diff --git a/sync_block.sh b/sync_block.sh index 7aa3499..061f7b4 100755 --- a/sync_block.sh +++ b/sync_block.sh @@ -6,30 +6,19 @@ if [[ -z $NETWORK_NAME ]]; then echo "Error: Argument not provided. Usage: $0 . Allowed values are 'sepolia' or 'mainnet'." exit 1 elif [[ $NETWORK_NAME == "sepolia" ]]; then - SNAPSHOT_ORIGIN=https://snapshot.sepolia.kroma.network/latest/snapshot.tar.gz + SNAPSHOT_ORIGIN=https://snapshot.sepolia.kroma.network/test/snapshot.tar.gz elif [[ $NETWORK_NAME == "mainnet" ]]; then - SNAPSHOT_ORIGIN=https://snapshot.kroma.network/latest/snapshot.tar.gz + SNAPSHOT_ORIGIN=https://snapshot.kroma.network/test/snapshot.tar.gz else echo "Error: Invalid network. Allowed values are 'sepolia' or 'mainnet'." exit 1 fi KROMA_DB_PATH=/.kroma/db/geth -SNAPSHOT_PATH=.snapshot_$(date +%s | base64 | cut -c 1-10) - -mkdir -p ${SNAPSHOT_PATH} -wget -P ./${SNAPSHOT_PATH} ${SNAPSHOT_ORIGIN} -tar xvzf ${SNAPSHOT_PATH}/snapshot.tar.gz -C ${SNAPSHOT_PATH}/ -rm -rf ${SNAPSHOT_PATH}/snapshot.tar.gz ${SNAPSHOT_PATH}/nodekey docker stop kroma-node - -docker exec -it kroma-geth sh -c "mv ${KROMA_DB_PATH}/nodekey ../nodekey" -docker exec -it kroma-geth sh -c "rm -rf ${KROMA_DB_PATH}/*" -docker exec -it kroma-geth sh -c "mv ../nodekey ${KROMA_DB_PATH}/nodekey" - -docker cp ${SNAPSHOT_PATH}/. kroma-geth:${KROMA_DB_PATH}/ -rm -rf ${SNAPSHOT_PATH} +docker exec -it kroma-geth sh -c "rm -rf ${KROMA_DB_PATH}/chaindata" +docker exec -it kroma-geth sh -c "cd /.kroma/db/geth && wget -O - ${SNAPSHOT_ORIGIN} | tar -xvz" docker restart kroma-geth sleep 5 From 116174b8d30af8ccee954bfc3eba2b72a662425b Mon Sep 17 00:00:00 2001 From: Techwoo Date: Thu, 21 Mar 2024 20:24:27 +0900 Subject: [PATCH 6/8] Update sync_block.sh --- sync_block.sh | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/sync_block.sh b/sync_block.sh index 061f7b4..e639b00 100755 --- a/sync_block.sh +++ b/sync_block.sh @@ -6,9 +6,9 @@ if [[ -z $NETWORK_NAME ]]; then echo "Error: Argument not provided. Usage: $0 . Allowed values are 'sepolia' or 'mainnet'." exit 1 elif [[ $NETWORK_NAME == "sepolia" ]]; then - SNAPSHOT_ORIGIN=https://snapshot.sepolia.kroma.network/test/snapshot.tar.gz + SNAPSHOT_ORIGIN=https://snapshot.sepolia.kroma.network/latest/snapshot.tar.gz elif [[ $NETWORK_NAME == "mainnet" ]]; then - SNAPSHOT_ORIGIN=https://snapshot.kroma.network/test/snapshot.tar.gz + SNAPSHOT_ORIGIN=https://snapshot.kroma.network/latest/snapshot.tar.gz else echo "Error: Invalid network. Allowed values are 'sepolia' or 'mainnet'." exit 1 From 81166b506da7a99cfe904be053ce74e943ff4a18 Mon Sep 17 00:00:00 2001 From: Hansol Lee <38912532+0xHansLee@users.noreply.github.com> Date: Thu, 28 Mar 2024 13:22:09 +0900 Subject: [PATCH 7/8] feat: upgrade kroma mainnet and kroma sepolia to v1.3.3 (#32) --- .env.mainnet | 6 +++--- .env.sepolia | 6 +++--- envs/mainnet/geth.env | 1 + upgrades/v1.3.3.md | 47 +++++++++++++++++++++++++++++++++++++++++++ 4 files changed, 54 insertions(+), 6 deletions(-) create mode 100644 upgrades/v1.3.3.md diff --git a/.env.mainnet b/.env.mainnet index 1c7f78b..75deace 100644 --- a/.env.mainnet +++ b/.env.mainnet @@ -1,9 +1,9 @@ # Network to run the node on ("mainnet") NETWORK_NAME=mainnet -IMAGE_TAG__KROMA_GETH=v0.4.3 -IMAGE_TAG__KROMA_NODE=v1.3.1 -IMAGE_TAG__KROMA_VALIDATOR=v1.3.1 +IMAGE_TAG__KROMA_GETH=v0.4.5 +IMAGE_TAG__KROMA_NODE=v1.3.3 +IMAGE_TAG__KROMA_VALIDATOR=v1.3.3 IMAGE_TAG__KROMA_PROVER_PROXY=v0.1.2 IMAGE_TAG__KROMA_PROVER=v0.1.4 diff --git a/.env.sepolia b/.env.sepolia index 7940020..59305ad 100644 --- a/.env.sepolia +++ b/.env.sepolia @@ -1,9 +1,9 @@ # Network to run the node on ("sepolia") NETWORK_NAME=sepolia -IMAGE_TAG__KROMA_GETH=v0.4.4 -IMAGE_TAG__KROMA_NODE=v1.3.2 -IMAGE_TAG__KROMA_VALIDATOR=v1.3.2 +IMAGE_TAG__KROMA_GETH=v0.4.5 +IMAGE_TAG__KROMA_NODE=v1.3.3 +IMAGE_TAG__KROMA_VALIDATOR=v1.3.3 IMAGE_TAG__KROMA_PROVER_PROXY=v0.1.2 IMAGE_TAG__KROMA_PROVER=v0.1.4 diff --git a/envs/mainnet/geth.env b/envs/mainnet/geth.env index 67b652b..255e95c 100644 --- a/envs/mainnet/geth.env +++ b/envs/mainnet/geth.env @@ -1,2 +1,3 @@ CHAIN_ID=255 BOOT_NODES=${KROMA_GETH__BOOT_NODES} +GETH_MINER_RECOMMIT=100ms diff --git a/upgrades/v1.3.3.md b/upgrades/v1.3.3.md new file mode 100644 index 0000000..8385f32 --- /dev/null +++ b/upgrades/v1.3.3.md @@ -0,0 +1,47 @@ +# Kroma `v1.3.3` Upgrade Instructions + +This document provides instructions to upgrade from Kroma `v1.3.1` to `v1.3.3`. +**No changes in flags have been made on this release, so you can simply change the tag for upgrade.** +For more details about `v1.3.3`, please refer the [release note](https://github.com/kroma-network/kroma/releases/tag/v1.3.3). +This upgrade mainly includes activation of fixed `KromaZKTrie` for better performance in terms of block processing. + +## Guides for upgrade + +### Stop Kroma + +For upgrade, stop your Kroma full node or validator. +```bash +# for full node +docker compose --profile fullnode down + +# for validator +docker compose --profile validator down +``` + +### Common + +You need to update your `.env` file. + +First, update the tag of `kroma-node` and `kroma-validator` docker image. +``` +IMAGE_TAG__KROMA_GETH=v0.4.5 +IMAGE_TAG__KROMA_NODE=v1.3.3 +IMAGE_TAG__KROMA_VALIDATOR=v1.3.3 +``` + +Also, a field is added to `geth.env`. Please make sure your `geth.eng` has the following field. +``` +GETH_MINER_RECOMMIT=100ms +``` + +### Start Kroma + +You can now start Kroma full node or validator with a new version. + +```bash +# for full node +docker compose --profile fullnode up -d + +# for validator +docker compose --profile validator up -d +``` From a16e6666481baae35be854527c929c8cdfecb0af Mon Sep 17 00:00:00 2001 From: Hansol Lee <38912532+0xHansLee@users.noreply.github.com> Date: Mon, 1 Apr 2024 18:09:56 +0900 Subject: [PATCH 8/8] feat: upgrade kroma mainnet and kroma sepolia to v1.3.4 (#33) --- .env.mainnet | 6 +++--- .env.sepolia | 6 +++--- upgrades/{v1.3.3.md => v1.3.4.md} | 12 ++++++------ 3 files changed, 12 insertions(+), 12 deletions(-) rename upgrades/{v1.3.3.md => v1.3.4.md} (78%) diff --git a/.env.mainnet b/.env.mainnet index 75deace..15d71f4 100644 --- a/.env.mainnet +++ b/.env.mainnet @@ -1,9 +1,9 @@ # Network to run the node on ("mainnet") NETWORK_NAME=mainnet -IMAGE_TAG__KROMA_GETH=v0.4.5 -IMAGE_TAG__KROMA_NODE=v1.3.3 -IMAGE_TAG__KROMA_VALIDATOR=v1.3.3 +IMAGE_TAG__KROMA_GETH=v0.4.6 +IMAGE_TAG__KROMA_NODE=v1.3.4 +IMAGE_TAG__KROMA_VALIDATOR=v1.3.4 IMAGE_TAG__KROMA_PROVER_PROXY=v0.1.2 IMAGE_TAG__KROMA_PROVER=v0.1.4 diff --git a/.env.sepolia b/.env.sepolia index 59305ad..854c532 100644 --- a/.env.sepolia +++ b/.env.sepolia @@ -1,9 +1,9 @@ # Network to run the node on ("sepolia") NETWORK_NAME=sepolia -IMAGE_TAG__KROMA_GETH=v0.4.5 -IMAGE_TAG__KROMA_NODE=v1.3.3 -IMAGE_TAG__KROMA_VALIDATOR=v1.3.3 +IMAGE_TAG__KROMA_GETH=v0.4.6 +IMAGE_TAG__KROMA_NODE=v1.3.4 +IMAGE_TAG__KROMA_VALIDATOR=v1.3.4 IMAGE_TAG__KROMA_PROVER_PROXY=v0.1.2 IMAGE_TAG__KROMA_PROVER=v0.1.4 diff --git a/upgrades/v1.3.3.md b/upgrades/v1.3.4.md similarity index 78% rename from upgrades/v1.3.3.md rename to upgrades/v1.3.4.md index 8385f32..fe13996 100644 --- a/upgrades/v1.3.3.md +++ b/upgrades/v1.3.4.md @@ -1,8 +1,8 @@ -# Kroma `v1.3.3` Upgrade Instructions +# Kroma `v1.3.4` Upgrade Instructions -This document provides instructions to upgrade from Kroma `v1.3.1` to `v1.3.3`. +This document provides instructions to upgrade from Kroma `v1.3.1` to `v1.3.4`. **No changes in flags have been made on this release, so you can simply change the tag for upgrade.** -For more details about `v1.3.3`, please refer the [release note](https://github.com/kroma-network/kroma/releases/tag/v1.3.3). +For more details about `v1.3.4`, please refer the [release note](https://github.com/kroma-network/kroma/releases/tag/v1.3.4). This upgrade mainly includes activation of fixed `KromaZKTrie` for better performance in terms of block processing. ## Guides for upgrade @@ -24,9 +24,9 @@ You need to update your `.env` file. First, update the tag of `kroma-node` and `kroma-validator` docker image. ``` -IMAGE_TAG__KROMA_GETH=v0.4.5 -IMAGE_TAG__KROMA_NODE=v1.3.3 -IMAGE_TAG__KROMA_VALIDATOR=v1.3.3 +IMAGE_TAG__KROMA_GETH=v0.4.6 +IMAGE_TAG__KROMA_NODE=v1.3.4 +IMAGE_TAG__KROMA_VALIDATOR=v1.3.4 ``` Also, a field is added to `geth.env`. Please make sure your `geth.eng` has the following field.