From: "Jorge Timón" <jtimon@jtimon•cc>
To: venzen@mail•bihthai.net
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] A summary list of all concerns related to not rising the block size
Date: Sat, 15 Aug 2015 01:12:08 +0200 [thread overview]
Message-ID: <CABm2gDqH2V0D5XWco9AJ_WNcFUyjkaWGj_oonmKZRocqOvqYVw@mail.gmail.com> (raw)
In-Reply-To: <CABm2gDp92omWk-eg5Sp8u4V8Z9hJcT_TcwyZyaw3Nm4ypLiWXQ@mail.gmail.com>
On Sat, Aug 15, 2015 at 12:35 AM, Jorge Timón <jtimon@jtimon•cc> wrote:
> On Wed, Aug 12, 2015 at 1:21 PM, Venzen Khaosan <venzen@mail•bihthai.net> wrote:
>> 4) General, undefined fear that something bad is going to happen when
>> nodes choke up on a backlog of transactions.
>> - - no specific symptoms are pointed at but presumably there is
>> "pre-traumatic stress" at play.
>> - - Bitcoin-based businesses are going to lose money, customers and
>> potentially fail
>> - - people will flee Bitcoin for another cryptocoin and Bitcoin will be
>> left in the corner, collecting dust and memories of it will fade as
>> SuperCoin with its big blocks becomes all things to all people.
>
> I believe thisbelongs in 2, not really sure if 2.1 or 2.2 since it's
> related to both.
I was tempted to add it as a sub-sub-risk in both, since both things
need to be solved before that stop being a concern. But they may be
more things to do to solve that so I'm listing it as a separate
sub-risk in 2:
2.3) Big list of valid unconfirmed transactions
resulting list:
1) Potential indirect consequence of rising fees.
1.1) Lowest fee transactions (currently free transactions) will become
more unreliable.
1.2) People will migrate to competing systems (PoW altcoins) with lower fees.
1.3) Layer 2 settlements become more expensive
1.4) Less usage than we could have had with a bigger size
1.4.1) More regulation pressure
1.4.2) Not enough fees when subsidy is lower
2) Software problem independent of a concrete block size that needs to
be solved anyway, often specific to Bitcoin Core (ie other
implementations, say libbitcoin may not necessarily share these
problems).
2.1) Bitcoin Core's mempool is unbounded in size and can make the program
crash by using too much memory.
2.2) There's no good way to increase the fee of a transaction that is
taking too long to be mined without the "double spending" transaction
with the higher fee being blocked by most nodes which follow Bitcoin
Core's default policy for conflicting spends replacements (aka "first
seen" replacement policy).
2.3) Big list of valid unconfirmed transactions
next prev parent reply other threads:[~2015-08-14 23:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-12 9:59 Jorge Timón
2015-08-12 11:21 ` Venzen Khaosan
2015-08-14 22:35 ` Jorge Timón
2015-08-14 23:12 ` Jorge Timón [this message]
2015-08-14 23:57 ` Jorge Timón
2015-08-20 21:11 ` Elliot Olds
2015-08-20 21:29 ` Ahmed Zsales
2015-08-12 19:52 ` Elliot Olds
2015-08-14 22:55 ` Jorge Timón
2015-08-15 20:36 ` Elliot Olds
2015-08-13 9:52 ` Ashley Holman
2015-08-13 16:36 ` Jean-Paul Kogelman
2015-08-14 22:57 ` Jorge Timón
2015-08-13 22:01 ` Geir Harald Hansen
2015-08-14 2:26 ` Venzen Khaosan
2015-08-14 11:35 ` Marcel Jamin
2015-08-14 13:48 ` Thomas Zander
2015-08-14 22:59 ` Jorge Timón
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CABm2gDqH2V0D5XWco9AJ_WNcFUyjkaWGj_oonmKZRocqOvqYVw@mail.gmail.com \
--to=jtimon@jtimon$(echo .)cc \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=venzen@mail$(echo .)bihthai.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox