{"type":"rich","version":"1.0","author_name":"npub1zw7cc8z78v6s3grujfvcv3ckpvg6kr0w7nz9yzvwyglyg0qu5sjsqhkhpx","author_url":"https://nostr.ae/npub1zw7cc8z78v6s3grujfvcv3ckpvg6kr0w7nz9yzvwyglyg0qu5sjsqhkhpx","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2018-05-09\n📝 Original message:Johnson Lau \u003cjl2012 at xbt.hk\u003e writes:\n\u003e 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\n\nThat won't propagate :(\n\n\u003e Instead, would you consider to use ANYONECANPAY to sign the tx, so it\n\u003e is possible add more inputs for fees? The total tx size is bigger than\n\u003e the OP_TRUE approach, but you don’t need to ask for any protocol\n\u003e change.\n\nNo, that would change the TXID, which we rely on for HTLC transactions.\n\n\u003e 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.\n\nAgreed:\nhttps://lists.linuxfoundation.org/pipermail/bitcoin-dev/2018-April/015862.html\n\nBut in the long term we'll have Eltoo and SIGHASH_NOINPUT which both\nallow different solutions.\n\nCheers,\nRusty."}
