From: David Vorick <david.vorick@gmail•com>
To: "Martin Lízner" <martin.lizner@gmail•com>,
"Bitcoin Dev" <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Hard fork proposal from last week's meeting
Date: Wed, 29 Mar 2017 11:57:19 -0400 [thread overview]
Message-ID: <CAFVRnyr=cYf34X80+dLHwYEPHdqA7mMtYZ_gD6j09C+aM31gQQ@mail.gmail.com> (raw)
In-Reply-To: <CAB-xxiPV9oN1r2hV5a=U1pcYuiZ_qmth-AM-H+1Cjgc2uw-0xA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1401 bytes --]
On Mar 29, 2017 9:50 AM, "Martin Lízner via bitcoin-dev" <
bitcoin-dev@lists•linuxfoundation.org> wrote:
Im tending to believe, that HF is necessary evil now.
I will firmly disagree. We know how to do a soft-fork blocksize increase.
If it is decided that a block size increase is justified, we can do it with
extension blocks in a way that achieves full backwards compatibility for
all nodes.
Barring a significant security motivation, there is no need to hardfork.
I am also solidly unconvinced that increasing the blocksize today is a good
move, even as little as SegWit does. It's too expensive for a home user to
run a full node, and user-run full nodes are what provide the strongest
defence against political manuveuring.
When considering what block size is acceptable, the impact of running
bitcoin in the background on affordable, non-dedicated home-hardware should
be a top consideration.
Disk space I believe is the most significant problem today, with RAM being
the second most significant problem, and finally bandwidth consumption as
the third most important consideration. I believe that v0.14 is already too
expensive on all three fronts, and that block size increases shouldn't be
considered at all until the requirements are reduced (or until consumer
hardware is better, but I believe we are talking 3-7 years of waiting if we
pick that option).
[-- Attachment #2: Type: text/html, Size: 2082 bytes --]
next prev parent reply other threads:[~2017-03-29 15:57 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 16:59 Wang Chun
2017-03-28 17:13 ` Matt Corallo
2017-03-29 8:45 ` Jared Lee Richardson
2017-03-28 17:23 ` Alphonse Pace
2017-03-28 17:31 ` Wang Chun
2017-03-28 17:33 ` Jeremy
2017-03-28 17:50 ` Douglas Roark
2017-03-28 17:33 ` Juan Garavaglia
2017-03-28 17:53 ` Alphonse Pace
2017-03-28 22:36 ` Juan Garavaglia
2017-03-29 2:59 ` Luv Khemani
2017-03-29 6:24 ` Emin Gün Sirer
2017-03-29 15:34 ` Johnson Lau
2017-04-01 16:15 ` Leandro Coutinho
2017-03-29 9:16 ` Jared Lee Richardson
2017-03-29 16:00 ` Aymeric Vitte
2017-03-28 17:34 ` Johnson Lau
2017-03-28 17:46 ` Luke Dashjr
2017-03-28 20:50 ` Tom Zander
2017-03-29 4:21 ` Johnson Lau
2017-03-28 20:48 ` Tom Zander
2017-03-29 6:32 ` Bram Cohen
2017-03-29 9:37 ` Jorge Timón
2017-03-29 19:07 ` Jared Lee Richardson
2017-04-02 19:02 ` Staf Verhaegen
2017-03-29 7:49 ` Martin Lízner
2017-03-29 15:57 ` David Vorick [this message]
2017-03-29 16:08 ` Aymeric Vitte
[not found] ` <CAFVRnyo1XGNbq_F8UfqqJWHCVH14iMCUMU-R5bOh+h3mtwSUJg@mail.gmail.com>
2017-03-29 16:18 ` David Vorick
2017-03-29 16:20 ` Andrew Johnson
2017-03-29 16:25 ` David Vorick
2017-03-29 16:41 ` Andrew Johnson
2017-03-29 17:14 ` Aymeric Vitte
2017-03-29 20:53 ` Jared Lee Richardson
2017-03-29 20:32 ` Jared Lee Richardson
2017-03-29 21:36 ` praxeology_guy
2017-03-29 22:33 ` Aymeric Vitte
2017-03-30 5:23 ` Ryan J Martin
2017-03-30 10:30 ` Tom Zander
2017-03-30 16:44 ` Jared Lee Richardson
2017-03-30 20:51 ` Jared Lee Richardson
2017-03-30 21:57 ` Tom Zander
[not found] ` <CAD1TkXvx=RKvjC8BUstwtQxUUQwG4eiU9XmF1wr=bU=xcVg5WQ@mail.gmail.com>
2017-03-30 10:13 ` Aymeric Vitte
2017-03-29 19:46 ` Jared Lee Richardson
2017-03-29 19:10 ` Jared Lee Richardson
2017-03-29 19:36 ` praxeology_guy
2017-04-02 19:12 ` Staf Verhaegen
2017-03-28 19:56 Paul Iverson
2017-03-28 20:16 ` Pieter Wuille
2017-03-28 20:43 ` Tom Zander
2017-03-28 20:53 ` Alphonse Pace
2017-03-28 21:06 ` Luke Dashjr
2017-03-29 19:33 Daniele Pinna
2017-03-29 20:28 ` Peter R
2017-03-29 22:17 ` Jared Lee Richardson
2017-03-29 20:28 ` David Vorick
2017-03-29 22:08 ` Jared Lee Richardson
2017-03-30 7:11 ` Luv Khemani
2017-03-30 17:16 ` Jared Lee Richardson
2017-03-31 4:21 ` Luv Khemani
2017-03-31 5:28 ` Jared Lee Richardson
2017-03-31 8:19 ` Luv Khemani
2017-03-31 15:59 ` Jared Lee Richardson
2017-03-31 16:14 ` David Vorick
2017-03-31 16:46 ` Jared Lee Richardson
2017-03-31 18:23 ` David Vorick
2017-03-31 18:58 ` Eric Voskuil
2017-04-01 6:15 ` Jared Lee Richardson
2017-03-29 19:50 Raystonn .
2017-03-30 10:34 ` Tom Zander
2017-03-30 11:19 ` David Vorick
2017-03-30 21:42 ` Jared Lee Richardson
2017-03-30 11:24 ` Aymeric Vitte
2017-03-31 21:23 Rodney Morris
2017-03-31 23:13 ` Eric Voskuil
[not found] ` <CABerxhGeofH4iEonjB1xKOkHcEVJrR+D4QhHSw5cWYsjmW4JpQ@mail.gmail.com>
2017-04-01 1:41 ` Rodney Morris
2017-04-01 6:18 ` Jared Lee Richardson
2017-04-01 7:41 ` Eric Voskuil
[not found] ` <CAAt2M1_sHsCD_AX-vm-oy-4tY+dKoDAJhfVUc4tnoNBFn-a+Dg@mail.gmail.com>
[not found] ` <CAAt2M19Gt8PmcPUGUHKm2kpMskpN4soF6M-Rb46HazKMV2D9mg@mail.gmail.com>
2017-04-01 14:45 ` Natanael
[not found] ` <CAD1TkXusCe-O3CGQkXyRw_m3sXS9grGxMqkMk8dOvFNXeV5zGQ@mail.gmail.com>
2017-04-01 18:42 ` Jared Lee Richardson
[not found] ` <CAAt2M1_kuCBQWd9dis5UwJX8+XGVPjjiOA54aD74iS2L0cYcTQ@mail.gmail.com>
[not found] ` <CAAt2M19Nr2KdyRkM_arJ=LBnqDQQyLQ2QQ-UBC8=gFnemCdPMg@mail.gmail.com>
2017-04-01 13:26 ` Natanael
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='CAFVRnyr=cYf34X80+dLHwYEPHdqA7mMtYZ_gD6j09C+aM31gQQ@mail.gmail.com' \
--to=david.vorick@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=martin.lizner@gmail$(echo .)com \
/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