Closed 0xHansLee closed 5 months ago
The recent update involves a modification to a time-related configuration parameter, specifically the EcotoneTime
value. This value has been adjusted from 1713772801
to 1714032001
in two related files. The change affects both the main configuration and its associated tests, ensuring consistency across the application's settings.
Files | Change Summary |
---|---|
op-node/chaincfg/chains.go ,op-node/chaincfg/chains_test.go |
Updated EcotoneTime from 1713772801 to 1714032001 . |
op-node/chaincfg/chains.go (1)
`44-44`: Change to `EcotoneTime` correctly updates the activation time for the Kroma mainnet as intended. Please ensure that this new activation time (`Thu Apr 25 2024 08:00:01` UTC) is correctly reflected in all relevant parts of the system and that it aligns with other dependent configurations or systems.op-node/chaincfg/chains_test.go (1)
`71-71`: Change to `EcotoneTime` in the test configuration correctly updates the activation time for the Kroma mainnet as intended. Please ensure that this new activation time (`Thu Apr 25 2024 08:00:01` UTC) is correctly reflected in all relevant test configurations and that it aligns with the production environment settings.
Change Ecotone activation time for Kroma mainnet. The activation time is
Thu Apr 25 2024 08:00:01
(unix timestamp1714032001
).Summary by CodeRabbit
EcotoneTime
configuration to reflect the correct time-related settings.