public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Oliver Egginger <bitcoin@olivere.de>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: [bitcoin-dev] Will there be a freeze of the current protocol version?
Date: Thu, 20 Aug 2015 12:16:57 +0200	[thread overview]
Message-ID: <55D5A919.3030505@olivere.de> (raw)

Hello,

BitPay seems to support BIP 101:

https://medium.com/@spair/increasing-the-block-size-limit-85ff236fc516

We do not know where this is going. But I suspect that ultimately also
the core client will increase the block size.

Bitcoin is also the subject of research. I think that research is much
to slow (and uncertain) for many companies and users. This is the
reason for XT. Nevertheless, I think further research on the base of the
current protocol version is very important. Thus, I hope that the
current block chain survives. Albeit at a lower level with fewer
users. And expressly not to sabotage necessary changes in the main project.

Let's suppose XT prevails or core is changed within the terms of BIP 101:

Do you think that there are enough people to continue with the old
protocol version? Would developers fork a Bitcoin client for supporting
the old nodes with security updates? Or will there be a compatibility
mode in XT, so that XT behave like an old Bitcoin node? What about
smaller but important projects like picocoin?

- oliver


             reply	other threads:[~2015-08-20 10:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-20 10:16 Oliver Egginger [this message]
2015-08-21  3:10 ` [bitcoin-dev] Will there be a freeze of the current protocol version? odinn

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=55D5A919.3030505@olivere.de \
    --to=bitcoin@olivere.de \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    /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