<unnamed>

Public Key

npub1fvqfcygrz35axxejv75jecj9vawekqpp7fnf8evq704nga0xge9q8n9kce

Profile Code

nprofile1qqsykqyuzyp3g6wnrvex02fvufzkwhvmqqslye5nukq086e5whnyvjspzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgqg5waehxw309aex2mrp0yhxgctdw4eju6t0nj7yh2

Publishing to

relay.primal.net

relay.damus.io

Last Notes

2023-06-07 15:40:33 UTC

- reply

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