Revert "feat: upgrade Kroma mainnet to v1.4.1 (#35)"

This reverts commit 7980739.

.env.mainnet

@@ -1,20 +1,18 @@
 # Network to run the node on ("mainnet")
 NETWORK_NAME=mainnet
 
-IMAGE_TAG__KROMA_GETH=v0.5.1
-IMAGE_TAG__KROMA_NODE=v1.4.1
-IMAGE_TAG__KROMA_VALIDATOR=v1.4.1
+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
 
 # L1 RPC endpoint.
 # You can check and use one of the list of RPC endpoints: https://chainlist.org/chain/1
 # Or you can also use Alchemy or Infura, etc.
-# After Ecotone activation, you need also L1 Beacon endpoint to get blob data.
 # You must use a websocket RPC endpoint to run a validator node for below reasons:
 # As an asserter, to respond if a challenge is created to the output you submitted.
 # As a challenger, to observe output submission events and create challenge to an invalid output.
-KROMA_NODE__L1_BEACON_ENDPOINT=
 KROMA_NODE__L1_RPC_ENDPOINT=
 KROMA_VALIDATOR__L1_RPC_ENDPOINT=
 

config/mainnet/rollup.json

@@ -28,6 +28,5 @@
   "l1_system_config_address": "0x3971eb866aa9b2b8afea8a7c816f3b7e8b195a35",
   "regolith_time": 0,
   "canyon_time": 1708502400,
-  "delta_time": 1709107200,
-  "ecotone_time": 1713772801
+  "delta_time": 1709107200
 }

envs/mainnet/node.env

@@ -1,5 +1,4 @@
 NODE_L1_ETH_RPC=${KROMA_NODE__L1_RPC_ENDPOINT}
-NODE_L1_BEACON=${KROMA_NODE__L1_BEACON_ENDPOINT}
 NODE_L2_ENGINE_RPC=http://kroma-geth:8551
 
 NODE_L2_ENGINE_AUTH=/.kroma/keys/jwt-secret.txt

upgrades/v1.4.1.md → upgrades/v1.4.0.md

@@ -1,27 +1,17 @@
-# Kroma `v1.4.1` Upgrade Instructions
+# Kroma `v1.4.0` Upgrade Instructions
 
-This document provides instructions to upgrade from Kroma `v1.3.4` to `v1.4.1`.
+This document provides instructions to upgrade from Kroma `v1.3.4` to `v1.4.0`.
 
-For more details about `v1.4.1`, please refer the [release note](https://github.com/kroma-network/kroma/releases/tag/v1.4.1).
+For more details about `v1.4.0`, please refer the [release note](https://github.com/kroma-network/kroma/releases/tag/v1.4.0).
 This upgrade mainly includes upstream of Optimism [`v1.7.2`](https://github.com/ethereum-optimism/optimism/releases/tag/v1.7.2)
 This upgrade includes Ecotone upgrade, which enables Kroma-batcher to post batch using blob-carrying transaction.
 So all full nodes and validators must complete the upgrade before the Ecotone upgrade is activated.
 The activation time of Ecotone upgrade is scheduled as below:
 
 - Kroma sepolia: `Wed Apr 17 2024 08:00:00 UTC`
-- Kroma mainnet: `Mon Apr 22 2024 08:00:01 UTC`
 
 ## Guides for upgrade
 
-### Pull the latest version of kroma-up
-
-First of all, pull the latest kroma-up and checkout to v1.4.1.
-
-```bash
-git pull origin main
-git checkout tags/v1.4.1
-```
-
 ### Stop Kroma
 
 For upgrade, stop your Kroma full node or validator.
@@ -39,9 +29,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.5.1
-IMAGE_TAG__KROMA_NODE=v1.4.1
-IMAGE_TAG__KROMA_VALIDATOR=v1.4.1
+IMAGE_TAG__KROMA_GETH=v0.5.0
+IMAGE_TAG__KROMA_NODE=v1.4.0
+IMAGE_TAG__KROMA_VALIDATOR=v1.4.0
 ```
 
 Also, after activation of Ecotone, you need L1 Beacon endpoint to get blob information.
@@ -50,18 +40,9 @@ Also, after activation of Ecotone, you need L1 Beacon endpoint to get blob infor
 KROMA_NODE__L1_BEACON_ENDPOINT=
 ```
 
-And Ecotone activation time should be added to `rollup.json`. Please make sure that the following field is added. 
-You can also refer the modified `rollup.json` file for [Kroma mainnet](../config/mainnet/rollup.json) or 
-[Kroma sepolia](../config/sepolia/rollup.json).
-
-For Kroma mainnet,
-```json
-{
-  "ecotone_time": 1713772801
-}
-```
+And Ecotone activation time should be added to `rollup.json`. Please make sure that the following field is added for 
+Kroma sepolia. You can also refer the modified [`rollup.json`](../config/sepolia/rollup.json).
 
-For Kroma sepolia,
 ```json
 {
   "ecotone_time": 1713340800