Skip to content

Latest commit

 

History

History
87 lines (78 loc) · 3.39 KB

marbles_demo_notes.md

File metadata and controls

87 lines (78 loc) · 3.39 KB
Raw

Marbles Demo Notes

Doc Links

Demo Part 1 Goals

  • User can create a marble and store it in the chaincode state
  • User can read all marbles in the chaincode state
  • User can transfer marble to another user
  • See block stats
  • User can delete a marble
  • Deployable on bluemix

Demo Part 2 Goals

  • Server pushes block/marble updates to client when a new block event has occured (polling based)
  • User's can advertise to trade/exchange their marbles (ie willing to trade large red for large blue/yellow/green)
  • User can remove their open trades
  • User identity (fake login as user1 or user2)
  • Ability to see past blocks details and some sort of animation on new blocks

Demo Part 3 Goals

  • User can see more block stats
  • Server pushes block/marble updates to client when any new block event has occured (push based)
  • User autentication (crypto signing of transactions)
  • All operations prove ownership ^^ before exe
  • User registration
  • Drop down on leroy's panel to switch to any user (just a view)

Demo Part 4 Goals

  • Transaction privacy

ToDos:

  • Write("name", "val", cb);
  • ReadNames(cb)
  • init_marble(json);
  • check permissions of requesting user in cc
  • verify user identity, ie public private key stuff
  • website to test cc, real basic
  • demo app website
  • make sdk proper npm module
  • custom custom function on UI
  • load json in UI
  • structured error reponse
  • mocha test for sdk
  • browsify sdk and tie cci into it (not sure if i want to)
  • change downloading zip to git clone
  • the regex to find golang functions needs improving, has false positives
  • follow redirect on zip download
  • auto deploy, correctly!
  • get delete to update marbleIndex
  • sdk, check inputs on load if they dne, error
  • [o] poll after chain deploy for cc up in peer [can't, future auth will prevent]
  • add block stats to sdk
  • write tutorial on part 1
  • change test var "a" to "abc" in cc
  • make advanced link in cci and hide ip/port fields, hide all things under tool like categories
  • make CCI work for multiple apps, pick which cc to load (even custom functions)
  • block history UI
  • CCI video
  • CCI screens with filled out info
  • restyle marbles to match new design
  • multi marble on willing list
  • marble quanity in trade
  • remove/edit trades that are no longer possible in CC
  • check requirments of trade before exe, in CC
  • error checking on arguements before invoking... do not let e blank named marble in (in CC)
  • url routing mapper
  • improve marble redraw so we don't have to blank the marble divs
  • tutorial for p2
  • re-parallelize the queryies
  • show open trades made by user
  • ability to remove open trades by user
  • make layout adaptive
  • better error messages
  • rename to jerry and ginni
  • point out that there is individual chaincode for part 1 and part2 in the tutorial
  • delete the temp dir if no deploy_name in sdk
  • add check transID in sdk, like monitor_height
  • redesign CCI
  • move cci into its own repo, uses the SDK