<oembed><type>rich</type><version>1.0</version><author_name>npub1fvqfcygrz35axxejv75jecj9vawekqpp7fnf8evq704nga0xge9q8n9kce</author_name><author_url>https://nostr.ae/npub1fvqfcygrz35axxejv75jecj9vawekqpp7fnf8evq704nga0xge9q8n9kce</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2015-06-27&#xA;📝 Original message:On 27/06/2015 03:36, Peter Todd wrote:&#xA;&gt; * Make websites with easy to understand displays of what the current mempool&#xA;&gt;    backlog is, and what fee/KB is needed to get to the front of the queue. We&#39;ve&#xA;&gt;    done a great job for Bitcoin price charts, let&#39;s extend that to transaction&#xA;&gt;    fees.&#xA;&gt;&#xA;+1&#xA;&#xA;This is especially important if take into account all the projects that &#xA;aim to build upon the bitcoin blockchain and that can have a significant &#xA;impact, both in terms of storage space as well as transaction volume spikes.&#xA;&#xA;Just recently I suggested the need for a BIP to standardize reporting of &#xA;&#34;delay alerts&#34; in wallets, so that users can act accordingly (i.e. &#xA;fee-bump, postpone, cancel) before sending their transactions during &#xA;these periods of increased transaction volume.&#xA;&#xA;https://community.blockstack.org/t/blockstore-footprint-on-blockchain/68/5?u=ktorn&#xA;&#xA;IMHO keeping the users informed of potential issues before committing &#xA;transactions to the network can go a long way towards preventing &#xA;frustration and potential backlashes against blockchain tech.&#xA;&#xA;Filipe Farinha</html></oembed>