Spring 1.0 RC1 Released
We are excited to announce that Antelope Spring 1.0 RC1 has been released! Spring 1.0 is a monumental advancement from its predecessor, Antelope Leap 5. This new version not only continues the legacy of innovation but also introduces groundbreaking features designed to set new benchmarks in blockchain performance, security, and community engagement.
Introducing Savanna Consensus: Instant Finality and Beyond
Spring 1.0 introduces Instant Finality through Savanna (Scalable Agreement on Validated Additions with Nimble Nonrepudiating Attestation), a revolutionary new consensus algorithm that mirrors a seamless web2 experience within the web3 space. Drawing inspiration from VMware Research’s HotStuff consensus algorithm, Savanna represents a significant shift in blockchain technology.
It introduces a next-generation consensus mechanism that redefines block-based chains by integrating cutting-edge advancements in distributed systems. This enhances scalability, security, and transaction finality, positioning the EOS Network at the forefront of innovation. By merging aggregate BLS signatures with advanced cryptographic techniques, Savanna dramatically reduces the time to finality and scales efficiently.
Set to revolutionize the EOS Network, Savanna ensures irreversible transactions, and finality in mere seconds, a 100x improvement over previous releases. This advancement boosts network efficiency and elevates the user experience, positioning EOS at the forefront of blockchain development.
Enhanced Privacy and Cryptographic Innovation
Another remarkable aspect of Spring 1.0 is its potential for cryptographic innovation. The introduction of aggregate BLS signatures able to be verified in as little as 1.1ms* lays the groundwork for more abstract cryptographic building blocks, enabling the development of ZK proof systems. This is accomplished through EOS’s own implementation of BLS operations and specialized matrix operations in WebAssembly. These systems promise enhanced privacy features, such as confidential transactions and the use of private addresses, setting new standards in blockchain privacy and security.
*As benchmarked with an I9-13900 CPU.
Enabling Flexible Blockchain Structure with Potential New Roles
Spring 1.0 marks a significant evolution within the EOS ecosystem, introducing the possibility for a transformative reconfiguration of the traditional Block Producer role. This update offers the EOS community the option to split Block Producer responsibilities into two distinct functions: Block Proposers and Block Finalizers.
This change does not automatically take effect with Spring 1.0 but provides the community with the flexibility to adopt this new structure, should there be a consensus to do so. The introduction of Block Proposers and Block Finalizers offers a potential pathway towards a more decentralized, secure, and efficiently governed network.
- Block Proposers – tasked with organizing transactions into proposed blocks and coordinating with Block Finalizers to generate Quorum Certificates. These certificates serve as definitive proof that a proposed block has been finalized.
- Block Finalizers – concentrate on endorsing block proposals by sending their signatures to the Block Proposer for the creation of Quorum Certificates. This division of responsibilities aims to enhance the network’s security and efficiency by providing a robust mechanism for block validation and finalization.
In Spring 1.0, block proposing and finalizing are distinct responsibilities. This separation enhances the EOS blockchain’s safety and liveness, making the network more predictable and easier to manage. It also facilitates inter-blockchain communication and allows third parties to monitor the network’s health without needing to participate in transaction creation.
Other Notable Changes
Also featured in Spring 1.0 is a significant reworking of the State History Plugin to improve performance, reliability, and support cross chain consensus leveraging the faster finality of Savanna.
A subset of the changes in this release may require node operators and downstream service providers to make configuration changes. At a glance, these include:
- Changes to some HTTP response codes
- Introduced new Snapshot format
- Disabled State Log History compression
- Introduced new State History configuration options
- Introduced new Finalizer configuration options
- Introduced new vote-threads option
Contributors
Special thanks to the contributors that submitted patches for this release.
@linh2931
@spoonincode
@systemzax
@heifner
@wanderingbort
@greg7mdp
@ericpassmore
New License Terms
Antelope Spring is made available under the terms of a Business Source License (BSL) which is automatically granted for all usages which are Directly in Service of or Materially Dependent on the EOS Blockchain Network. Full details of the license terms may be found in the LICENSE file. Parties seeking a License for other usages may inquire by contacting licensing@eosnetwork.com.
NOTE: To maintain IBC compatibility with EOS after it transitions to Savanna consensus, other Antelope chains will need to upgrade to a Savanna compatible IBC contract which depends on the activation of the BLS protocol feature that was first introduced in Leap 5.0.
Important Links for Node Operators
- Instructions to upgrade a node to Spring 1.0.0
- Instructions to transition a network to Savanna Consensus
- Recommendations for managing finalizer keys
Important Dates
Collaboration and readiness for all ecosystem participants is crucial as we gear up for the upcoming Spring 1.0 upgrade. Reflecting on our journey since the last major consensus upgrade with Antelope Leap 3.1, we recognize the importance of a unified effort across the ecosystem for a smooth transition.
Infrastructure providers and technical partners should note these key dates for the Spring 1.0 hard fork:
- Stable Release: September 4, 2024
- Recommended Upgrade Period: September 5-24, 2024
- Hard Fork: September 25, 2024*
*Process will begin at 14:00 UTC
All node operators must prepare for the upcoming hard fork to continue participating in the EOS Network. Please note that not upgrading your node infrastructure to Spring 1.0 will result in falling out of sync from the EOS Network on September 25.
Stay Informed
Block producers and node operators can stay informed on by joining the dedicated EOS Upgrade Support Telegram group and the Antelope Node Operators Round Table Telegram group.
Spring 1.0 upgrade Zoom calls for node operators are also hosted by the EOS Network Foundation product team every Wednesday at 9a EDT / 1p UTC where planning and coordination discussions around the Spring 1.0 hard fork take place. You can join these calls at the following link.
