Releases: etclabscore/go-ethereum
Geth Classic v6.1.2-stable
IMPORTANT: Classic Geth is a relic from 2016 and will only be kept compatible with upcoming hardforks to ease the migration paths for old infrastructure and services. Classic Geth, however, will reach END OF LIFE on January 15th, 2020. The Agharta hardfork will be the last hardfork supported by Classic Geth. The v6.1.x versions will be the last release track ever for Classic Geth. Subsequently, in 2020, Classic Geth will ultimately only receive consensus critical patches if necessary. There will be no further bug fixes or improvements released. The Aztlán hardfork in March 2020 will not be supported. As of today, it is no longer recommended to run Classic Geth in production. Please, consider migrating your infrastructure to one of the following clients:
- Parity Ethereum https://github.com/paritytech/parity-ethereum/releases
- Multi-Geth https://github.com/etclabscore/multi-geth/releases
- Multi-Geth https://github.com/multi-geth/multi-geth/releases
- Hyperledger Besu https://github.com/hyperledger/besu/releases
RELEASE NOTES: This 6.1.2-stable release is enabled with Agharta protocol features as per ECIP-1056 and will activate the hardfork on Ethereum Classic mainnet block 9_573_000.
Please, use at own risk -- for research and development purposes only. Geth Classic will no longer provide binaries. Please, consider migrating your infrastructure to Parity Ethereum, Multi-Geth, or Hyperledger Besu.
The full list of introduced changes since 6.1.1-beta:
- core/config: activate agharta on mainnet 9573000 (#71)
Geth Classic v6.1.1-beta
IMPORTANT: Classic Geth is a relict from 2016 and will only be kept compatible with upcoming hardforks to ease the migration paths for old infrastructure and services. Classic Geth, however, will reach END OF LIFE on January 15th, 2020. The Agharta hardfork will be the last hardfork supported by Classic Geth. The v6.1.x versions will be the last release track ever for Classic Geth. Subsequently, in 2020, Classic Geth will ultimately only receive consensus critical patches if necessary. There will be no further bug fixes or improvements released. The Aztlán hardfork in March 2020 will not be supported. As of today, it is no longer recommended to run Classic Geth in production. Please, consider migrating your infrastructure to one of the following clients:
- Parity Ethereum https://github.com/paritytech/parity-ethereum/releases
- Multi-Geth https://github.com/multi-geth/multi-geth/releases
- Hyperledger Besu https://github.com/hyperledger/besu/releases
RELEASE NOTES: This 6.1.1-beta release is enabled with Agharta protocol features as per ECIP-1056. It will allow for core developers and community members to start testing a potential protocol upgrade by manually enabling EIPs 145, 1014, and 1052. This release enables the following hardforks:
- Mordor Agharta Hardfork Block
301_243:geth --chain mordor - Morden Agharta Hardfork Block
5_000_381:geth --chain morden
This release is considered as beta and still requires testing. Please, use at own risk -- for research and development purposes only. Geth Classic will no longer provide binaries. Please, consider migrating your infrastructure to Parity Ethereum, Multi-Geth, or Hyperledger Besu.
The full list of introduced changes since 6.1.0-alpha:
Geth Classic v6.1.0-alpha "Agharta"
IMPORTANT: Classic Geth is a relict from 2016 and will only be kept compatible with upcoming hardforks to ease the migration paths for old infrastructure and services. Classic Geth, however, will reach END OF LIFE on January 15th, 2020. The Agharta hardfork will be the last hardfork supported by Classic Geth. The v6.1.x versions will be the last release track ever for Classic Geth. Subsequently, in 2020, Classic Geth will ultimately only receive consensus critical patches if necessary. There will be no further bug fixes or improvements released. The Aztlán hardfork in March 2020 will not be supported. As of today, it is no longer recommended to run Classic Geth in production. Please, consider migrating your infrastructure to one of the following clients:
- Parity Ethereum https://github.com/paritytech/parity-ethereum/releases
- Multi-Geth https://github.com/multi-geth/multi-geth/releases
- Hyperledger Besu https://github.com/hyperledger/besu/releases
RELEASE NOTES: This 6.1.0-alpha pre-release is enabled with Agharta protocol features as per ECIP-1056. It will allow for core developers and community members to start testing a potential protocol upgrade by manually enabling EIPs 145, 1014, and 1052.
This release is considered as unstable and still requires a lot of testing. Please, use at own risk -- for research and development purposes only. No binaries will be provided until the releases are considered stable.
The full list of introduced changes since 6.0.10-stable:
Geth Classic v6.0.10-stable
Geth Classic v6.0.10-stable is a bug-fix release that improves performance and stability.
The full list of introduced changes since the v6.0.8-stable release:
Geth Classic v6.0.9-Stable Hot-Fix
Geth Classic v6.0.9-Stable Hot-Fix release is a hot fix to v6.0.8-Stable Atlantis, which updates the default bootnode list with active peers.
This release includes the following updates:
- Updated default mainnet bootnodes (#45)
Geth Classic v6.0.8-stable
Geth Classic v6.0.8-stable is a bug-fix release that improves performance and stability. Among others, it fixes issues with malformed status response codes on certain RPC requests.
Attention: This stable release is the mandatory minimum requirement for any node serving Ethereum Classic, Morden Classic Testnet, Kotti Classic Testnet, the Kensington Classic Testnet, and any other network that plans to implement the Atlantis protocol upgrade. Upgrading as soon as possible is highly recommended.
The full list of introduced changes since the v6.0.7-beta release:
Geth Classic v6.0.7-beta
Geth Classic v6.0.7-beta is a release that fixes a critical consensus-relevant issue dealing with various edge-cases discovered during tests on Morden testnet as part of the Atlantis protocol upgrade and applies EIP-684 as default to all chains to avoid splits.
Upgrading classic Geth nodes is highly recommended and mandatory to avoid chain splits after the Atlantis hardfork which is scheduled to activate in September on the Ethereum Classic main network.
The full list of introduced changes since the v6.0.6-beta release:
Geth Classic v6.0.6-beta
Geth Classic v6.0.6-beta is a release that fixes a critical consensus-relevant issue dealing with zero-nonce accounts as part of the Atlantis protocol upgrade. Upgrading classic Geth nodes is highly recommended and mandatory to avoid chain splits after the Atlantis hardfork which is scheduled to activate in September on the Ethereum Classic main network.
The full list of introduced changes since the v6.0.5-alpha release:
- Docs: badges badges badges badges (eth-classic/go-ethereum#80)
- Core: state-trie clearing fix (eth-classic/go-ethereum#82)