Aleph Zero Testnet Update: Smart Contracts are Live on the Testnet
Today, the Aleph Zero Testnet has been successfully upgraded with several important features, including smart contracts, identity pallets, and the ability to establish the consensus via outside validators.
As per last week’s announcement, we are now excited to announce that the smart contracts are live on the Aleph Zero Testnet. The Substrate stack has been upgraded from version 9.13 to 9.23, and the Aleph Zero consensus, AlephBFT, has been updated from version 0.8.4 to 0.12. Here’s what it means in practice.
Smart contracts on the testnet
To start, you will need to prepare your computer for development in Rust and ink!—similarly to how you might’ve already operated with the Smartnet. ink! is an embedded domain-specific language (eDSL) for writing smart contracts in Rust which then compiles to Wasm code. Thanks to years of work by the Parity team, ink! is definitely mature enough to release interesting applications—albeit it won’t be as smooth of an experience as you might expect. The community should, however, expect significant improvements over time as the developments are occurring on several fronts and multiple teams are involved in the process.
The goals for the Testnet release are similar to the ones for the Smartnet—although we put more emphasis on the stability and reliability of the smart contract layer. While the Smartnet release was aimed primarily at having the smart contracts in a separate environment and chaos was actually expected, the Testnet release aims to be more stable and fit into our overall deployment pipeline.
As the smart contracts have been pushed to the testnet, the Smartnet will now be disabled.
Aleph Zero community validators
Today’s update also takes care of the needs of Aleph Zero’s community validators as it opens the committee responsible for establishing the consensus for external nodes.
The committee rotation mechanism is also live. For each epoch, a large validator pool is fixed, and then a different committee is chosen for every session. A session lasts 900 blocks (15 minutes) and an era lasts 96 sessions (24 hours) ensuring frequent rotation of the committee. All the validators from the pool that has been fixed for a given era will be rewarded proportionally to their stake.
Aleph Zero identity
Adding the identity pallet to the Aleph Zero network will allow for human-readable aliases for accounts. In practice, it would allow for the validators to be named accordingly to their desires (Awesome_Validator instead of 5XXX_XXX), improving the overall user experience of the network.
We’re beyond excited to bring this important testnet update to you. Expect the changes to go live on the Aleph Zero Mainnet within the following weeks.
On-chain privacy, confidential data, and compliance in Web3
What does “compliant privacy” mean? Can privacy by itself be non-compliant? How can Web3 ensure that users’ rights are protected, and at the same time, proactively limit the amount of bad actors in the ecosystem? First things first: by definition, privacy is not non-compliant. It’s generally recognized as a fundamental human right in many parts
DAGs Are Driving the Future of Blockchain Speed
As we’ve seen, the quest for the fastest blockchain is currently being won by an array of new approaches to scalability. This race is going on because blockchain speed is becoming more and more important to the viability of end-user applications in web3. We also saw that the speed of a main chain is still
Understanding TPS: A Key Measure of Blockchain Speed
We’ve talked about how important blockchain scalability is to all sorts of compliance and privacy solutions. However, we also need to understand what having this scalability means and what it looks like in a blockchain network’s operations. There are many ways to measure the speed of a blockchain network. The most popular of these is