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

Compare with Current View Page History

« Previous Version 14 Next »

This working group was formed to promote the interoperability of Hyperledger Fabric network services. The primary goal of this working group is to ensure Fabric services provided by different vendors can work with each other with the following specific requirements:

  1. Peers from a new organization can join a running fabric network, that is, a peer from a new organization can eventually participate in an existing channel to receive and respond Fabric blockchain transaction requests
  2. A client application can perform Fabric SDK provided API calls against any of the peers and orderers to perform the following Fabric operations:
    1. Channel create
    2. Channel join
    3. Chaincode install (in golang or nodejs)
    4. Chaincode instantiate
    5. Chaincode invoke/query


To test the compliance of each service from a vendor, an new or existing orderering service shall be used. The orderering services should at least satisfy the following requirements:

  1. Kafka based orderering service
  2. TLS on


Working Group Meetings: Working group meet on every Thursday at 9:00am US EST. Here are the meeting info.

Join from PC, Mac, Linux, iOS or Android: https://zoom.us/my/hyperledger.community.backup

Or iPhone one-tap :
US: +16699006833,,6223336701# or +16465588656,,6223336701#
Or Telephone:
Dial(for higher quality, dial a number based on your current location):
US: +1 669 900 6833 or +1 646 558 8656 or +1 877 369 0926 (Toll Free) or +1 855 880 1246 (Toll Free)
Meeting ID: 622-333-6701
International numbers available: https://zoom.us/zoomconference?m=BYDz1WGXJTTJ_s4_zumD9hqKjJv-Whgs

Working Group Meeting minutes: (Section to be updated once meeting minutes become available)


2019-01-10

Agenda

  1. Welcome
  2. State, discuss and confirm the purpose of the working group
  3. Finding people to record meeting minutes for each meeting?
  4. Do we need a Rocket.chat channel for this working group?
  5. General process of adding a new org to an existing network (Contributed by Murali, thanks Murali)

    1. relevant orgs agree to add the Org

    2. create the config updates

    3. collect signatures on the config updates to satisfy the policy

    4. submit the updates

  6. Proposals discussion on how to do new org join channel, key problems
    1. how to pass around these signatures?
    2. who should receive signature request and how?
    3. who (the new org or one of the admins in the channel) eventually make channel updates?
  7. What tool do we want to use to do all the work?


Proposals:

  1. SAP (Brian McKellar)
  2. Leizu (Kai Chen)
  3. A special channel (Tong Li)


  • No labels