<oembed><type>rich</type><version>1.0</version><title>ZmnSCPxj [ARCHIVE] wrote</title><author_name>ZmnSCPxj [ARCHIVE] (npub1g5…3ms3l)</author_name><author_url>https://yabu.me/npub1g5zswf6y48f7fy90jf3tlcuwdmjn8znhzaa4vkmtxaeskca8hpss23ms3l</author_url><provider_name>njump</provider_name><provider_url>https://yabu.me</provider_url><html>📅 Original date posted:2020-04-02&#xA;📝 Original message:&#xA;Good morning Nadav,&#xA;&#xA;&gt; I could be missing something, but it seems to me like the proposal to close channels after a soft timeout unless non-cooperation can be proven upstream adds a cost to the attacker of two on-chain transactions, which they can immediately revoke (as they know both pieces to the revocation priv key), but still allows very long lock-ups of other&#39;s funds (with a 10x multiplier if they choose a long route). I do think that this is certainly an improvement on what we have now but I&#39;m not sure it properly punishes the attacker in its current form.&#xA;&#xA;Ah, right, E knows the revocation for the unilateral close of EE, because it is a self-channel, sigh.&#xA;And by this revocation clause it can claim the money immediately and put it into a channel as well.&#xA;&#xA;Regards,&#xA;ZmnSCPxj</html></oembed>