Releases: taikoxyz/simple-taiko-node
v1.17.2
1.17.2 (2025-06-06) is a pre-release for the Taiko Hekla testnet, with changes for based preconfirmations.
Note that since this is Stage 1 Whitelisted Preconfirmations, community members WILL NOT be able to propose/prove blocks. Community proposer/provers are encouraged to disable their proposer/provers to prevent loss of funds. Read more about the based preconfirmations rollout here.
Required Software Versions
The versions listed below are the minimum required for the upgrade. Please note that newer versions may be released, and it's advised to stay updated.
Command-Line Flag Changes
Driver Flag Changes
--taikoL1
has been replaced by--taikoInbox
. Functionally remains the same.--taikoL2
has been replaced by--taikoAnchor
. Functionally remains the same.--preconfirmation.serverPort
: Optional config. HTTP port of the preconfirmation block server, 0 means disabled.--preconfirmation.jwtSecret
: Optional config. Path to a JWT secret to use for the preconfirmation block server.--preconfirmation.corsOrigins
: Optional config. CORS Origins settings for the preconfirmation block server, default value is*
.--preconfirmation.whitelist
: Optional config. PreconfWhitelist contract L1 address.--preconfirmation.handoverSkipSlots
: Optional config. Handover slots to provide a boundary at the end of an epoch, default value is 4.
Proposer Flag Changes
--txPool.locals
: DEPRECATED Priority inclusion accounts list has been deprecated.--txPool.localsOnly
: DEPRECATED Same as above.
Prover Flag Changes
--prover.startingBlockID
has been replaced by--prover.startingBatchID
.--prover.localProposerAddresses
: Optional config. Comma separated list of local proposer addresses, if set, prover will prove the batches proposed by these addresses before the assignment expiration time.--graffiti
: DEPRECATED Adding additional graffiti info to proof evidence has been deprecated.--mode.contester
: DEPRECATED Contesters no longer part of protocol.--prover.port
: DEPRECATED--http.maxExpiry
: DEPRECATED--prover.guardianProverHealthCheckServerEndpoint
: DEPRECATED Guardians no longer part of protocol.--guardianProverMinority
: DEPRECATED--guardianProverMajority
: DEPRECATED--guardian.submissionDelay
: DEPRECATED--prover.enableLivenessBondProof
: DEPRECATED--prover.l1NodeVersion
: DEPRECATED--prover.l2NodeVersion
: DEPRECATED
Chores
v1.17.1
v1.17.0
v1.16.1
1.16.1 (2025-05-21)
Mandatory Update
Key Dates
- The contract upgrade will take place at 2:00 PM on May 20, 2025(UTC +8).
- Pacaya Fork: Estimated for May 21, 2025 UTC at block height 1,166,000. The exact time may vary due to block time variability.
Required Software Versions
The versions listed below are the minimum required for the upgrade. Please note that newer versions may be released, and it's advised to stay updated.
- Taiko BCR Protocol v2.3.0 — If using a ProverSet for block proposals, update to the new implementation.
- taiko-geth v1.15.1-hotfix
- taiko-client v1.5.1
- simple-taiko-node v1.16.1
- raiko v1.8.0
Failure to upgrade may lead to proof operation failure or operational issues.
Bug Fixes
v1.16.0
1.16.0 (2025-05-16)
Mandatory Update
Key Dates
- The contract upgrade will take place at 2:00 PM on May 20, 2025(UTC +8).
- Pacaya Fork: Estimated for May 21, 2025 UTC at block height 1,166,000. The exact time may vary due to block time variability.
Required Software Versions
The versions listed below are the minimum required for the upgrade. Please note that newer versions may be released, and it's advised to stay updated.
- Taiko BCR Protocol v2.3.0 — If using a ProverSet for block proposals, update to the new implementation.
- taiko-geth v1.15.1
- taiko-client v1.5.1-hotfix
- simple-taiko-node v1.16.1
- raiko v1.8.0
Failure to upgrade may lead to proof operation failure or operational issues.
Features
v1.15.0
1.15.0 (2025-04-30)
1.15.0 (2025-04-30) is a mandatory update for all Mainnet node operators, introducing compatibility changes for the upcoming Ethereum Electra hardfork (Wed May 07 10:05:11 2025 UTC).
Required Software Versions
The versions listed below are the compatible software versions. Please note that newer versions may be released, and it's advised to stay updated.
Features
v1.14.0
v1.13.1
1.13.1 is a release only for the Hekla testnet, with support for the upcoming Hekla Pacaya fork, as well as optimizations and bug fixes.
Mandatory Update ⚠️
Key Dates
- Pacaya Fork: Estimated for Mar 29th, 2025, at block height 1,299,888. The exact time may vary due to block time variability.
Required Software Versions
The versions listed below are the minimum required for the Pacaya upgrade. Please note that newer versions may be released, and it's advised to stay updated.
- Taiko BCR Protocol v2.2.0 — If using a ProverSet for block proposals, update to the new implementation.
- taiko-geth v1.14.1
- taiko-client v1.4.1
- simple-taiko-node v1.13.1
- raiko v1.6.0
Failure to upgrade may lead to network disconnection or operational issues.
Details
Bug Fixes
v1.13.0
1.13.0 (2025-03-27) is a hotfix release for the Hekla testnet, with support for the upcoming Pacaya fork, as well as optimizations and bug fixes.
Mandatory Update ⚠️
Key Dates
- Pacaya Fork: Estimated for Mar 28th, 2025, at block height 1,299,888. The exact time may vary due to block time variability.
Required Software Versions
The versions listed below are the minimum required for the Pacaya upgrade. Please note that newer versions may be released, and it's advised to stay updated.
- Taiko BCR Protocol v2.2.0 — If using a ProverSet for block proposals, update to the new implementation.
- taiko-geth v1.14.1
- taiko-client v1.4.0
- simple-taiko-node v1.13.0
- raiko v1.6.0
Failure to upgrade may lead to network disconnection or operational issues.
Details
Features
v1.12.0
1.12.0 (2025-03-24) is a release for the Hekla testnet, with support for the upcoming Pacaya fork, as well as optimizations and bug fixes.
Mandatory Update ⚠️
Key Dates
- Pacaya Fork: Estimated for Mar 28th, 2025, at block height 1,299,888. The exact time may vary due to block time variability.
Required Software Versions
The versions listed below are the minimum required for the Pacaya upgrade. Please note that newer versions may be released, and it's advised to stay updated.
- Taiko BCR Protocol v2.2.0 — If using a ProverSet for block proposals, update to the new implementation.
- taiko-geth v1.14.1
- taiko-client v1.3.2
- simple-taiko-node v1.12.0
- raiko v1.6.0
Failure to upgrade may lead to network disconnection or operational issues.