Releases: autonity/autonity
Autonity Mainnet Release (v1.1.2)
Autonity v1.1.1
We are excited to announce the release of Autonity Go Client version 1.1.1, designed to support the Bakerloo Testnet, which mirrors the upcoming Autonity Mainnet. This release introduces critical features and enhancements to ensure compatibility, performance, and stability for validators and developers preparing for the mainnet launch.
We've introduced a clustering model for efficient message routing within the consensus network. While maintaining full mesh connections, nodes are now organized into clusters with designated roles: Originator, First Relayer (Origin/Remote Cluster), and Local Relayer (Origin/Remote Cluster). Combined with BLS signature aggregation, this clustering enables our consensus protocol to scale to 500 validators, processing up to 1,000 transactions per second (TPS) in testing. Further optimizations are planned to boost performance and scalability.
Other additional updates include:
- ASMv2 : The Autonity Stabilization Mechanism has been upgraded to version 2, featuring a new auction mechanism.
- Delegated staking: New functionality to support delegated staking.
- Formal code audit: Issues identified in a formal audit have been resolved, with a report to be published soon.
Stay tuned for a detailed changelog and further information.
Rome (v1.0.2-alpha)
Autonity v1.0.2-alpha "Rome" marks a key milestone, supporting the pre-mainnet testnet "Tiber." Key features include:
- Consensus Omission Accountability: Validators in the epoch consensus committee are expected to actively participate. To encourage this, a portion of epoch rewards is allocated to active participants. Validators failing to meet the participation threshold may face jailing.
- Oracle Outlier Detection and Incentives: The Oracle protocol can now identify and exclude outlier reports from price calculations. Additionally, a portion of epoch rewards is dedicated to incentivizing accurate price reporting, similar to the consensus participation mechanism.
- Auto-Bonding of NTN Rewards: Instead of being claimable, NTN rewards are now automatically re-bonded to their respective validators, enabling an auto-compounding mechanism.
For more detailed informations please check out the Autonity documentation.
Changelog
[1.0.2-alpha] - 09/12/2024
Added
- Liquid Newton Contract's State/Logic separation #1015
- Consensus Omission Accountability #1021
- NTN auto-bonding #1059
- Oracle Accountability #1067
Changed
- BLS aggregator refinements 863d321
- Epoch block header #1022
- Accountability event processing refinements #965
- Consensus pipeline optimization #1033
- Vesting contracts rework #1048
- Restrict opening of CDPs at genesis #1065
- Removal of the
autJSON-RPC namespace #1066
Fixed
v0.14.1
Delhi (v0.14.0)
Autonity v0.14.0 is our latest release with some new features regarding the protocol economics. We're introducing NTN inflation rewards: all stakers are now entitled to inflation NTN tokens dynamically injected in the current supply and this using the same reward claiming circuit as ATN rewards. The inflation of staking token NTN is designed to keep the total supply capped to 100M NTN.
We're introducing as well a new feature for changing a validator enode information (ip and port) and in-protocol unlock contracts which can be in either staked or non-stakeable mode.
Finally, on a more fundamentally technical point, we have completed the switch to BLS signatures with a brand new signature aggregator component that should enable scaling up the consensus committee size.
For more information please look at our updated documentation.
Changelog
[0.14.0] - 10/06/2024
Added
- BLS aggregation 7b999d0
- Valdator enode update #982
- NTN inflation mechanism #979
- Vesting manager contracts #956
- Spammer suspensions #994
Changed
Fixed
Tokyo (v0.13.0)
Autonity v0.13.0 marks a significant milestone in the history of Autonity, introducing several important modifications to the protocol.
- We've thoroughly redesigned our consensus protocol's mechanics at the network level by launching a specialized peer-to-peer network exclusively for the consensus committee: the "Consensus" network. This should boost the performance of the system and reduce mining rate fluctuations during periods of high transaction volume.
- We're initiating the deep integration of BLS signatures starting with an updated validator onboarding process and the replacement of the "nodekey" file with the "autonitykeys" file.
- We've also decoupled our discovery protocol from Ethereum's, aiming for quicker initial synchronization.
- We resolved numerous internal problems. This should substantially minimize slashing incidents, especially when rebooting validator nodes.
- Furthermore, we've introduced a novel governance feature that provides a universal on-chain mechanism for smart contract upgrades, accompanied by a new "jailbound" state for validators.
We highly recommend you to check our documentation for more information.
Changelog
[0.13.0] - 26/02/2024
Added
- Snappy compression devp2p optimization #843
- New Validator Status Jailbound #857
- Consensus key onboarding #858
- Reject bonding to jailed validator #926
- Introducing Autonity Consensus Network, the "ACN" protocol #923 alongside Execution network's topology optimizations.
Changed
- Refactor Consensus messages 6e9781b
- Discovery protocol isolation 315082b
- Committee Selection in precompile #921
Fixed
v0.12.3
This release addresses issues experienced on the Piccadilly testnet, with a key focus on resolving slashing problems during periods of high activity. Additionally, it includes a temporary fix for Prometheus metrics collection. We encourage all validators to deploy this new version. Wishing you a Happy New Year from our team!
Changelog
[0.12.3] - 04/01/2024
Fixed
Changed
- Decrease default gas limit to 20,000,000 #912
Damascus (v0.12.2)
Version 0.12.2 marks a significant milestone in Autonity's evolution, introducing a suite of innovative features designed to kickstart round 4 of the Piccadilly Circus Games. Key highlights of this major release include:
- Introduction of a cutting-edge Byzantine fault detector, a product of extensive R&D, enabling advanced slashing mechanisms.
- Integration of the consensus layer with an Oracle network, offering dApps real-time trusted FX market data feed.
- Introduction of an inventive economic proof-of-stake feature known as "Penalty-Absorbing Stake."
- Enshrined stabilization of our native currency, the Auton, through the implementation of a CDP protocol contract.
For more detailed information, we invite you to consult our meticulously crafted documentation here.
Changelog
[0.12.2] - 01/12/2024
Added
- Byzantine fault detector #273
- Slashing #257
- Oracle protocol integration c35d825
- With protocol refunding mechanism #820
- ASM Protocols contracts
- Advanced consensus metrics #281
Changed
- Improved unbonding #807
Fixed
... and much more
Babylon (v0.10.1)
Autonity is the reference implementation of the Autonity Protocol. The protocol provides an EVM-based blockchain that utilizes Tendermint BFT for delegated proof of stake consensus, has a dual native coin design for tokenomics, and provides liquid staking for capital efficiency. See documentation.
Cartegana (v0.7.1)
The Autonity v0.7.1 contains below 3 corrections:
- Upgrade golang to 1.15.5 to fix the potential panic issue of the upstream (GETH)
See - https://blog.ethereum.org/2020/11/12/geth_security_release - Fix nodejs console issue
See - https://github.com/clearmatics/autonity/issues/728 - Fix the network economic metric exporting issue.