data representations/formats (in this case, between protobufs and JSON). Additionally, the tool can compute a configuration update transaction based on the differences between two channel configurations. config protobufs. This command will output a new protobuf binary named org3_update.pb: configtxlator compute_update --channel_id $CHANNEL_NAME --original config.pb --updated modified_config.pb --output org3_update proto_encode --input modified_config.json --type common.Config --output modified_config.pb configtxlator compute_update --channel_id $CH_NAME --original config.pb --updated modified_config.pb --output config_update

data representations/formats (in this case, between protobufs and JSON). Additionally, the tool can compute a configuration update transaction based on the differences between two channel configurations. config protobufs. This command will output a new protobuf binary named org3_update.pb: configtxlator compute_update --channel_id $CHANNEL_NAME --original config.pb -- ˓→updated modified_config.pb --output --input modified_config.json --type common.Config --output ˓→modified_config.pb configtxlator compute_update --channel_id $CH_NAME --original config.pb --updated ˓→modified_config.pb --output config_update

into a dispute or if they want to transfer the asset to a third party. The third party can then compute the hash of the private data and see if it matches the state on the channel ledger, proving that data representations/formats (in this case, between protobufs and JSON). Additionally, the tool can compute a configuration update transaction based on the differences between two channel configurations. config protobufs. This command will output a new protobuf binary named org3_update.pb: configtxlator compute_update --channel_id $CHANNEL_NAME --original config.pb --updated modified_config.pb --output org3_update

into a dispute or if they want to transfer the asset to a third party. The third party can then compute the hash of the private data and see if it matches the state on the channel ledger, proving that data representations/formats (in this case, between protobufs and JSON). Additionally, the tool can compute a configuration update transaction based on the differences between two channel configurations. config protobufs. This command will output a new protobuf binary named org3_update.pb: configtxlator compute_update --channel_id $CHANNEL_NAME --original config.pb -- ˓→updated modified_config.pb --output

into a dispute or if they want to transfer the asset to a third party. The third party can then compute the hash of the private data and see if it matches the state on the channel ledger, proving that data representations/formats (in this case, between protobufs and JSON). Additionally, the tool can compute a configuration update transaction based on the differences between two channel configurations. config protobufs. This command will output a new protobuf binary named org3_update.pb: configtxlator compute_update --channel_id $CHANNEL_NAME --original config.pb -- ˓→updated modified_config.pb --output

into a dispute or if they want to transfer the asset to a third party. The third party can then compute the hash of the private data and see if it matches the state on the channel ledger, proving that data representations/formats (in this case, between protobufs and JSON). Additionally, the tool can compute a configuration update transaction based on the differences between two channel configurations. config protobufs. This command will output a new protobuf binary named org3_update.pb: configtxlator compute_update --channel_id $CHANNEL_NAME --original config.pb --updated modified_config.pb --output org3_update

into a dispute or if they want to transfer the asset to a third party. The third party can then compute the hash of the private data and see if it matches the state on the channel ledger, proving that data representations/formats (in this case, between protobufs and JSON). Additionally, the tool can compute a configuration update transaction based on the differences between two channel configurations. config protobufs. This command will output a new protobuf binary named org3_update.pb: configtxlator compute_update --channel_id $CHANNEL_NAME --original config.pb -- ˓→updated modified_config.pb --output

into a dispute or if they want to transfer the asset to a third party. The third party can then compute the hash of the private data and see if it matches the state on the channel ledger, proving that data representations/formats (in this case, between protobufs and JSON). Additionally, the tool can compute a configuration update transaction based on the differences between two channel configurations. config protobufs. This command will output a new protobuf binary named org3_update.pb: configtxlator compute_update --channel_id $CHANNEL_NAME --original config.pb --updated modified_config.pb --output org3_update

into a dispute or if they want to transfer the asset to a third party. The third party can then compute the hash of the private data and see if it matches the state on the channel ledger, proving that data representations/formats (in this case, between protobufs and JSON). Additionally, the tool can compute a configuration update transaction based on the differences between two channel configurations. config protobufs. This command will output a new protobuf binary named org3_update.pb: configtxlator compute_update --channel_id $CHANNEL_NAME --original config.pb -- ˓→updated modified_config.pb --output

into a dispute or if they want to transfer the asset to a third party. The third party can then compute the hash of the private data and see if it matches the state on the channel ledger, proving that data representations/formats (in this case, between protobufs and JSON). Additionally, the tool can compute a configuration update transaction based on the differences between two channel configurations. config protobufs. This command will output a new protobuf binary named org3_update.pb: configtxlator compute_update --channel_id $CHANNEL_NAME --original config.pb -- ˓→updated modified_config.pb --output