epistemophiliac/fabric-samples
1
0
Fork 0
mirror of https://github.com/hyperledger/fabric-samples.git synced 2026-06-17 15:35:09 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
fabric-samples/asset-transfer-private-data/application-gateway-typescript
History
Mark S. Lewis b931df3a5f Explicitly specify hash in client applications 
For some signing implementations, such as ed25519, a non-default hash
implementation must be specified when creating the Gateway connection in
client applications. Rather than relying on the default hash algorithm,
it is probably good practice in general to specify an algorithm that is
compatible with your signing implementation.

This change explicitly specifies the hash algorithm to raise visibility
of the option to select the hash algorithm.

Signed-off-by: Mark S. Lewis <Mark.S.Lewis@outlook.com>
2024-10-07 12:25:40 -04:00
..
src Explicitly specify hash in client applications 2024-10-07 12:25:40 -04:00
.gitignore Private data samples migration (#574) 2022-03-09 08:51:48 +00:00
.npmrc Enable engine-strict checks for TypeScript Gateway samples (#726) 2022-04-29 15:59:50 +01:00
eslint.config.mjs Update TypeScript implementations 2024-06-18 06:51:58 -04:00
package.json Update applications to use fabric-gateway v1.6.0 2024-09-25 13:18:45 +09:00
README.md Private data samples migration (#574) 2022-03-09 08:51:48 +00:00
tsconfig.json Update TypeScript implementations 2024-06-18 06:51:58 -04:00

README.md

Asset Transfer Private Data Sample

This app uses fabric-samples/test-network based setup and the companion chaincode asset-transfer-private-data/chaincode-go/ with chaincode endorsement policy as "OR('Org1MSP.peer','Org2MSP.peer')"

For this usecase illustration, we will use both Org1 & Org2 client identity from this same app In real world the Org1 & Org2 identity will be used in different apps to achieve asset transfer.

For more details refer: https://hyperledger-fabric.readthedocs.io/en/release-2.4/private_data_tutorial.html#pd-use-case