Re: [bitcoin-dev] The need for larger blocks

[Aaron Voisine <voisine@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1707 bytes --]

Also remember that the sender is not the one who cares about delays or even
getting confirmations at all, it's the receiver who's concerned with these
things. They have to tell the sender up-front what they're willing to
accept in exchange for goods and services.


Aaron Voisine
co-founder and CEO
breadwallet.com

On Fri, Jun 26, 2015 at 11:13 PM, Filipe Farinha <filipe@ktorn.com> wrote:

> 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
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>

[-- Attachment #2: Type: text/html, Size: 2821 bytes --]