SDK for early dApp Developers to use

Description

Overview
The goal for this epic is to provide an SDK based on requirements expressed by engaged dApp devs as of Nov 2018.

Use case description
A developer authors his dApp via some other mechanism and wants to deploy his contract(s) to the blockchain, make calls to the contracts, and get data back from contracts.

The developer can learn with gRPC methods to use and how to use them.

Requirements

  • Developers can determine some unforgeable names generated on chain as part of the deployment.

  • Developers can monitor events related to the unforgeable names

Stretch Goals

  • Developers can deploy the contract and pay for it using the Rholang API to fund contract deployment (short leash deploy) described in

  • Developers can estimate the cost of the deployment.

Requirements for a wallet (separate Epic?)
see also wallet keyword

  • * Developers can generate and use a platform-supported wallet with a public/private key set

  • Developers use this tool via the command line.

  • This application is a separate client from RNode.

  • Developers do not have to install and run RNode to use this tool and deploy to nodes on the platform.

Wish List

  • Developers can specify the binary(s) to deploy.

Needs clarification / motivation

  • Developers can check on the status of their deployment using ID and timestamp.

  • Developers can receive the hash of a block based on the hash of the deploy

Resources
See notes from various meetings, esp Nov 15, below.

Notes from an Oct 14 conversation to plan this work are available.

Status

Assignee

Dan Connolly

Reporter

Medha Parlikar

Components

None

Story Points

None

Labels

None

Sprint

None

Priority

Medium

Epic Name

dApp SDK 0.1
Configure