Add new crypto features

[SupunS]

Closes #582

Description

This PR introduces the Cadence changes needed for the new crypto features. Includes the following changes:

Cadence Changes

Hash Algorithms

• New KMAC128_BLS_BLS12_381 hashing algorithm

  var algo: HashAlgorithm = HashAlgorithm.KMAC128_BLS_BLS12_381

Signature Algorithms

• New BLS_BLS12_381 signature algorithm

  var algo: SignatureAlgorithm = SignatureAlgorithm.BLS_BLS12_381

• Rename ECDSA_Secp256k1 signature algorithm to ECDSA_secp256k1

PublicKey Native Type

• New isValid field
  • eg:

    let publicKey = PublicKey(publicKey: [], signatureAlgorithm: SignatureAlgorithm.ECDSA_P256)
    
    let valid = publicKey.isValid

  • Get initialized during the construction of a public key, to the value returned by the ValidatePublicKey method on the host env.
• New verify method to validate a signature
  • signature: pub fun verify(signature: [UInt8], signedData: [UInt8], domainSeparationTag: String, hashAlgorithm: HashAlgorithm): Bool
  • e.g:

    let valid = publicKey.verify(
        signature: [],
        signedData: [],
        domainSeparationTag: "something",
        hashAlgorithm: HashAlgorithm.SHA2_256
    )

Crypto Contract

• New hashWithTag function
  • Signature: pub fun hashWithTag(_ data: [UInt8], tag: string, algorithm: HashAlgorithm): [UInt8]
  • e.g:

    Crypto.hashWithTag(
        "01020304".decodeHex(),
        tag: "some-tag",
        algorithm: HashAlgorithm.SHA3_256
     )
    

Changes to the FVM Interface

• New ValidatePublicKey(key *PublicKey) (bool, error) method
• Additional parameter tag string in the Hash method.
  • New signature: Hash(data []byte, tag string, hashAlgorithm HashAlgorithm) ([]byte, error)
• PublicKey has two new fields: IsValid and Validated

---

For contributor use:

• Targeted PR against master branch
• Linked to Github issue with discussion and accepted design OR link to spec that describes this work
• Code follows the standards mentioned here
• Updated relevant documentation
• Re-reviewed Files changed in the Github PR explorer
• Added appropriate labels

[turbolent]

Looks great, nice work!

I added a breaking changes label because of the naming change from ECDSA_Secp256k1 to ECDSA_secp256k1, which we need to communicate

[tarakby]

This is not quite what the verification checks, I suggest updating the text to be more precise:

    ///  Verifies a signature under the given tag, data and public key. It uses the given hash algorithm to hash the tag and data. 

[tarakby]

Another point, I'm not sure if this is right place to mention that all verifications with an invalid public key will fail.

[SupunS]

I think it should be fine to add it here, or we can also add it as a note outside of the code block.

[tarakby]

I leave this comment here, it's about the function at this line:

Shouldn't we also update isValid to Verify here too? or is that a big breaking change?

[tarakby]

I have suggested hashWithTag as I wasn't sure if PublicKey.Verify would be implemented entirely by the fvm or would be partly implemented in Cadence code. In the case of the former, I don't think hashWithTag is needed in Cadence, we would only need it as an fvm function.

[tarakby]

Can PublicKey fields (data, signature algo, isValid..) be updated after the creation of the object?

[SupunS]

No, they are defined as constant fields (i.e. read-only).

[tarakby]

As @turbolent mentioned about breaking changes, I think the change from isValid to verify is a breaking one.

[turbolent]

Hmm, both were added, so this isn't a breaking change

[tarakby]

ah my bad, I somehow though isValid already existed.