you have not made any modifications to the default channel name, then the command will return you a proto titled mychannel.block. Note You will remain in the CLI container for the remainder of these manual Understanding the Docker Compose topology The BYFN sample offers us two flavors of Docker Compose files, both of which are extended from the docker-compose-base.yaml (located in the base folder). Our first into the org3-artifacts subdirectory from first- network. cd org3-artifacts There are two yaml files of interest here: org3-crypto.yaml and configtx.yaml. First, generate the crypto material for Org3:

the appropriate version tag 3. Install the Hyperledger Fabric platform-specific binaries and config files for the version specified into the /bin and /config directories of fabric-samples 4. Download the c75bd6911aca8089...-pub You can examine these files, but as discussed, it’s easier to use the SDK to manipulate these data. Operations The different place to run the application. For this tutorial, you’ll primarily be using the application JavaScript files in the fabcar/javascript directory. Let’s take a look at what’s inside: ls You should see the following:

the appropriate version tag 3. Install the Hyperledger Fabric platform-specific binaries and config files for the version specified into the /bin and /config directories of fabric-samples 4. Download the c75bd6911aca8089...-pub You can examine these files, but as discussed, it’s easier to use the SDK to manipulate these data. Operations The different place to run the application. For this tutorial, you’ll primarily be using the application JavaScript files in the fabcar/javascript directory. Let’s take a look at what’s inside: ls You should see the following:

the appropriate version tag 3. Install the Hyperledger Fabric platform-specific binaries and config files for the version specified into the /bin and /config directories of fabric-samples 4. Download the c75bd6911aca8089...-pub You can examine these files, but as discussed, it’s easier to use the SDK to manipulate these data. Operations The different place to run the application. For this tutorial, you’ll primarily be using the application JavaScript files in the fabcar/javascript directory. Let’s take a look at what’s inside: ls You should see the following:

the appropriate version tag 3. Install the Hyperledger Fabric platform-specific binaries and config files for the version specified into the /bin and /config directories of fabric-samples 4. Download the you have not made any modifications to the default channel name, then the command will return you a proto titled mychannel.block. Note You will remain in the CLI container for the remainder of these manual Understanding the Docker Compose topology The BYFN sample offers us two flavors of Docker Compose files, both of which are extended from the docker-compose-base.yaml (located in the base folder). Our first

the appropriate version tag 3. Install the Hyperledger Fabric platform-specific binaries and config files for the version specified into the /bin and /config directories of fabric-samples 4. Download the you have not made any modifications to the default channel name, then the command will return you a proto titled mychannel.block. Note You will remain in the CLI container for the remainder of these manual Understanding the Docker Compose topology The BYFN sample offers us two flavors of Docker Compose files, both of which are extended from the docker-compose-base.yaml (located in the base folder). Our first

channel. Inspectable chaincode packages The Fabric lifecycle packages chaincode in easily readable tar files. This makes it easier to inspect the chaincode package and coordinate installation across multiple extension. The tar file needs to contain two files (no directory): a metadata file “metadata.json” and another tar “code.tar.gz” containing the chaincode files. “metadata.json” contains JSON that specifies the appropriate version tag 3. Install the Hyperledger Fabric platform-specific binaries and config files for the version specified into the /bin and /config directories of fabric-samples 4. Download the

channel. Inspectable chaincode packages The Fabric lifecycle packages chaincode in easily readable tar files. This makes it easier to inspect the chaincode package and coordinate installation across multiple extension. The tar file needs to contain two files (no directory): a metadata file “metadata.json” and another tar “code.tar.gz” containing the chaincode files. “metadata.json” contains JSON that specifies the appropriate version tag 3. Install the Hyperledger Fabric platform-specific binaries and config files for the version specified into the /bin and /config directories of fabric-samples 4. Download the

channel. Inspectable chaincode packages The Fabric lifecycle packages chaincode in easily readable tar files. This makes it easier to inspect the chaincode package and coordinate installation across multiple file extension. The tar file needs to contain two files (no directory): a metadata file “metadata.json” and another tar containing the chaincode files. “metadata.json” contains JSON that specifies the the appropriate version tag 3. Install the Hyperledger Fabric platform-specific binaries and config files for the version specified into the /bin and /config directories of fabric-samples 4. Download the

channel. Inspectable chaincode packages The Fabric lifecycle packages chaincode in easily readable tar files. This makes it easier to inspect the chaincode package and coordinate installation across multiple file extension. The tar file needs to contain two files (no directory): a metadata file “metadata.json” and another tar containing the chaincode files. “metadata.json” contains JSON that specifies the the appropriate version tag 3. Install the Hyperledger Fabric platform-specific binaries and config files for the version specified into the /bin and /config directories of fabric-samples 4. Download the