revault
Non-repudiation in Revault
This has been mentioned over and over by @kloaec. We should make a list of cases for which we want to achieve non-repudiation (eg emergency broadcast) and whether we already do (spoiler alert: we don't for the former example) and/or are able at all.
Some update re identifying who has broadcast an emergency: we could use the locktimes to give ids to each participant, but it's incompatible with the "Massive Broadcast On Emergency" :tm: policy.
EmergencyTx: because it's REALLY not cool if it's sent without good reason. Now the only exception i see is under physical threat, you would know WHO triggered it (if manually triggered)
CancelTx: because if a watchtower is buggy and keep canceling it'd be kinda nice to know which one it is
The MBOE :tm: is indeed somewhat annoying. We could ask (honest) watchtowers to identity the triggering Emergency through logs or other means... but hey that relies on many assumptions (mempool relay especially)
For the cancel transaction it's not a threat, and debugging can be achieved by other means than modifying the "Smart Contracts :tm:"
Still annoying AF is someone is trolling and making logs look clean :trollface:
We assume nobody is trolling though, as they could always refuse to sign :)