November 2020 Release Plan
Reference
Document status | COMPLETE |
Release status | in Development |
Milestones
Start date | Oct 5, 2020 |
Release | Nov 5, 2020 |
Stakeholders
@Medha Parlikar | CTO | |
@Mrinal Manohar | CEO |
Development team
Program manager | Project Manager | Engineering Lead | SRE |
@Medha Parlikar | @Piotr Dziubecki | @Ed Hastings (Deactivated) | @Former user (Deleted) |
Marketing team
Marketing lead | Content owner |
|
|
Release Overview
Simple Overview
Release 20.11 delivers Transaction Fees, additional consensus security, ability for the new nodes to join the network using trusted hash from current era and prioritized bug fixes.
This network will support up to 100 validator slots in the bonding auction. Validators can bid for open slots by using the bidding API.
Detailed Overview
With this release the network will award transaction fees to the block proposer for processing transactions. The fees will be distributed to wallet of the block proposer as part of the block. The network will support an adaptive round length, which supports validators with varying bandwidth allocations to participate in consensus. Node will adjust the round length adjusts based upon the ability to finalize a block in the round. A minimum value will be specified for the round exponent. The protocol demonstrates resistance to spam attacks and replay attacks.
This release will improve networking by providing a robust node discovery and gossiping protocol to support message passing and node discovery for the Casper network.
A new validator can join the network securely using trusted hash from the current era. The new node only has to replay the deploys to build up their internal global state, and does not need to replay the protocol state for the linear blockchain, because the blocks have finality signatures.
The network will be resistant to deploy replay attacks and to being spammed by deploy, and there is a limit to the number of deploys that can be put into a block. This limit is configurable and depends on the block gas limit. For now this limit can be configured in the chainspec, in future, the validators should be able to adjust this block gas limit.
Users that pay for transactions are able to get a receipt proving that they did indeed pay for the transaction, which includes the cost for the transaction and the accounts involved.
Prospective dApp developers who want to get started with Casper can deploy a contract within 30 minutes from start to finish. They can do this by using an example contract, making some small adjustments, and then deploying this contract to the testnet, and querying a data service for the effects of their execution. All of this is possible with the new Rust network.
A block explorer with ‘Faucet’, in browser token transfers and ‘Deploy from browser functionality will support the network. An 'Event Store’ will be provide that consumes event stream and supports various queries. SRE will have necessary metric to monitor network as well as node health.
Key Consensus Deliverables
Key Node Deliverables
Key Contract Runtime Deliverables
Ecosystem Product Updates
Event Capturing Service, Event Store
Clarity supporting Rust Node
Enhancements to Signer
SRE
Network Health Monitoring
Documentation
Updated dApp developer guide for Rust Node
Metric for tracking the success:
What is special about this release?
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