all relevant organizations before it is applied to the ledger. Failed transactions are retained for audit, but are not applied to the ledger. The second role of an orderer node is to distribute blocks to updates the ledger. Failed transactions are not applied to the ledger, but they are retained for audit purposes, as are successful transactions. This means that peer blocks are almost exactly the same | | |____/ |_| /_/ \_\ |_| \_\ |_| Channel name : mychannel Creating channel... The logs will continue from there. This will launch all of the containers, and then drive a complete end-to-end

all relevant organizations before it is applied to the ledger. Failed transactions are retained for audit, but are not applied to the ledger. The second role of an orderer node is to distribute blocks to updates the ledger. Failed transactions are not applied to the ledger, but they are retained for audit purposes, as are successful transactions. This means that peer blocks are almost exactly the same The hash serves as evidence of the transaction and is used for state validation and can be used for audit purposes. The following diagram illustrates the ledger contents of a peer authorized to have private

all relevant organizations before it is applied to the ledger. Failed transactions are retained for audit, but are not applied to the ledger. The second role of an orderer node is to distribute blocks to updates the ledger. Failed transactions are not applied to the ledger, but they are retained for audit purposes, as are successful transactions. This means that peer blocks are almost exactly the same The hash serves as evidence of the transaction and is used for state validation and can be used for audit purposes. The following diagram illustrates the ledger contents of a peer authorized to have private

00000000000000000000000056170706c650 00000000000000000000000000000000000000000000000000000", "logs":[ { "address":"0x42fc572759fd568bd590f46011784be2a2d53f0c", "dat 00000000000000000000000056170706c650 00000000000000000000000000000000000000000000000000000", "logs":[ { "address":"0x42fc572759fd568bd590f46011784be2a2d53f0c", "data --------------------------------------------------------------------- ------------------------ Event logs event signature: InsertResult(int256) index: 0 event value: (1) ---------------------------------

00000000000000000000000056170706c650 00000000000000000000000000000000000000000000000000000", "logs":[ { "address":"0x42fc572759fd568bd590f46011784be2a2d53f0c", "data 00000000000000000000000056170706c650 00000000000000000000000000000000000000000000000000000", "logs":[ { "address":"0x42fc572759fd568bd590f46011784be2a2d53f0c", "data --------------------------------------------------------------------- ------------------------ Event logs event signature: InsertResult(int256) index: 0 event value: (1) ---------------------------------

00000000000000000000000056170706c650 00000000000000000000000000000000000000000000000000000", "logs":[ { "address":"0x42fc572759fd568bd590f46011784be2a2d53f0c", "data 00000000000000000000000056170706c650 00000000000000000000000000000000000000000000000000000", "logs":[ { "address":"0x42fc572759fd568bd590f46011784be2a2d53f0c", "data --------------------------------------------------------------------- ------------------------ Event logs event signature: InsertResult(int256) index: 0 event value: (1) ---------------------------------

00000000000000000000000056170706c650 00000000000000000000000000000000000000000000000000000", "logs":[ { "address":"0x42fc572759fd568bd590f46011784be2a2d53f0c", "data 00000000000000000000000056170706c650 00000000000000000000000000000000000000000000000000000", "logs":[ { "address":"0x42fc572759fd568bd590f46011784be2a2d53f0c", "data --------------------------------------------------------------------- ------------------------ Event logs event signature: InsertResult(int256) index: 0 event value: (1) ---------------------------------

00000000000000000000000056170706c650 00000000000000000000000000000000000000000000000000000", "logs":[ { "address":"0x42fc572759fd568bd590f46011784be2a2d53f0c", "data 00000000000000000000000056170706c650 00000000000000000000000000000000000000000000000000000", "logs":[ { "address":"0x42fc572759fd568bd590f46011784be2a2d53f0c", "data --------------------------------------------------------------------- ------------------------ Event logs event signature: InsertResult(int256) index: 0 event value: (1) ---------------------------------

all relevant organizations before it is applied to the ledger. Failed transactions are retained for audit, but are not applied to the ledger. The second role of an orderer node is to distribute blocks to updates the ledger. Failed transactions are not applied to the ledger, but they are retained for audit purposes, as are successful transactions. This means that peer blocks are almost exactly the same The hash serves as evidence of the transaction and is used for state validation and can be used for audit purposes. The following diagram illustrates the ledger contents of a peer authorized to have private

all relevant organizations before it is applied to the ledger. Failed transactions are retained for audit, but are not applied to the ledger. The second role of an orderer node is to distribute blocks to updates the ledger. Failed transactions are not applied to the ledger, but they are retained for audit purposes, as are successful transactions. This means that peer blocks are almost exactly the same The hash serves as evidence of the transaction and is used for state validation and can be used for audit purposes. The following diagram illustrates the ledger contents of a peer authorized to have private