From: Erik Aronesty <erik@q32•com>
To: Sergio Demian Lerner <sergio.d.lerner@gmail•com>
Cc: bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] A Segwit2x BIP
Date: Sat, 8 Jul 2017 02:30:03 -0400 [thread overview]
Message-ID: <CAJowKg+E8kJFBPa_q-QMGffpv20hWCeNaH1YYGs3JKELcWejbw@mail.gmail.com> (raw)
In-Reply-To: <CAKzdR-qCmuj02yobAj9YDYq7Ed309z2VUaMtbL_i9vF3zkp5mw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1756 bytes --]
- The BIP91 portion of the fork seems OK to me. There are some issues with
timing, but since this is for miner coordination of segwit activation, and
has little to do with other network users, it could be included as an
option. (I'm a fan of adding options;plugins, etc. to Bitcoin... some
others aren't.)
- This hard fork portion of the proposal is being deployed with "emergency"
speed... even though there is not an emergency on the network today that I
am aware of. If enacted, it will certainly result in two chains - and
with no replay protection.. The results of this will be confusing - two
ledgers with many transactions appearing on both and others appearing only
on one.
- The BIP should be modified to provide evidence and justification for the
timeline that is consistent with the level of risk the network would bear
if it were enacted.
- The coercion used to drive production of this BIP is mired in a
misinterpretation of BIP9 and sets a precedent for Bitcoin that may
undermine the value prospect of all cryptocurrency in general. For this
reason alone - even if all of the engineering concerns and timelines are
improved - even assigning this BIP a number could be considered
irresponsible.
- If you still want to code up a fork for the Bitcoin network, consider
starting with Luke's hard fork code and changing the rates of growth as
needed for your desired effect. Also you might want to read this first
(code references are in there):
https://petertodd.org/2016/hardforks-after-the-segwit-blocksize-increase .
Plans are already underway for a hard fork, for reasons that have nothing
to do with block size, but could include a timeline for a block size growth
consistent with global average residential bandwidth growth.
[-- Attachment #2: Type: text/html, Size: 2011 bytes --]
next prev parent reply other threads:[~2017-07-08 6:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-07 22:25 Sergio Demian Lerner
2017-07-07 22:44 ` Matt Corallo
2017-07-07 23:25 ` Gregory Maxwell
2017-07-07 23:22 ` Gregory Maxwell
2017-07-13 3:10 ` Sergio Demian Lerner
2017-07-13 3:19 ` Sergio Demian Lerner
2017-07-07 23:27 ` Luke Dashjr
2017-07-07 23:38 ` Gregory Maxwell
2017-07-08 6:30 ` Erik Aronesty [this message]
2017-07-08 13:28 ` Btc Drak
[not found] ` <A7FFF8F7-9806-44F1-B68F-F83C44893365@ob1.io>
2017-07-10 11:50 ` Sergio Demian Lerner
2017-07-10 18:38 ` Jorge Timón
2017-07-12 8:15 ` Tom Zander
2017-07-12 12:38 ` Jonas Schnelli
2017-07-12 17:38 ` Jorge Timón
2017-07-13 19:19 ` Sergio Demian Lerner
2017-07-13 19:48 ` Andrew Chow
2017-07-13 21:18 ` Charlie 'Charles' Shrem
2017-07-14 13:50 ` Erik Aronesty
2017-07-12 1:06 ` Luke Dashjr
2017-07-12 15:41 ` Aymeric Vitte
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=CAJowKg+E8kJFBPa_q-QMGffpv20hWCeNaH1YYGs3JKELcWejbw@mail.gmail.com \
--to=erik@q32$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=sergio.d.lerner@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