<div dir="ltr">That's fair, and we've implemented child-pays-for-parent for spending unconfirmed inputs in breadwallet. But what should the behavior be when those options aren't understood/implemented/used?<div><br></div><div>My argument is that the less risky, more conservative default fallback behavior should be either non-propagation or delayed confirmation, which is generally what we have now, until we hit the block size limit. We still have lots of safe, non-controversial, easy to experiment with options to add fee pressure, causing users to economize on block space without resorting to dropping transactions after a prolonged delay.</div><div class="gmail_extra"><br><div><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>Aaron Voisine</div><div>co-founder and CEO<br><a href="http://breadwallet.com" target="_blank">breadwallet.com</a></div></div></div></div></div></div>
<br><div class="gmail_quote">On Fri, May 8, 2015 at 3:45 PM, Mark Friedenbach <span dir="ltr"><<a href="mailto:mark@friedenbach.org" target="_blank">mark@friedenbach.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><span class="">On Fri, May 8, 2015 at 3:43 PM, Aaron Voisine <span dir="ltr"><<a href="mailto:voisine@gmail.com" target="_blank">voisine@gmail.com</a>></span> wrote:<br></span><div class="gmail_extra"><div class="gmail_quote"><span class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">This is a clever way to tie block size to fees.<div><br></div><div>I would just like to point out though that it still fundamentally is using hard block size limits to enforce scarcity. Transactions with below market fees will hang in limbo for days and fail, instead of failing immediately by not propagating, or seeing degraded, long confirmation times followed by eventual success.</div></div></blockquote><div><br></div></span><div>There are already solutions to this which are waiting to be deployed as default policy to bitcoind, and need to be implemented in other clients: replace-by-fee and child-pays-for-parent. <br></div></div></div></div>
</blockquote></div><br></div></div>