You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hydra doom people had a question related to one of our checks in the initial validator https://github.com/cardano-scaling/hydra/blob/master/hydra-plutus/src/Hydra/Contract/Initial.hs#L125C9-L126C37 . They have the need to change the values distributed on L2 without using an extra tx on L2 hopefully. The increment validator is making this impossible since it expects that whatever we put in the commit datum to be matching exactly with what we consume in the commit tx and the same needs to be present in the initial redeemer (ViaCommit) . What they would like is to keep the UTxO value check but don't check if the exact inputs are also locked so that they could distribute the UTxO on L2 as they please. Question is: does this affect any security guarantees of a Hydra Head protocol?
The text was updated successfully, but these errors were encountered:
ViaCommit
) . What they would like is to keep the UTxO value check but don't check if the exact inputs are also locked so that they could distribute the UTxO on L2 as they please. Question is: does this affect any security guarantees of a Hydra Head protocol?The text was updated successfully, but these errors were encountered: