Sign snapshots including the initial UTxO set #688
Labels
amber ⚠️
Medium complexity or partly unclear feature
L1
Affects the on-chain protocol of Hydra
💬 feature
A feature on our roadmap
superseded
An item that may get superseded by related feature.
Why
Users would like to have their funds not be locked up and be inaccessible, even if a rollback past the "opening" happens.
When a Head is open and snapshots have been signed, but then a
collectCom
and one or morecommit
transactions were rolled back, a bad actor could choose to commit a different UTxO and open the Head with a different initial UTxO set, while the already signed snapshots would still be (cryptographically) valid. This is problematic as the old snapshots would still be valid to close the head with a not agreed or even invalid (= not fanoutable) UTxO set.To mitigate this, all signatures on snapshots need to incorporate the initial UTxO set by including η0.
What
S1
is createdcollectCom
and one of thecommit
transactionscommit
transaction with a different UTxOcollectCom
transactionS1
should not be possible, but right now it wouldHow
Context
https://nvd.nist.gov/vuln-metrics/cvss/v2-calculator?vector=(AV:L/AC:H/Au:M/C:N/I:P/A:C/E:U/RL:ND/RC:ND/CDP:L/TD:L/CR:ND/IR:ND/AR:ND)
The text was updated successfully, but these errors were encountered: