Interview the internal auditor to see what kind of specification they will require to audit the protocol logic

[ch1bo]

No description provided.

[ch1bo]

From latest interaction

• The new spec "looks simpler" than the paper. (Although not compared in detail I guess)
• Would benefit from list of interactions / use cases
• After chatting a bit, a state diagram explaining the interaction (individual API messages + side effects) with the hydra-node could help .. maybe also a dedicated architecture page.

[ffakenz]

During the last interview with the auditor (Yun Lu), we went through the spec document to resolve questions and provide clarifications.

Observations:

• It was mentioned by @arnaud that it would be great to have, as an outcome, a specification anyone can follow to implement the hydra-head protocol.
• Yun mentioned that she is currently working on getting a high-level overview of the spec, and providing some starting questions over email, and that she was going to start getting into the details later on. We agree not to continue the discussions over email but over the spec document or Slack.
• @arnaud shared the Miro board "head full life cycle," which the auditor found useful (an updated version will be sent to her).
• There were some things unclear to Yun:
  • Why not define "val" assets using Set notation?
  • What exactly is the PT and how does it work (what role does it play in the protocol)?
• Yun's questions revealed her lack of experience with Plutus scripts for writing smart contracts.
• Yun mentioned she only has a fixed box time of 2 hours per week to work on the spec.
• We only covered the "on-chain validators" section of the spec document during this interview.