@@ -139,8 +139,8 @@ be accessed.
139
139
140
140
Specifically access to the private data will be restricted as follows:
141
141
142
- - ``name, color, size, and owner `` will be visible to all members of the channel (Org1 and Org2)
143
- - ``price `` only visible to members of Org1
142
+ - ``name, color, size, and owner `` will be visible to all members of the channel (Org1 and Org2)
143
+ - ``price `` only visible to members of Org1
144
144
145
145
Thus two different sets of private data are defined in the marbles private data
146
146
sample. The mapping of this data to the collection policy which restricts its
@@ -218,7 +218,7 @@ For example, in the following snippet of the ``initMarble`` function,
218
218
err = stub.PutPrivateData("collectionMarblePrivateDetails", marbleName, marblePrivateDetailsBytes)
219
219
if err != nil {
220
220
return shim.Error(err.Error())
221
- }
221
+ }
222
222
223
223
To summarize, the policy definition above for our ``collection.json ``
224
224
allows all peers in Org1 and Org2 can store and transact (endorse, commit,
@@ -529,7 +529,7 @@ Switch to a peer in Org2
529
529
~~~~~~~~~~~~~~~~~~~~~~~~
530
530
531
531
From inside the docker container, run the following commands to switch to
532
- the peer which is unauthorized to the marbles ``price `` private data.
532
+ the peer which is unauthorized to access the marbles ``price `` private data.
533
533
534
534
:guilabel: `Try it yourself `
535
535
@@ -582,7 +582,7 @@ the public state but will not have the private state.
582
582
transaction ID: b04adebbf165ddc90b4ab897171e1daa7d360079ac18e65fa15d84ddfebfae90:
583
583
Private data matching public hash version is not available. Public hash
584
584
version = &version.Height{BlockNum:0x6, TxNum:0x0 }, Private data version =
585
- (*version.Height)(nil)"}"
585
+ (*version.Height)(nil)"}
586
586
587
587
Members of Org2 will only be able to see the public hash of the private data.
588
588
0 commit comments