Releases: taikoxyz/simple-taiko-node
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.
Details
Features
v1.11.0
1.11.0 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.1
- simple-taiko-node v1.11.0
- raiko v1.6.0
Failure to upgrade may lead to network disconnection or operational issues.
Details
Features
- hekla: bump client tags (#373) (451dab3)
- hekla: update tags for Hekla (#371) (f2a4af7)
- repo: update Hekla image tags for Pacaya fork (#369) (0f1e3b1)
Chores
v1.10.3
v1.10.2
v1.10.1
v1.9.1
v1.9.0
Summary
1.9.0 (2025-01-20) is a pre-release for the Hekla testnet, with support for the upcoming protocol fork, as well as optimizations and bug fixes.
Major Updates:
- Supported revert protection to protect proposers' profit. (Need your PBS service support revert protection and upgrade the
ProverSet) - Introduced the fallback mechanism, proposer will use calldata as DA when blob fee is more expensive than using calldata when enabled the
l1.fallbackToCalldata. - Reduced the
provingWindow. - Introduced proof aggregation, provers can accumulate a certain number of proofs and submit them in batches to save gas costs.
- Breaking change in ABI encoding due to contract upgrade
⚠️ .
Command-Line Flags
New Flags
-
--l1.fallbackToCalldata: Optional config. If set to true, the proposer will use calldata as DA when the blob fee is more expensive than using calldata. -
--l1.revertProtection: Optional config. Enable revert protection within your ProverSet contract, this is effective only if your PBS service supports revert protection. -
--prover.sgx.batchSize: Optional config. The default size of batch sgx proofs, when it arrives, submit a batch of proof immediately, when the value is larger than 1, it means enabling the proof aggregation. -
--prover.forceBatchProvingInterval: Optional config. Time interval to prove blocks, even if the number of pending proofs does not exceed the batchSize, this flag only works when the proof aggregation is enabled.
Removed Flags
--prover.capacity: Please ensure this flag is removed from your configuration file.--extraData: Optional, if you used this flag before, it won't work after the upgrade.--prover.minEthBalance: Optional, if you used this flag before, it won't work after the upgrade.--prover.minTaikoTokenBalance: Optional, if you used this flag before, it won't work after the upgrade.--prover.blockSlippage: Optional, if you used this flag before, it won't work after the upgrade.--prover.maxProposedIn: Optional, if you used this flag before, it won't work after the upgrade.
Mandatory Update ⚠️
Key Dates
- Protocol Upgrade: Feb 1st, 2025, 2:00 AM UTC (10:00 AM Singapore) — Ensure your software is updated before this time.
Required Software Versions
The versions listed below are the minimum required for the fork upgrade. Please note that newer versions may be released, and it's advised to stay updated.
- Taiko BCR Protocol v1.11.0 — If using a ProverSet for block proposals, update to the new implementation.
- taiko-geth v1.11.1
- taiko-alethia-client v0.43.1
- simple-taiko-node v1.9.0
Failure to upgrade may lead to network disconnection or operational issues. You can revert to previous versions before the fork if necessary, as no database schema changes are involved. This pre-release applies only to the Hekla testnet and is not for mainnet use.