<oembed><type>rich</type><version>1.0</version><author_name>npub1m230cem2yh3mtdzkg32qhj73uytgkyg5ylxsu083n3tpjnajxx4qqa2np2</author_name><author_url>https://nostr.ae/npub1m230cem2yh3mtdzkg32qhj73uytgkyg5ylxsu083n3tpjnajxx4qqa2np2</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2018-05-09&#xA;📝 Original message:On Thu, May 10, 2018 at 04:19:31AM +0800, Johnson Lau wrote:&#xA;&gt; &#xA;&gt; &#xA;&gt; &gt; On 10 May 2018, at 3:27 AM, Peter Todd &lt;pete at petertodd.org&gt; wrote:&#xA;&gt; &gt; &#xA;&gt; &gt; On Thu, May 10, 2018 at 01:56:46AM +0800, Johnson Lau via bitcoin-dev wrote:&#xA;&gt; &gt;&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;&gt; &gt;&gt; &#xA;&gt; &gt;&gt; Instead, would you consider to use ANYONECANPAY to sign the tx, so it is possible add more inputs for fees? The total tx size is bigger than the OP_TRUE approach, but you don’t need to ask for any protocol change.&#xA;&gt; &gt;&gt; &#xA;&gt; &gt;&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;&gt; &gt; &#xA;&gt; &gt; I don&#39;t think that will work, as a zero-fee tx won&#39;t get relayed even with&#xA;&gt; &gt; CPFP, due to the fact that we haven&#39;t yet implemented package-based tx&#xA;&gt; &gt; relaying.&#xA;&gt; &gt; &#xA;&gt; &gt; -- &#xA;&gt; &gt; https://petertodd.org &#39;peter&#39;[:-1]@petertodd.org&#xA;&gt; &#xA;&gt; My only concern is UTXO pollution. There could be a “CPFP anchor” softfork that outputs with empty scriptPubKey and 0 value are spendable only in the same block. If not spent immediately, they become invalid and are removed from UTXO. But I still think the best solution is a more flexible SIGHASH system, which doesn’t need CPFP at all.&#xA;&#xA;I don&#39;t see any reason why UTXO pollution would be a special concern so long as&#xA;those outputs are subject to the same dust rules as any other output is.&#xA;&#xA;-- &#xA;https://petertodd.org &#39;peter&#39;[:-1]@petertodd.org&#xA;-------------- next part --------------&#xA;A non-text attachment was scrubbed...&#xA;Name: signature.asc&#xA;Type: application/pgp-signature&#xA;Size: 488 bytes&#xA;Desc: not available&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20180509/17714285/attachment.sig&gt;</html></oembed>