<oembed><type>rich</type><version>1.0</version><title>stallion wrote</title><author_name>stallion (npub187…24sdn)</author_name><author_url>https://yabu.me/npub187ygerlkw7sth7dj5wmvhsv4gf2tx3j0tfpecsx9tdcu0yfyz60sn24sdn</author_url><provider_name>njump</provider_name><provider_url>https://yabu.me</provider_url><html>Some thoughts on mempool.space back channel fees. &#xA;&#xA;1) it will cripple mempool based fee estimation&#xA;2) hard to know what fee to pay because these &#34;back payments&#34;won&#39;t be included in the block fees. Even though scanning last block fees it won’t be visible. &#xA;3) only mempool.space thing. No open protocol.&#xA;4) mempool space might become central part of the whole network if this will be used heavily. Not good. &#xA;5) No idea why this service when you already can use RBF or CPFP. Probably these RBF and CPFP solutions will also be cheaper as I believe mempool will take some extra cut for this service&#xA;6) business that is doing mempool - fee estimation - is now trying to offer the service that will effect transparency in fee estimations for transaction. &#xA;7) this back channel bump fee also requires trust that third party will bump the fee. In case of RBF no trust is needed.&#xA;&#xA;Anyway it might cause issues only if used heavily by many people.</html></oembed>