Sandra Vrtikapa

@csuwildcat @thehenrytsai Is this planned for v1?

@thehenrytsai I may have misunderstood your comment here: https://github.com/decentralized-identity/sidetree/blob/e64bcd3b7389350a9a8d50d8c8e6146a38ffd7d0/lib/core/versions/latest/OperationProcessor.ts#L91 I will remove hashAlgorithm parameter since it looks like it was never meant to be different hash for commitment double hashing

@thehenrytsai @csuwildcat Should we use the multihash code that is used for recoveryCommitment (part of suffix data)?

@thehenrytsai @csuwildcat @csuwildcat @troyronda According to spec all hashes have to be calculated using the same currently supported multi-hashing algorithm (https://identity.foundation/sidetree/spec/#hashing-process). Does this mean that you should reject create request...

@llorllale Currently the issuer (CMS) contains multiple sets of data for the user and the user is giving consent to the issuer to release (create credential for) certain set of...

Review latest spec before coding this.

Low priority, TBD.