CAN will use multihash to encode digests

The CAN notebook will address notes using multihash encoded digests. This will allow future support for fallbacks in the case of a problem - as CAN will depend on openssl for hashing algorithms

Backlinks

• CAN will use SHA3 512-bit digests
  • The CAN notebook addresses will be SHA3-512 multihashes (CAN will use multihash to encode digests)
• When the SCRATCHFILE_PARSED event is fired CAN should hash the AST
  • CAN should fire a SCRATCHFILE_PARSED event. When this happens, CAN should make a digest of the AST. CAN will use SHA3-512 digests and will use multihash to encode digests. For now no check needs to be performed around which hashing algorithm is used, as there's only one implemented.
• CAN will depend on openssl for hashing algorithms
  • node uses openssl for crypto under the hood. Because CAN will encode digests with multihash, can will be able to provide fallbacks in the future.
• Which hashing algorithm should the CAN manager use?
  • This leads to a few decisions. Firstly, CAN will use SHA3-512 digests. Secondly, CAN will use multihash to encode digests. Finally as node relies on openssl for crypto, CAN will depend on openssl for hashing algorithms.