<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-08&#xA;📝 Original message:Hi all,&#xA;&#xA;        The largest problem we are having today with the lightning&#xA;protocol is trying to predict future fees.  Eltoo solves this elegantly,&#xA;but meanwhile we would like to include a 546 satoshi OP_TRUE output in&#xA;commitment transactions so that we use minimal fees and then use CPFP&#xA;(which can&#39;t be done at the moment due to CSV delays on outputs).&#xA;&#xA;Unfortunately, we&#39;d have to P2SH it at the moment as a raw &#39;OP_TRUE&#39; is&#xA;non-standard.  Are there any reasons not to suggest such a policy&#xA;change?&#xA;&#xA;Thanks!&#xA;Rusty.</html></oembed>