Since permissioned blockchain has been adopted widely in various industries, the need to integrate different permissioned blockchains rises up recently. The two core problems of this case are chain contract interoperability and transaction atomic. Many frameworks and solutions proposed currently are a bit complex. We introduced a lightweight protocol and reference implementation inspired by the ‘ServiceMesh’ pattern in the microservice integration area. Combine with a stateless off-chain relay and an extended on-chain contract development kit as a ‘SideCar’ for different permissioned blockchains. Contract developers can focus on writing business logic since the on-chain contract development kit uses an AOP(aspect-oriented programming) approach to delegate the contract interoperability. In addition it also provides a lock API for locking contract state which can be used in two-phase commit cases. The off-chain relay uses an event based architecture to coordinate different permissioned blockchains. Learning Outcome 1) Implement the on-chain contract development kit for Hyperledger fabric using JAVA. 2) Implement the on-chain contract development kit for Consensys quorum or Hyperledger Besu using Solidity. 3) Implement the off-chain relay plugin for Consensys quorum or Hyperledger Besu.
No project history available for this organization.
Counts are based on projects listed in the Contribo catalog.
Showing 1 of 1 projects. Click any project card for scope, mentors, and proposal studio.
Since permissioned blockchain has been adopted widely in various industries, the need to integrate different permissioned blockchains rises up recently. The two core problems of this case are chain contract interoperability and transaction atomic. Many frameworks and solutions proposed currently are a bit complex. We introduced a lightweight protocol and reference implementation inspired by the ‘ServiceMesh’ pattern in the microservice integration area. Combine with a stateless off-chain relay and an extended on-chain contract development kit as a ‘SideCar’ for different permissioned blockchains. Contract developers can focus on writing business logic since the on-chain contract development kit uses an AOP(aspect-oriented programming) approach to delegate the contract interoperability. In addition it also provides a lock API for locking contract state which can be used in two-phase commit cases. The off-chain relay uses an event based architecture to coordinate different permissioned blockchains. Learning Outcome 1) Implement the on-chain contract development kit for Hyperledger fabric using JAVA. 2) Implement the on-chain contract development kit for Consensys quorum or Hyperledger Besu using Solidity. 3) Implement the off-chain relay plugin for Consensys quorum or Hyperledger Besu.