public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Oliver Egginger <bitcoin@olivere.de>
To: Yifu Guo <yifu@coinapex.com>
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Core Devs : can you share your thoughts about all BIPs on this website ?
Date: Fri, 21 Aug 2015 15:18:05 +0200	[thread overview]
Message-ID: <55D7250D.5@olivere.de> (raw)
In-Reply-To: <CAHcfU-U2KHmaDUvtASY5+oHE1OmEzHG8MZcx_ar6uM2oCU5Smw@mail.gmail.com>

Yifu Guo via bitcoin-dev:
> One thing is for sure though, not increasing the blocksize is not an option.

Why not? The blocksize increase eliminates the pressure to seek durable
solutions. But it will turn out differently. Other than we all think.

I really can not imagine that a 20-year plan will be successful. At one
point we like to clear away the auto-increase. I think that is the only
thing for sure at the moment.

I hope that the current protocol and blockchain will be continued.
Perhaps with fewer people. That would settles the matter for the time
being. ;)

- oliver


  reply	other threads:[~2015-08-21 13:18 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-19  4:57 [bitcoin-dev] Core Devs : can you share your thoughts about all BIPs on this website ? Nicolas Dorier
2015-08-21  3:10 ` Btc Drak
2015-08-21  4:45 ` Gregory Maxwell
2015-08-21  5:10   ` Nicolas Dorier
2015-08-21  9:09     ` Btc Drak
2015-08-21  9:32       ` Peter Todd
2015-08-21  9:29   ` Peter Todd
2015-08-21  9:31     ` Btc Drak
2015-08-21  9:35       ` Peter Todd
2015-08-21 10:55         ` Yifu Guo
2015-08-21 11:28           ` Btc Drak
2015-08-21 12:28             ` Yifu Guo
2015-08-21 13:18               ` Oliver Egginger [this message]
2015-08-21 13:34                 ` Will Madden
2015-08-21 17:31                   ` Oliver Egginger
2015-08-21 18:07                     ` Will Madden
2015-08-22  3:02             ` odinn
2015-08-21 16:58         ` Nicolas Dorier
2015-08-21  3:38 Nicolas Dorier
2015-08-21  3:45 ` Eric Lombrozo
2015-08-21  3:54   ` Nicolas Dorier

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=55D7250D.5@olivere.de \
    --to=bitcoin@olivere.de \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=yifu@coinapex.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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