Head identification in commit/deposit

[ch1bo]

Why

DApps on Cardano are represented as script validators. Making a DApp support the Hydra L2 means to make the spending validator be agreeing to spend parts of the DApp state into the Hydra Head via a commit/deposit transaction. Consequently, DApp developers need to know how those transactions look like and how they can write validators that acknowledge transfer of state (or funds) into en eligible Head.

What

• Create an interface specification, documentation and examples for DApp developers that explains how a script can verify the Head it is spent into.

• Ensure that commit/deposit transaction contain enough reliable information to identify the Head a script output is transferred to, e.g.

  • Number of participants (validators)
  • Public keys of participants (validators)
  • Contestation period