order-execute architecture can be found in virtually all existing blockchain systems, ranging from pub- lic/permissionless platforms such as Ethereum (with PoW-based consensus) to permissioned platforms • cryptogen, • idemixgen • orderer, • peer, and • fabric-ca-client and places them in the bin sub-directory of the current working directory. You may want to add that to your PATH environment variable play either within the scope of the organization the MSP represents (e.g., admins, or as members of a sub-organization group), and sets the basis for defining access privileges in the context of a network

configtxlator, cryptogen, idemixgen orderer, peer, and fabric-ca-client and places them in the bin sub-directory of the current working directory. You may want to add that to your PATH environment variable play either within the scope of the organization the MSP represents (e.g., admins, or as members of a sub-organization group), and sets the basis for defining access privileges in the context of a network first-network sample. Let’s open that sub- directory now. cd fabric-samples/first-network Note The supplied commands in this documentation MUST be run from your first- network sub-directory of the fabric-samples

order-execute architecture can be found in virtually all existing blockchain systems, ranging from pub- lic/permissionless platforms such as Ethereum (with PoW-based consensus) to permissioned platforms play either within the scope of the organization the MSP represents (e.g., admins, or as members of a sub-organization group), and sets the basis for defining access privileges in the context of a network • discover, • idemixgen • orderer, • peer, and • fabric-ca-client and places them in the bin sub-directory of the current working directory. You may want to add that to your PATH environment variable

play either within the scope of the organization the MSP represents (e.g., admins, or as members of a sub-organization group), and sets the basis for defining access privileges in the context of a network configtxlator, cryptogen, discover, idemixgen orderer, peer, and fabric-ca-client and places them in the bin sub-directory of the current working directory. You may want to add that to your PATH environment variable first-network sample. Let’s open that sub- directory now. cd fabric-samples/first-network Note The supplied commands in this documentation MUST be run from your first- network sub-directory of the fabric-samples

order-execute architecture can be found in virtually all existing blockchain systems, ranging from pub- lic/permissionless platforms such as Ethereum (with PoW-based consensus) to permissioned platforms play either within the scope of the organization the MSP represents (e.g., admins, or as members of a sub-organization group), and sets the basis for defining access privileges in the context of a network • discover, • idemixgen • orderer, • peer, and • fabric-ca-client and places them in the bin sub-directory of the current working directory. You may want to add that to your PATH environment variable

elements that render the functionality we’ve described so far. A local MSP folder contains the following sub-folders: The figure above shows the subfolders in a local MSP on the file system config.yaml: Used discover, idemixgen, orderer, peer, fabric-ca-client, fabric-ca-server and places them in the bin sub-directory of the current working directory. You may want to add that to your PATH environment variable topic you’ve understood how to implement the smart contract for PaperNet. You can move to the next sub topic to see how an application calls the smart contract using the Fabric SDK. Application Audience:

elements that render the functionality we’ve described so far. A local MSP folder contains the following sub-folders: The figure above shows the subfolders in a local MSP on the file system config.yaml: Used discover, idemixgen, orderer, peer, fabric-ca-client, fabric-ca-server and places them in the bin sub-directory of the current working directory. You may want to add that to your PATH environment variable topic you’ve understood how to implement the smart contract for PaperNet. You can move to the next sub topic to see how an application calls the smart contract using the Fabric SDK. Application Audience:

elements that render the functionality we’ve described so far. A local MSP folder contains the following sub-folders: The figure above shows the subfolders in a local MSP on the file system config.yaml: Used discover, idemixgen, orderer, peer, fabric-ca-client, fabric-ca-server and places them in the bin sub-directory of the current working directory. You may want to add that to your PATH environment variable topic you’ve understood how to implement the smart contract for PaperNet. You can move to the next sub topic to see how an application calls the smart contract using the Fabric SDK. Application Audience:

play either within the scope of the organization the MSP represents (e.g., admins, or as members of a sub-organization group), and sets the basis for defining access privileges in the context of a network configtxlator, cryptogen, discover, idemixgen orderer, peer, and fabric-ca-client and places them in the bin sub-directory of the current working directory. You may want to add that to your PATH environment variable topic you’ve understood how to implement the smart contract for PaperNet. You can move to the next sub topic to see how an application calls the smart contract using the Fabric SDK. Application Audience:

order-execute architecture can be found in virtually all existing blockchain systems, ranging from pub- lic/permissionless platforms such as Ethereum (with PoW-based consensus) to permissioned platforms elements that render the functionality we’ve described so far. A local MSP folder contains the following sub-folders: The figure above shows the subfolders in a local MSP on the file system • config.yaml: Used idemixgen, • orderer, • peer, • fabric-ca-client, • fabric-ca-server and places them in the bin sub-directory of the current working directory. You may want to add that to your PATH environment variable