From: Eric Lombrozo <elombrozo@gmail•com>
To: "Jorge Timón" <jtimon@jtimon•cc>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Bitcoin XT Fork
Date: Wed, 19 Aug 2015 13:04:16 -0700 [thread overview]
Message-ID: <E3D72CF4-3D1C-4235-87F9-A035AFF28C27@gmail.com> (raw)
In-Reply-To: <CABm2gDpAOQim63Q7r9r-Pv-K+FqizgDHNUmQ7uheGMuMt-e2QA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1383 bytes --]
FWIW,
I would fully like to see the consensus stuff split off into a separate organization from everything else. Let XT continue to support additional p2p messages or relay policies or whatever. Let Mike and Gavin argue for their improved wallet or whatever - I have absolutely no problem with that.
But the consensus code should NOT be subject to the same commit policies…and we should make an effort to separate the two clearly. And we should find a way to communicate the difference succinctly and clearly to laypeople (which is something I think the XT opponents have been horrible at doing so far).
> On Aug 19, 2015, at 12:58 PM, Jorge Timón <jtimon@jtimon•cc> wrote:
>
> On Wed, Aug 19, 2015 at 9:48 PM, Eric Lombrozo via bitcoin-dev
> <bitcoin-dev@lists•linuxfoundation.org> wrote:
>> [...]
>> core devs” and relying on the fact that many people out there can’t seem to
>> tell the difference between a source code fork and a blockchain fork.
>
> And this is precisely why we should make perfectly clear that we're
> not against a code fork where Hearn or anyone else acts as a
> "benevolent dictator", just against the controversial hardfork it is
> attempting to deploy.
> Otherwise the PR battle is probably lost (which may mean users sell
> all their BTC for XTBTC [or just forget about their BTC and only care
> about their XTBTC]).
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 842 bytes --]
next prev parent reply other threads:[~2015-08-19 20:04 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-19 16:53 Adam Back
2015-08-19 17:22 ` Simon Liu
2015-08-19 18:13 ` Peter Todd
2015-08-19 23:37 ` Simon Liu
2015-08-19 17:28 ` Jorge Timón
2015-08-19 17:32 ` Btc Drak
2015-08-19 18:20 ` Peter Todd
2015-08-19 19:15 ` Btc Drak
2015-08-19 19:32 ` odinn
2015-08-19 19:48 ` Eric Lombrozo
2015-08-19 19:58 ` Jorge Timón
2015-08-19 20:04 ` Eric Lombrozo [this message]
2015-08-19 22:00 ` Jorge Timón
2015-08-19 23:07 ` Eric Voskuil
2015-08-19 23:27 ` Jorge Timón
2015-08-19 23:56 ` Jorge Timón
2015-08-20 1:00 ` GC
2015-08-20 1:17 ` Jorge Timón
2015-08-20 0:08 ` Eric Voskuil
2015-08-19 18:22 ` Jorge Timón
2015-08-19 19:12 ` Santino Napolitano
2015-08-19 19:28 ` Eric Lombrozo
2015-08-20 9:00 ` Mike Hearn
2015-08-20 9:13 ` Peter Todd
2015-08-21 3:01 ` odinn
-- strict thread matches above, loose matches on Subject: below --
2015-08-19 8:25 Btc Drak
2015-08-17 20:24 Theo Chino
2015-08-18 4:56 ` Dave Scotese
2015-08-15 17:43 Satoshi Nakamoto
2015-08-15 19:08 ` Laszlo Hanyecz
2015-08-15 19:10 ` jl2012
2015-08-17 11:40 ` Oliver Egginger
2015-08-17 11:44 ` Jorge Timón
2015-08-17 11:51 ` Oliver Egginger
2015-08-17 16:32 ` Jorge Timón
2015-08-17 17:01 ` Oliver Egginger
2015-08-17 17:15 ` Jorge Timón
2015-08-17 17:30 ` Btc Drak
2015-08-17 17:18 ` Gregory Maxwell
2015-08-17 19:14 ` Peter Todd
2015-08-17 17:28 ` Jeff Garzik
2015-08-17 19:03 ` Warren Togami Jr.
2015-08-17 20:37 ` Oliver Egginger
2015-08-18 5:16 ` Gregory Maxwell
2015-08-18 9:15 ` Warren Togami Jr.
2015-08-18 11:52 ` Micha Bailey
2015-08-18 18:57 ` Oliver Egginger
2015-08-18 20:59 ` Anon Moto
2015-08-19 1:03 ` Sergio Demian Lerner
2015-08-17 19:02 ` Anon Moto
2015-08-17 19:40 ` Marcel Jamin
2015-08-17 19:16 ` Hector Chu
2015-08-17 19:28 ` Gregory Maxwell
2015-08-17 19:39 ` Jorge Timón
2015-08-19 2:54 ` odinn
2015-08-19 2:59 ` Angel Leon
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=E3D72CF4-3D1C-4235-87F9-A035AFF28C27@gmail.com \
--to=elombrozo@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=jtimon@jtimon$(echo .)cc \
/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