Versions Compared

Old Version 5

changes.mady.by.user Medha Parlikar

Saved on

compared with

New Version Current

changes.mady.by.user Medha Parlikar

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Reference

Document status

Status
colourGreen
titlecomplete

Release status

Status
colourGreen
titlein Dev

Milestones

Start date

 

Release

03  

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

Matthew Iles (Unlicensed)

Everett M (Unlicensed)


Release Overview

Simple Overview

Release 20.12 delivers prioritized bug fixes, networking improvements and more consensus protocol security features.

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

This release will further harden the consensus protocol by detecting dopplegangers on the network, adding enhanced endorsements and fork bomb protection. The protocol will also undergo a security review with Trail of Bits during this time. The protocol will also include finality signatures and gossip these signatures via the gossip protocol.

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. The protocol will also begin to integrate with a custody provider during this release cycle.The team will begin implementing CEP3 with a prototype.

Ecosystem

We will update our documentation for the Blockchain Design at docs.casperlabs.io

We will create a developer portal (uplift of docs.casperlabs.io)

We will create video tutorial content for the following:

  • Deploying a contract & calling it using ERC20 -send tokens to an account.

  • Deploying a contract and then upgrading it. Showing the change in version.

    • Walk through of code to upgrade.

Tickets for this Release

Features

Jira Legacy
serverSystem JIRA
maximumIssues20
columnskey,summary,status,priority
maximumIssues20
jqlQueryproject = FEAT and fixVersion in(20.12) AND ( labels not in ("ecosystem") or labels is EMPTY) ORDER BY priority
serverId74adbfdc-03f9-334e-80a4-d9a3f2a98ccf

Ecosystem Features

Jira Legacy
serverSystem JIRA
maximumIssues20
columnskey,summary,status,prioritymaximumIssues20
jqlQueryproject = FEAT AND issuetype = Epic AND status in (Analyzing, Backlog, Implementing, "In Review", Planning) AND fixVersion = 20.12 AND labels =ecosystem ORDER BY priority
serverId74adbfdc-03f9-334e-80a4-d9a3f2a98ccf

Key Consensus Deliverables

Jira Legacy
serverSystem JIRA
maximumIssues20
columnskey,summary,assignee,status,sprint,prioritymaximumIssues20
jqlQueryIssuetype=story and labels ="consensuscrew" and fixVersion="20.12"
serverId74adbfdc-03f9-334e-80a4-d9a3f2a98ccf

Key Node Deliverables

Jira Legacy
maximumIssues
serverSystem JIRA
maximumIssues1000
columnskey,summary,assignee,status,sprint,priority1000
jqlQueryissuetype !=Epic and project=node-rs and FixVersion=20.12 and labels is empty
serverId74adbfdc-03f9-334e-80a4-d9a3f2a98ccf

Key Contract Runtime Deliverables

Jira Legacy
serverSystem JIRA
maximumIssues1000
columnskey,summary,assignee,status,sprint,prioritymaximumIssues20
jqlQueryproject = ee and fixVersion = 20.12
serverId74adbfdc-03f9-334e-80a4-d9a3f2a98ccf

Ecosystem Product Updates

  • Event Capturing Service, Event Store

  • Javascript SDK

  • Clarity supporting Rust Node

  • Enhancements to Signer

Jira Legacy
maximumIssues
serverSystem JIRA
maximumIssues1000
columnskey,summary,assignee,status,sprint,priority
1000jqlQueryproject = eco and FixVersion = 20.12
serverId74adbfdc-03f9-334e-80a4-d9a3f2a98ccf

SRE

  • Network Health Monitoring

Documentation

  • Updated dApp developer guide for Rust Node

Defects Fixed

Jira Legacy
serverSystem JIRA
maximumIssues20
columnskey,summary,status
maximumIssues1000
jqlQueryissuetype = Bug AND fixVersion= 20.12 ORDER BY status DESC, key ASC
serverId74adbfdc-03f9-334e-80a4-d9a3f2a98ccf

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. http://docs.casperlabs.io

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?