<oembed><type>rich</type><version>1.0</version><author_name>npub1zw7cc8z78v6s3grujfvcv3ckpvg6kr0w7nz9yzvwyglyg0qu5sjsqhkhpx</author_name><author_url>https://nostr.ae/npub1zw7cc8z78v6s3grujfvcv3ckpvg6kr0w7nz9yzvwyglyg0qu5sjsqhkhpx</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2018-05-09&#xA;📝 Original message:Johnson Lau &lt;jl2012 at xbt.hk&gt; writes:&#xA;&gt; You should make a “0 fee tx with exactly one OP_TRUE output” standard, but nothing else. This makes sure CPFP will always be needed, so the OP_TRUE output won’t pollute the UTXO set&#xA;&#xA;That won&#39;t propagate :(&#xA;&#xA;&gt; Instead, would you consider to use ANYONECANPAY to sign the tx, so it&#xA;&gt; is possible add more inputs for fees? The total tx size is bigger than&#xA;&gt; the OP_TRUE approach, but you don’t need to ask for any protocol&#xA;&gt; change.&#xA;&#xA;No, that would change the TXID, which we rely on for HTLC transactions.&#xA;&#xA;&gt; In long-term, I think the right way is to have a more flexible SIGHASH system to allow people to add more inputs and outputs easily.&#xA;&#xA;Agreed:&#xA;https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2018-April/015862.html&#xA;&#xA;But in the long term we&#39;ll have Eltoo and SIGHASH_NOINPUT which both&#xA;allow different solutions.&#xA;&#xA;Cheers,&#xA;Rusty.</html></oembed>