March 2020 Release Description
Reference
Document status | COMPLETE |
Release status | RELEASE |
Related pages |
Milestones
Start date |
|
Sprint 30 (2 weeks) |
|
| Sprint 29 (2 weeks) | |
Release |
|
Stakeholders
Name | Role | Reviewed? |
| Medha Parlikar | CTO | |
| Mrinal Manohar | CEO |
Development team
Program manager | Project Manager | Developer | Developer | Developer | SRE |
| Ashok Ranadive (Unlicensed) | Piotr Dziubecki | Michael Birch | Akosh Farkas | Henry Till | Tom Vasile |
Marketing team
Marketing lead | Content owner |
| Kevin Watt | Former user (Deleted) |
Release Overview
Simple Overview
With this release we complete the functionality required for Alpha TestNet- a working version of the Highway Protocol with honest validators. We will be preparing for our TestNet launch with 10 Validators.
Detailed Overview
Execution Engine Enhancements
- Performance enhancements via 'turbo' mode
Support multiple Key Lengths for accounts- Documentation for AssemblyScript library.
Consensus & Node Features
- Eras, Leaders, Efficient Fork Choice and fixed Rounds
- Configurable Highway parameters
- Era switch blocks, ballots and a revised Genesis process
EcoSystem:
AssemblyScript examples- Getting started with AssemblyScript
- dApp Tutorials
- dApp Developer guide
- Deploy contracts from the browser to the network.
Test & Operations:
- Infrastructure for TestNet Launch
- Performance testing and tuning of protocol
- STESTS testing platform for scalable Production Engineering
Metric for tracking the success:
What is special about this release?
This release completes the initial production implementation of The Highway protocol, and will support the launch of the Alpha TestNet launch of the CasperLabs blockchain protocol.
For dApp Developers
For Node Operators
Are we doing something differently? If so, why are we doing it this way?
Before these features were available, what were developers able to do?
After these features launch, what will developers be able (and not able) to do?
Description of release packaging
Release packaging will include:
- Debian package
- Docker image
- Brew packages
- RPM package
- tar.gz file
Where do developers go to learn more and get started?
- At release, links to installation packages and relevant documentation is available at
- Packages available at: http://github.com/CasperLabs/releases
- Docs available on GitHub.
Where will bugs be filed?
Github - part of the public release.
Where do developers go for support? What is the SLA? Who is on point?
Gitter developer channel