2018 04 21 @ 2pm UTC

Actions

• research and explore Hyperledger and hashgraph landscape
• reach out to folks who might be interested in this
• prioritise features to be implemented
• ideate a proposed architecture
• once we're orientated towards a vision for the future, how can we eat through this work in an efficient, effective way (i.e. Agile)

Discussion

Hyperledger Features

• Smart Contract Modelling - ChainCode
• DB Layer - CouchDB & LevelDB
• DevOps SDK - Composer CLI
• Expose DLT interface to UI layer - composer command line, REST API server
• CA + MSP = Org specific Certificate Authorities + Membership Service Provider
• Ledger Sync = Gossip about Gossip
• Consensus Algorithm runtime = Kafka / PBFT
• Permission / ACL = Part of modeling language
• Channels = Multiple DLT/Blockchains per Org/node
• Query = SQL style queries for NO-SQL DB
• Cross organization automation = Business Process Management product from IBM
• Smart Contract/Chaincode Natural Language Processing Rules Engine = Operational Decision Management tooling from IBM - Autogenerate Chaincode and DevOps Automation of ChainCode
• Language support = GOLANG, JAVA, nodeJS, Python
• AI/WATSON plugin

Priorities

• Chaincode https://github.com/hyperledger/fabric/tree/release-1.1/core/chaincode
• What dependencies does chaincode have?
• What does the API (Swirlds App) look like?
• DevOps?

Participants

• Eamonn Hynes - Northern Ireland - Allstate Corporation
• Tim McHale - Swirlds - Madrid, Spain - Ken’s team
• Alex Males - Romania -
• Craig Drabik - TxMQ - DLT - Hyperledger
• Chuck Fried - TxMQ
• Ken Anderson - Swirlds - Tools
• Raj - ChainStar