{"type":"rich","version":"1.0","author_name":"npub1fyh6gqhg8zgyhhywkty047s64z2a7fjr307enrr3kqwtnk64plmsup2mv9","author_url":"https://nostr.ae/npub1fyh6gqhg8zgyhhywkty047s64z2a7fjr307enrr3kqwtnk64plmsup2mv9","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2018-05-09\n📝 Original message: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\nInstead, 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.\n\nIn 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\n\n\n\u003e On 9 May 2018, at 7:57 AM, Rusty Russell via bitcoin-dev \u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e \n\u003e Hi all,\n\u003e \n\u003e        The largest problem we are having today with the lightning\n\u003e protocol is trying to predict future fees.  Eltoo solves this elegantly,\n\u003e but meanwhile we would like to include a 546 satoshi OP_TRUE output in\n\u003e commitment transactions so that we use minimal fees and then use CPFP\n\u003e (which can't be done at the moment due to CSV delays on outputs).\n\u003e \n\u003e Unfortunately, we'd have to P2SH it at the moment as a raw 'OP_TRUE' is\n\u003e non-standard.  Are there any reasons not to suggest such a policy\n\u003e change?\n\u003e \n\u003e Thanks!\n\u003e Rusty.\n\u003e _______________________________________________\n\u003e bitcoin-dev mailing list\n\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev"}