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>
* Import Full Stack Asset Transfer Guide at commit fb554befdbbeff9e69159b54fce0b811603f29c7
Signed-off-by: Josh Kneubuhl <jkneubuh@us.ibm.com>
* Update the workshop with a new WORKSHOP_PATH under fabric-samples
Signed-off-by: Josh Kneubuhl <jkneubuh@us.ibm.com>
* Update the workshop with a new WORKSHOP_PATH under fabric-samples
Signed-off-by: Josh Kneubuhl <jkneubuh@us.ibm.com>
* missed a .git ignored directory on add
Signed-off-by: Josh Kneubuhl <jkneubuh@us.ibm.com>
* Updates to run the workshop on the Apple M1
Signed-off-by: Josh Kneubuhl <jkneubuh@us.ibm.com>
* Workaround for https://github.com/eslint/eslint/issues/15299 in the contract tslinter
Signed-off-by: Josh Kneubuhl <jkneubuh@us.ibm.com>
* Build an arch-specific CC images on M1
Signed-off-by: Josh Kneubuhl <jkneubuh@us.ibm.com>
* empty commit - force a build
Signed-off-by: Josh Kneubuhl <jkneubuh@us.ibm.com>
* revert an accidental commit that was building the top-level asset-transfer as arm64
Signed-off-by: Josh Kneubuhl <jkneubuh@us.ibm.com>
Signed-off-by: Josh Kneubuhl <jkneubuh@us.ibm.com>
