Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

Reference

Document status

PLANNING

Release status

IN PROGRESS

Related pagesRholang (Interpreter)


Milestones

Start date29 Jan 2018
Sprint9 March 2018
Sprint23 March 2018
Release from development26 March 2018
Membership demo28 March 2018
Release29 March 2018


Development team

Development leadProgram managerProject managerDeveloperDeveloperDeveloperDevOpsPage owner
Kyle ButtMedha Parlikar (Unlicensed)Kelly FosterHenry TillFormer user (Deleted)Joseph DenmanJeremy BuskMedha Parlikar (Unlicensed)


Marketing team

Marketing leadEvangelistContent owner
Lawrence Lerner
Kelly Foster



Release summary

Simple overview

This release integrates the Rholang Interpreter into the RChain Node and creates a Rholang runtime environment in the RChain Node, and introduces an encryption handshake.

Technical overview

This a RChain Node that can run Rholang smart contracts.  The Rholang grammar will be equivalent or better than the grammar released as part of the 0.1 SDK, which was released in January.  Rather than using the C++ Rosette runtime environment (as was in the SDK) to run Rholang smart contracts, this node will use a Rholang Interpreter to achieve the same result.  This node also uses encryption in communications, following industry best practices.


Metric for tracking success

Done when node integrates with the interpreter and executes an encrypted handshake.

What is special about this release?

The RChain architecture uses a key value store as the mechanism to house the machine state (Continuations), and this release is the first demonstration of that architecture.  

Anything special about the encrypted handshake? 

Nothing special about encrypted handshake

Are we doing something differently? If so, why are we doing it this way?

Processes that are waiting for input (for comprehensions) are stored in the storage tier. This architecture lays a foundation for consensus to be formed on the machine state, not just transactions.

Before these features were available, what were developers able to do with RChain?

Developers were able to observe the RChain node connect to other RChain nodes and pull and display metrics on local operation.

After these features launch, what will developers be able (and not able) to do with RChain?

Developers will be able to start an RChain node and use an encrypted handshake when connecting to peers. Developers can also run Rholang smart contracts on RChain nodes and experience how Rholang Smart Contracts express continuations (wait for input)

Developers will not be able to:

  • Use any functionality pertaining to blockchain, incl. history in the storage layer
  • Use the Cryptography library
  • Use any System processes in the storage layer
  • Concurrent processes

Description of release packaging

Release packaging includes:

  • Docker image
  • Debian package
  • RPM package
  • tar.gz file
  • .zip file

Where do developers go to learn more and get started?

Developers can visit developer.rchain.coop to learn more and get started.

Where will bugs be filed?

Developers can report bugs on the RChain JIRA.

Where do developers go for support? What is the SLA? Who is on point?

Developers can post questions to the RChain developer forum: https://forum.rchain.coop. This forum is monitored and developers can expect a response within 24 hours.

What license will this be released under?


Release readiness

#DescriptionNotesIssue created in JIRA?
1Document for the node API what methods are exposed? What do they do? Publish in readme on rchain/node.
CORE-278
2Publish installation instructions to appropriate readme 
CORE-279
3Write tutorial (How to run Rholang contracts, and what to expect)
RHOL-173
4Validation of code completeness in dev branch
RHOL-174
5Cut packages (Deb,RPM, and docker) from dev branch for testing
RHOL-175
6Test installation and execution of all packages on various operating systems (pre-release from development)
OPS-83
7Test installation instructions  (pre-release from development)
OPS-84
8Test get started guide and/or tutorial (pre-release from development)
OPS-85
9Publish release notes
MAR-12
10Deliver demo to CEO and CTO
RHOL-181
11Validation of issue completion (prior to merge to master)
RHOL-182
12Validation of completion of merge to master 
RHOL-183
13Tag packages for release
RHOL-184
14Create listing in Docker store
RHOL-185
15Test installation and execution of all packages on various operating systems
OPS-86
16Deliver demo to RChain Coop membership
RHOL-187
17Write announcement message
MAR-9
18Update developer web site (release info and relevant links)
MAR-10
19Publish announcement message
MAR-11
20


21



JIRA issues in this release

key summary type assignee status resolution sprint
Loading...
Refresh

  • No labels