Aleph Zero Blog
Progress

Mainnet 12.2 is out. Staking UX improvements, faster block sync

Jan 25, 2024

AI Summary

Here's your AI summary of Mainnet 12.2 is out. Staking UX improvements, faster block sync on Aleph Zero blog

Top 10 key takeaways:

  1. Mainnet 12.2 Release: The new update has been rolled out, bringing significant changes and improvements.

  2. Contracts Pallet and Block Sync Enhancements: Performance improvements have been made to the contracts pallet and internal block synchronization request mechanism.

  3. Staking Process Revamp: The staking process has been updated to eliminate the use of separate controller accounts for new users. A single account will now serve as both stash and controller.

  4. Current Users Unaffected: Existing users with controller accounts can continue using them without any changes.

  5. Proxy Pallet Introduction: The update sets the stage for the upcoming proxy pallet, which will streamline staking processes like bonding and unbonding, even when the stash account is offline.

  6. Staking Dashboard Access: The Staking Dashboard is now accessible at dashboard.alephzero.org, replacing the previous address dashboard.azero.dev.

  7. Breaking Changes: Several breaking changes include:

    • Default RPC port for HTTP is now 9944 instead of 9933.
    • Staking->bond and Staking->set_controller extrinsics no longer accept the controller argument.
  8. Mainnet Validators Update: Validators are urged to download and upgrade to Aleph Node 12.2 as soon as possible, following the new update procedure detailed in the Release Notes.

  9. Detailed Changelog: For more comprehensive details, users are directed to the Release Notes.

  10. Support and Feedback: The team is available on Discord and Telegram for any questions or concerns, emphasizing the importance of user feedback.

AI Summary

Mainnet 12.2 sets the stage for a major update to controller and stash accounts, as well as brings updates to contracts pallet and block sync. Here’s all you need to know!

We’re happy to inform you that the Mainnet 12.2 has been rolled out. Here are all the changes of this release and what’s ahead in the next steps!

Updates to Contracts Pallet and Block Synchronization:

We’ve enhanced the contracts pallet and internal block synchronization request mechanism, aiming for improved performance.

Revamp of Staking Process for Stash and Controller:

A key advancement has been made in the staking process. Going forward, if you choose to stake your AZERO, you won’t have the option to use a separate controller account. A single account will now function as both stash and controller.

Note for Current Users: If you’re already using a controller account, there’s no change for you – you can continue as usual. This change applies only to new users, who won’t have the option to create new controller accounts. This change is already live on the Mainnet.

This modification is setting the stage for the introduction of the proxy pallet, which is expected to be part of the releases following 12.2.

The Mainnet 12.2 update will bring in proxy accounts, streamlining staking processes like bonding and unbonding. These actions can be performed even when the stash account is not online, simplifying the overall staking experience.

Among the other improvements, you can now access the Staking Dashboard by going to dashboard.alephzero.org – previously, the address had been dashboard.azero.dev.

Breaking changes

There are several breaking changes in Mainnet 12.2. If you’ve been using those API functions, make sure you adapt to the new methods.

  • The default port for RPC over HTTP is no longer 9933. The default RPC port (for both WS and HTTP) is now 9944
  • Staking->bond extrinsic no longer accepts controller argument
  • Staking->set_controller extrinsic no longer accepts controller argument

For a more detailed Changelog, head over to the Release Notes.

Mainnet Validators – update your nodes!

Mainnet validators can now download Aleph Node 12.2 and upgrade their nodes–we ask all of you to perform the update at your earliest convenience.

NOTE! Due to the recent rework of aleph-node-runner, the update procedure this time is different than usual. To update your node to the recent version, please follow the instructions at the end of Release Notes.

Have questions?

We are always available, both on Discord and Telegram, to assist with any questions or concerns you might have. Your feedback and questions are vital to us; please don’t hesitate to connect!