From: Micha Bailey <michabailey@gmail.com>
To: "jl2012@xbt.hk" <jl2012@xbt.hk>
Cc: "bitcoin-dev@lists.linuxfoundation.org"
<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Bitcoin is an experiment. Why don't we have an experimental hardfork?
Date: Tue, 18 Aug 2015 14:57:11 +0300 [thread overview]
Message-ID: <CAAmoQf3OqvHqaGu4UW3ckkhYG91RDHynq+o53HEWa=HccviAiQ@mail.gmail.com> (raw)
In-Reply-To: <d17549688c0c747b2077c1f6f96b6445@xbt.hk>
[-- Attachment #1: Type: text/plain, Size: 671 bytes --]
A smaller block size would make this a soft fork, as unupgraded nodes would
consider the new blocks valid. It would only make things that were allowed
forbidden, which is the definition of a soft fork. For a hard fork, you
need to allow something that was previously invalid.
On Tuesday, August 18, 2015, jl2012 via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
>
> s = 1.5MB. As the 1MB cap was set 5 years ago, there is no doubt that all
> types of technology has since improved by >50%. I don't mind making it a
> bit smaller but in that case not much valuable data could be gathered and
> the second objective of this experiment may not be archived.
>
[-- Attachment #2: Type: text/html, Size: 859 bytes --]
next prev parent reply other threads:[~2015-08-18 11:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-18 9:54 [bitcoin-dev] Bitcoin is an experiment. Why don't we have an experimental hardfork? jl2012
2015-08-18 11:57 ` Micha Bailey [this message]
2015-08-18 18:52 ` Eric Lombrozo
2015-08-18 20:48 ` Danny Thorpe
2015-08-18 20:51 ` Eric Lombrozo
2015-08-18 21:06 ` Danny Thorpe
2015-08-18 21:17 ` Eric Lombrozo
2015-08-18 21:39 ` Danny Thorpe
2015-08-19 9:29 ` Jorge Timón
2015-08-19 10:14 ` odinn
2015-08-19 11:06 ` Jorge Timón
2015-08-19 11:25 ` odinn
2015-08-19 15:22 ` jl2012
2015-08-19 15:48 ` Tier Nolan
2015-08-19 15:25 ` Jorge Timón
2015-08-19 17:30 ` Danny Thorpe
2015-08-19 18:33 ` Jorge Timón
2015-08-18 22:51 ` Ahmed Zsales
2015-08-19 2:53 ` Eric Lombrozo
2015-08-19 9:24 ` Jorge Timón
2015-08-19 10:34 ` jl2012
2015-08-19 10:53 ` 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='CAAmoQf3OqvHqaGu4UW3ckkhYG91RDHynq+o53HEWa=HccviAiQ@mail.gmail.com' \
--to=michabailey@gmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=jl2012@xbt.hk \
/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