2018 04 28 @ 2pm UTC
- Continue research into Hyperledger architecture
- Encourage others to participate in this project
- Start to contemplate simple proofs of concept
- Last week discussions focussed around replacing the gossip layer in HLF
- Now considering reorienting toward replacing the ordering layer, and leaving the gossip layer as is. (Discussion spurred by mid-week conversation with Leemon)
- Example Multi-organisation architecture discussed
- Each organisation has one CA and one orderer
- CA sends hashes to the ordering service
- Kafka master-slave architecture
- Every organisation has their own Kafka orderer node
- Kafka nodes must be synced
- Hedera will support Cryptocurrency and Solidity smart-contracts from the outset
- Swirlds SDK will not include either of the above
- SDK codebase is common to both platforms. Hedera includes additional services layer
- Create functionality akin to Hyperledger Fabric and/or Corda R3 over Swirlds SDK
- Leverage familiarity and tooling
- Initally focus on enabling ChainCode execution on top of SDK
- Operational deployment of generic smart-contracts
- Encapsulation of Business logic inside an state machine
- Atomic execution of this logic
- Eamonn Hynes - Northern Ireland - Allstate Corporation
- Tim McHale - Hashgraph - Madrid, Spain - Ken’s team
- Alex Males - Romania
- Craig Drabik - TxMQ - DLT - Hyperledger + EXO project
- Raj - ChainStar