8000 GitHub - IBM-Blockchain-Archive/marbles at v2.0
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

WARNING: This repository is no longer maintained ⚠️ This repository will not be updated. The repository will be kept available in read-only mode.

License

Notifications You must be signed in to change notification settings

IBM-Blockchain-Archive/marbles

 
 

Repository files navigation

Marbles Demo

Versions and Supported Platforms

Please note there are multiple version of marbles. One marbles branch for each major Hyperledger Fabric release. Pick a version of marbles that is compatible with your version of Fabric. If you don't have any version of Fabric, then pick the marbles version marked latest!

  • Marbles - Branch v4.0 (Latest)

    • Works with Hyperledger Fabric v1.0.1, v1.0.0 and v1.0.0-rc1
    • Works with the IBM Blockchain Bluemix Service - Plan IBM Blockchain Platform - Enterprise
  • Marbles - Branch v3.0 (Deprecated)

    • Works with Hyperledger Fabric v1.0.0-alpha
    • No longer supported by the IBM Blockchain Bluemix service
  • Marbles - Branch v2.0 (Deprecated) (You are viewing this branch!)

    • Works with Hyperledger Fabric v0.6.1-preview
    • Works with IBM Blockchain Bluemix Service - Plan Starter or HSBN
  • Marbles - Branch v1.0 (Deprecated)

    • Works with Hyperledger Fabric v0.5-developer-preview
    • No longer supported by the IBM Blockchain Bluemix service

Application Background

Hold on to your hats everyone, this application is going to demonstrate transferring marbles between two users leveraging IBM Blockchain. We are going to do this in Node.js and a bit of GoLang. The backend of this application will be the GoLang code running in our blockchain network. The chaincode itself will create a marble by storing it to the chaincode state. The chaincode itself is able to store data as a string in a key/value pair setup. Thus we will stringify JSON objects to store more complex structures.

Attributes of a marble:

1. name (unique string, will be used as key)
1. color (string, css color names)
1. size (int, size in mm)
1. user (string)

We are going to create a Web UI that can set these values and pass them to the chaincode. Interacting with the chaincode is done with a HTTP REST call to a peer on the network. The ibc-js SDK will abstract the details of the REST calls away. This allow us to use dot notation to call our GoLang functions (such as chaincode.init_marble(args)).

Start the tutorials below to have your own marbles blockchain demo!

Tutorial / Documentation

  • Looking for chaincode documentation? Check out the learn chaincode repo - start here!
  • Tutorial for Marbles Part 1
  • Tutorial for Marbles Part 2
  • Documentation for IBM Blockchain IBC-JS SDK (our REST based SDK)

Projects Contents

If you run marbles on local host you will have these two urls:

  1. Marbles Part 1 - http://localhost:3000/p1
  2. Marbles Part 2 - http://localhost:3000/p2

Privacy Notice

This web application includes code to track deployments to IBM Bluemix and other Cloud Foundry platforms. The following information is sent to a Deployment Tracker service on each deployment:

  • Application Name (application_name)
  • Space ID (space_id)
  • Application Version (application_version)
  • Application URIs (application_uris)

This data is used by IBM to track metrics around deployments of sample applications to IBM Bluemix to measure the usefulness of our examples, so that we can continuously improve the content we offer to you. Only deployments of sample applications that include code to ping the Deployment Tracker service will be tracked.

Deployment tracking can be disabled by deleting the 'Deployment Tracking' section in app.js.

About

WARNING: This repository is no longer maintained ⚠️ This repository will not be updated. The repository will be kept available in read-only mode.

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Contributors 28

0