Skip to content
This repository has been archived by the owner on Oct 25, 2021. It is now read-only.

substrate-api-client.md #114

Merged
merged 2 commits into from
Aug 23, 2019
Merged

substrate-api-client.md #114

merged 2 commits into from
Aug 23, 2019

Conversation

brenzi
Copy link
Contributor

@brenzi brenzi commented May 27, 2019

Grant Application

This application is (select one):

  • Speculative (use this by default)
  • an RFP response

This application is (select one):

  • Public (fully)
  • Public with private finances

Abstract

This application is a side-effect of our grant for developing substraTEE. During the implementation of substraTEE we also implemented a Rust websocket client for substrate, released as substrate-api-client. That client is kept very simple and serves its purpose for substaTEE, but at the current state it is more of a code sample than of a production library for general use. Examples show how to query chain state, send transfers and listen to events.

On riot, we realized that there's a heavy interest in the dev community for a substrate client written in Rust.

Features to be added to the existing code base

  • dynamic API, parsing runtime metadata (current API is static)
  • generic type arguments for runtime types like Balances, AccountId aso.
    • the library shall support composing extrinsics to custom runtime modules
  • deploy and call ink contracts
  • support custom structs for runtime

Checklist

  • The grants document has been read and understood.
  • The Google Form will be completed accurately. Note that the Google Form requires the pull request URL.
  • Abstract (above) is succinct and complete.
  • The application is being included into the correct directory: either 'targeted' or 'speculative'.
  • The application includes a project description.
  • The application includes all names of team members.
  • The application includes a description of the team's experience.
  • The application includes all necessary links (e.g. GitHub and LinkedIn)
  • The "Development Roadmap" section in the application has a timeline of development ("milestones").
  • The "Development Roadmap" section in the application has an estimate of funds required.
  • The "Development Roadmap" section gives an indication of the team's long term plans.
  • The "Development Roadmap" section includes documentation as a deliverable for at least one milestone.

@EdwardAThomson EdwardAThomson merged commit 9a7c3dc into w3f:master Aug 23, 2019
# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants