Releases: Cardinal-Cryptography/aleph-node
Releases · Cardinal-Cryptography/aleph-node
Testnet release 10.0
- Several backend db migrations that fix the state of the chain: bumping StorageVersion for pallets Balances, Scheduler, Staking
- Migrating all contracts from V8 to V9 version
- Update to Substrate v0.9.38, which is ink4 compatible
- Setting storage per one byte of contract storage: 4*10^{-5} AZERO per byte
- Increase total memory to 256MB, decrease call stack to 16 and enforce heap pages limit at cli.
- minor improvements to the finalization network
Mainnet hotfix release 8.4
Bumping pallet version for below pallets:
- Staking:
V10
- Scheduler:
V3
- History:
V1
- TransactionPayment:
V2
Testnet hotfix 9.1
Several backend db migrations that fix state of the chain:
- Bumping StorageVersion for pallets TransactionPayment, History, Scheduler, Multisig, Staking. Otherwise no functional changes for those pallets.
- Removing 6 nomination pools that are still on outdated V1 schema.
- Migrating V2 to V3 schema for all nomination pools.
- Migrating all contracts from V7 to V8 version
Testnet release 9.0
- Update of pallet contracts that makes it compatible with Ink! 4.0.beta
- Adjustments of the validator network:
- The legacy back-up network is removed, as it is not necessary anymore.
- The nodes establish now only one connection instead of two.
- Update of AlephBFT to version 0.20, which introduces more efficient unit requests and various other improvements.
- Validator suspension now has an additional effect of “chilling” the validator.
Mainnet release 8.3
- Fix for nomination pools unbonding issue:
- add
pending_rewards
API call to Aleph Runtime
- add
Testnet release 8.3
- Fix for nomination pools unbonding issue:
- add
pending_rewards
API call to Aleph Runtime
- add
Mainnet release 8.2
Release notes:
- a bugfix for a scenario in which finalization proofs (justifications) were not disseminated reliably enough, which caused some validators to think they are on the "main branch" while they were not,
- Stop producing blocks when finalization does not happen
Testnet release 8.2
Release notes:
- a bugfix for a scenario in which finalization proofs (justifications) were not disseminated reliably enough, which caused some validators to think they are on the "main branch" while they were not,
- Produce fewer blocks when finalization does not happen
Mainnet release 8.0
Release notes:
- Add a new mode to the elections subsystem that will allow permissionless elections on mainnet.
- Add automated removal of dead validators from the validators list for a given era. If a validator doesn’t produce blocks when they should and they meet the given threshold, they are removed from the validator list for the next era.
- Rewrite of network layer for the committee establishing consensus and ensuring better stability and performance.
- New layer for compatibility of consensus messages sent in alephbft enabling smoother runtime updates.
- There are improvements to the build process that result in a smaller and faster binary.
- The justifications are now created for all blocks that simplify the logic of several components.
- A new command to the binary for checking its version.
- Incorporated bug fix for the sync protocol.
- CCR basic support
- Fix for justification compatibility
- Try-runtime cli in the node (plus fixes for logging in the substrate)
- Pruning related changes
- Unit saving for crash recovery
- everybody wins - opens committee responsible for establishing consensus for outside validators
- pallet identity - enables human-readable aliases for accounts
- tweaks in substrate network - enable querying the same block multiple times
- compatibility for justifications
- substrate update 9.13 → 9.28
- AlephBFT 0.8.4 → 0.19.1
Release 2022-11-03
What's changed:
- Add a new mode to the elections subsystem that will allow permissionless elections on mainnet.
- Add automated removal of dead validators from the validators list for given era. If a validator doesn’t produce blocks when they should and they meet given threshold, they are removed from the validator list for next era.
- Rewrite of network layer for the committee establishing consensus ensuring better stability and performance.
- New layer for compatibility of consensus messages sent in alephbft enabling smoother runtime updates.
- There are improvements to build process that result it smaller and faster binary.
- The justifications are now created for all blocks that simplifies logic of several components.
- A new command to the binary for checking its version.
- Update substrate to v0.9.28.
- Update alephbft to 0.19.1.