fabric-samples/asset-transfer-private-data/chaincode-go
Matthew B White 67ae2c9d02 Correct the private data collection information
For the asset transfer example (https://hyperledger-fabric.readthedocs.io/en/release-2.5/private_data_tutorial.html#pd-use-case)
the are three private data collections, one per org and one shared between the orgs.

The shared collection didn't have an endorsement policy so inheritted the chaincodes; this was specifically set away from the default
to be OR(Org1MSP,Org2MSP).   The documentation says this is to ensure that either organization can create and asset.

However this isn't really necassary, the endorsement policy should be lowest level; so this PR moves the endorsement policy to
the collection.  The documentation does I believe lead to a false understanding

Signed-off-by: Matthew B White <whitemat@uk.ibm.com>
2023-03-22 16:19:56 -04:00
..
chaincode Add in examples and notes on using PurgePrivateData (#878) 2023-01-23 11:40:52 -05:00
META-INF/statedb/couchdb/collections/assetCollection/indexes bugfix: asset type field name in couchdb index def 2020-10-12 16:27:17 -04:00
collections_config.json Correct the private data collection information 2023-03-22 16:19:56 -04:00
go.mod Update Go and Go dependencies (#996) 2023-03-07 14:44:33 +00:00
go.sum Update Go and Go dependencies (#996) 2023-03-07 14:44:33 +00:00
main.go Asset transfer private-data go-chaincode - Add unit tests (#290) 2020-08-25 10:04:03 -04:00
README.md go chaincode now sets the Asset owner as client identity certificate string (instead of base64 str) 2020-11-25 22:40:04 -05:00