Open kss-espeo opened 5 years ago
A default deployment should also be aligned, so that a one command build spins up a Fabric environment and deploys to it.
Possibly it means gardener-smart-contracts
will be split into something like gardener-ethereum
and gardener-fabric
, an other option is to just make gardener-smart-contracts
configurable.
Almost done, but blocked on https://jira.hyperledger.org/browse/FAB-16792
Integrate Gardener with Hyperledger Fabric. It should be seamless - all the smart contracts that currently work on Ethereum should also on Fabric. Server-side part of Gardener should remain unchanged.