<oembed><type>rich</type><version>1.0</version><author_name>npub18gjvug29c4yg46lmplq38e75gg6wn5mn8taytckcsr4jt8p74h3s5knkzl</author_name><author_url>https://nostr.ae/npub18gjvug29c4yg46lmplq38e75gg6wn5mn8taytckcsr4jt8p74h3s5knkzl</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2015-05-08&#xA;📝 Original message:As the author of a popular SPV wallet, I wanted to weigh in, in support of&#xA;the Gavin&#39;s 20Mb block proposal.&#xA;&#xA;The best argument I&#39;ve heard against raising the limit is that we need fee&#xA;pressure.  I agree that fee pressure is the right way to economize on&#xA;scarce resources. Placing hard limits on block size however is an&#xA;incredibly disruptive way to go about this, and will severely negatively&#xA;impact users&#39; experience.&#xA;&#xA;When users pay too low a fee, they should:&#xA;&#xA;1) See immediate failure as they do now with fees that fail to propagate.&#xA;&#xA;2) If the fee lower than it should be but not terminal, they should see&#xA;degraded performance, long delays in confirmation, but eventual success.&#xA;This will encourage them to pay higher fees in future.&#xA;&#xA;The worst of all worlds would be to have transactions propagate, hang in&#xA;limbo for days, and then fail. This is the most important scenario to&#xA;avoid. Increasing the 1Mb block size limit I think is the simplest way to&#xA;avoid this least desirable scenario for the immediate future.&#xA;&#xA;We can play around with improved transaction selection for blocks and&#xA;encourage miners to adopt it to discourage low fees and create fee&#xA;pressure. These could involve hybrid priority/fee selection so low fee&#xA;transactions see degraded performance instead of failure. This would be the&#xA;conservative low risk approach.&#xA;&#xA;Aaron Voisine&#xA;co-founder and CEO&#xA;breadwallet.com&#xA;-------------- next part --------------&#xA;An HTML attachment was scrubbed...&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150508/61a099ec/attachment.html&gt;</html></oembed>