<oembed><type>rich</type><version>1.0</version><title>Rusty Russell [ARCHIVE] wrote</title><author_name>Rusty Russell [ARCHIVE] (npub1zw…hkhpx)</author_name><author_url>https://yabu.me/npub1zw7cc8z78v6s3grujfvcv3ckpvg6kr0w7nz9yzvwyglyg0qu5sjsqhkhpx</author_url><provider_name>njump</provider_name><provider_url>https://yabu.me</provider_url><html>📅 Original date posted:2019-12-02&#xA;📝 Original message:&#xA;Conner Fromknecht &lt;conner at lightning.engineering&gt; writes:&#xA;&gt; Hi all,&#xA;&gt;&#xA;&gt; I recently revisited the eltoo paper and noticed some things related&#xA;&gt; watchtowers that might affect channel construction.&#xA;&gt;&#xA;&gt; Due to NOINPUT, any update transaction _can_ spend from any other, so&#xA;&gt; in theory the tower only needs the most recent update txn to resolve&#xA;&gt; any dispute.&#xA;&gt;&#xA;&gt; In order to spend, however, the tower must also produce a witness&#xA;&gt; script which when hashed matches the witness program of the input. To&#xA;&gt; ensure settlement txns can only spend from exactly one update txn,&#xA;&gt; each update txn uses unique keys for the settlement clause, meaning&#xA;&gt; that each state has a _unique_ witness program.&#xA;&#xA;I didn&#39;t think this was the design.  The update transaction can spend&#xA;any prior, with a fixed script, due to NOINPUT.&#xA;&#xA;The settlement transaction does *not* use NOINPUT, and thus can only&#xA;spend the matching update.&#xA;&#xA;Cheers,&#xA;Rusty.</html></oembed>