Best practice on committing script utxo (blueprint)

[HinsonSIDAN]

Description

We know that we can commit script utxos into Hydra using blueprint. However, from the perspective of implementing the on-chain script (e.g. Plutus or Aiken script), we need to specify a redeemer for allowing getting into Hydra.

Since DApps' states are critical so as the time getting into Hydra, if this step isn't guarded correctly it would become a single point of failure of the entire DApps.

As every DApp considering using Hydra must face this issue at some point, think it would be great for Hydra team to propose an official "best practice" for committing script utxos into Hydra.

Suggested solution

So far from my team's understanding, best thing we can do is checking:

1. Whether the tx (the committing tx) is signed by all keys of hosted hydra node
2. Whether the output is send to the hydra validator address with inline datum of the way Hydra node read it (i.e. serializing entire utxo information)

Alternative

No response

Additional context

No response

[noonio]

Related - #1655