<oembed><type>rich</type><version>1.0</version><author_name>npub1r3san9v5njl6798hvauyu9ntm6r9c7u8s0t65wls58gpfdcvqp5sa48d0u</author_name><author_url>https://nostr.ae/npub1r3san9v5njl6798hvauyu9ntm6r9c7u8s0t65wls58gpfdcvqp5sa48d0u</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2015-05-08&#xA;📝 Original message:On Fri, May 8, 2015 at 3:43 PM, Aaron Voisine &lt;voisine at gmail.com&gt; wrote:&#xA;&#xA;&gt; This is a clever way to tie block size to fees.&#xA;&gt;&#xA;&gt; I would just like to point out though that it still fundamentally is using&#xA;&gt; hard block size limits to enforce scarcity. Transactions with below market&#xA;&gt; fees will hang in limbo for days and fail, instead of failing immediately&#xA;&gt; by not propagating, or seeing degraded, long confirmation times followed by&#xA;&gt; eventual success.&#xA;&gt;&#xA;&#xA;There are already solutions to this which are waiting to be deployed as&#xA;default policy to bitcoind, and need to be implemented in other clients:&#xA;replace-by-fee and child-pays-for-parent.&#xA;-------------- next part --------------&#xA;An HTML attachment was scrubbed...&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150508/a030d88b/attachment.html&gt;</html></oembed>