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