CAN will use SHA3 512-bit digests

The CAN notebook addresses will be SHA3-512 multihashes (CAN will use multihash to encode digests)

Backlinks

• Each CAN address is a directory
  • Inside CAN's notebook there should exist a directory for every address present. The directory will be named the hash of the note which lives at this address (CAN will use SHA3-512 digests). Inside the address there'll be an AST file with the content of the note itself and a metadata file alongside the AST.
• 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.
• Each CAN address will contain an AST file
  • If you hash the contents of this file, you should find the address it is stored at (CAN will use SHA3-512)
• 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.