path: root/5d/de0ac52e473df2789aef837421ca87efdf54e6

Return-Path: <s7r@sky-ip.org>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id E5004A1A
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed, 19 Aug 2015 15:42:13 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from outbound.mailhostbox.com (outbound.mailhostbox.com
	[162.222.225.19])
	by smtp1.linuxfoundation.org (Postfix) with ESMTP id 45394F2
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed, 19 Aug 2015 15:42:06 +0000 (UTC)
Received: from [0.0.0.0] (torproxy01.31173.se [185.65.135.226])
	(using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits))
	(No client certificate requested)
	(Authenticated sender: s7r@sky-ip.org)
	by outbound.mailhostbox.com (Postfix) with ESMTPSA id 19228784314;
	Wed, 19 Aug 2015 15:41:59 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sky-ip.org;
	s=20110108; t=1439998922;
	bh=q8po8ucrzc4nF9CcUJ8sNyLV+XRVvZ9VEoNkA4kMzms=;
	h=Reply-To:Subject:References:To:Cc:From:Date:In-Reply-To;
	b=IlsQ5Ap6OPb35OXzQwrbDKNU6jZ9jaZAJ8An9tGD1aVYKsqsEcuN/LPduaRaMWwgm
	hlVKCyhNCBgYwYt7WyvG+CFzumzc+i8e1e3rvaWED8sImL29A3FfIXIUZKj90pj9Hx
	co0PG+LbfkoZqcAUxpzEhCr3tRn3QTlzAqWEKtoY=
Reply-To: s7r@sky-ip.org
References: <CADWuND3EfO6YO3g4H09_mWhrHC4PX4SZpTTuETiX2PyCxSRCsQ@mail.gmail.com>
	<55D1167B.1060107@gmail.com>
	<CAEX2NSfaPv0g07hfT31voGWX05Z6uaBsZOjhMkOwBr4mdHbPQw@mail.gmail.com>
	<55D124D7.4050209@gmail.com>
	<61AD0CE6-014E-44E2-B9C7-00B35D2E09CC@petertodd.org>
	<CAEX2NSeAgrN877zAVDrk_J+7EVDPagt8u4+HB7hDMVMPwS6Zng@mail.gmail.com>
	<F99FFEE6-6D10-480D-B96D-960B84092C88@gmail.com>
	<CABm2gDoEVmqiOpPcf1wUsNt4pmU=oVawq2-0YwrEjm1W1YBmeg@mail.gmail.com>
To: =?UTF-8?Q?Jorge_Tim=c3=b3n?= <jtimon@jtimon.cc>,
	Eric Lombrozo <elombrozo@gmail.com>
From: s7r <s7r@sky-ip.org>
X-Enigmail-Draft-Status: N1010
Message-ID: <55D4A3BD.2060706@sky-ip.org>
Date: Wed, 19 Aug 2015 18:41:49 +0300
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101
	Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <CABm2gDoEVmqiOpPcf1wUsNt4pmU=oVawq2-0YwrEjm1W1YBmeg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
X-CTCH-RefID: str=0001.0A020201.55D4A3CB.01F2, ss=1, re=0.000, recu=0.000,
	reip=0.000, cl=1, cld=1, fgs=0
X-CTCH-VOD: Unknown
X-CTCH-Spam: Unknown
X-CTCH-Score: 0.000
X-CTCH-Rules: 
X-CTCH-Flags: 0
X-CTCH-ScoreCust: 0.000
X-CTCH-SenderID: s7r@sky-ip.org
X-CTCH-SenderID-TotalMessages: 1
X-CTCH-SenderID-TotalSpam: 0
X-CTCH-SenderID-TotalSuspected: 0
X-CTCH-SenderID-TotalBulk: 0
X-CTCH-SenderID-TotalConfirmed: 0
X-CTCH-SenderID-TotalRecipients: 0
X-CTCH-SenderID-TotalVirus: 0
X-CTCH-SenderID-BlueWhiteFlag: 0
X-CMAE-Score: 0
X-CMAE-Analysis: v=2.1 cv=YL9iskyx c=1 sm=1 tr=0
	a=ceO5iDd/nFDcJFZ6yUMShQ==:117 a=ceO5iDd/nFDcJFZ6yUMShQ==:17
	a=-NIMs_s3AAAA:8 a=bvjBBkZ6AAAA:8 a=6PzwTDcoQqoA:10 a=IkcTkHD0fZMA:10
	a=ag1SF4gXAAAA:8 a=yVV3LOsx-XESrndnYosA:9 a=u2oda74I9aoFMtzr:21
	a=hTm2brU5If_SBZy3:21 a=QEXdDO2ut3YA:10
X-Spam-Status: No, score=-0.3 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,URIBL_BLACK autolearn=no version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.org
Cc: Cameron Garnham via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Bitcoin XT 0.11A
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Aug 2015 15:42:14 -0000

Hello Jorge, Eric,

With all this noise on the -dev mail list I had to implement application
level filters so I can treat with priority posts from certain people,
you are on that list. While I agree with your arguments, I think it is
_very_ important to highlight some things. I am neither for the
blocksize increase neither against it, because plain and simple I don't
have enough arguments to take some definitive decision on this topic.
What I am angry about is spreading FUD that a fork could kill Bitcoin
and what we are experiencing now is somehow terrible.

1. Bitcoin XT is not necessarily an attack over Bitcoin and will not
split it into 2 different coins. It is the result of an open source free
system which lacks centralization. It is just at early stage, it could
have thousands for forks (or fork attempts) during its life.

2. We have no proof that Mike Hearn and Gavin Andresen are trying to do
something bad to Bitcoin. So far everything they have done is (or should
be) allowed. They have forked an open source software and implemented a
voting system for a consensus rule change - doesn't sound like they are
committing a crime here (either legally or morally). If they are
qualified enough to maintain the software, or if the decision is
technically correct or not is another story, and it should only matter
to whoever uses / wants to use -XT.

3. If Bitcoin's value can be decreased (or Bitcoin as a project killed)
just by 2 people forking the software and submitting a consensus rule to
a vote, it means Bitcoin is dead already and it should be worthless! We
can't go around and panic every time somebody forks Bitcoin and tries to
change something - this should be allowed by the nature of its license.
If tomorrow 5 more people fork 5 different software implementing the
bitcoin protocol and submit 5 different new consensus rules to a vote,
then what? We should all sell so the price will drop to 1 cent, because
it is somehow not good enough, not stable enough?

I can fork tomorrow Bitcoin Core to a Bitcoin-XYZ software which at some
block in the future spends all the longest dusted coins to me, out of
which I give away 50% to the miners (so the hashing power will have
incentive to use my fork).

Can they do it? YES
Will they do it? NO
Should the world care about this? NO

It's as simple as that. We cannot continue to panic that "Bitcoin as a
project" is at threat because somebody forked it.

4. By having a software fork and consensus rule submitted to vote we
actually prove how open Bitcoin is, and how there is lack of control
over it from all parties (developers, miners, engineers on the mail
list). This is reason to increase Bitcoin's value! It is a feature, not
a flaw!


It's very important for everyone in the ecosystem to understand:

- yes, Bitcoin is open source, even you can fork it tomorrow if you want
and you think enough users might follow you.

- no, it's not a requirement for 100% of the nodes in the network to be
running Core, or -XT or other implementation. The more we have, the better.

- yes, there is absolutely no authority in Bitcoin - this is what lead
to this dispute in the first place. This is the truly decentralized
nature of the software, not important if we have 10.000 full nodes or
1000 full nodes.

- no, Bitcoin won't split / die or whatever because of this fork.
Regardless what it happens, if XT will reach the threshold or not,
Bitcoin will go on just because it has some unique advantages and has no
competitor from some points of view.

- Bitcoin by its design has many many advantages, but also the
limitation that it relies on majority being honest / doing the right
thing! This is just the way it is, and the benefits it is offering
heavily win over this fundamental limitation.

On 8/19/2015 1:09 PM, Jorge Timón via bitcoin-dev wrote:
> On Mon, Aug 17, 2015 at 1:02 AM, Cameron Garnham via bitcoin-dev
> <bitcoin-dev@lists.linuxfoundation.org> wrote:
>> I think that it is important to note that Bitcoin XT faces a natural
>> uphill battle.
>>
>> Since it is possible to setup atomic inter-fork coin trades. I do not
>> see how Bitcoin XT could possibly win if Satoshi decides to sell 10000
>> XTBTC for BTC everyday for the first 100 days after the fork.
>>
>> In many ways Satoshi gets to decide the winning fork just by his huge
>> economic investment in Bitcoin.
>>
>>
>> Here is some simple game-theory for non-consensus forks:
>>
>> 1. Spoil the ballot. Have Bitcoin Core propagate the Bitcoin XT version
>> string.
>>
>> 2. Encourage all miners to false vote for the Bitcoin XT fork.
>>
>> - Now people have no-idea what % of the economy Bitcoin XT holds. -
>> Making it impossible for people to put economic faith behind Bitcoin XT.
>>
>> 3. Setup good Atomic Swap markets.
>> [...]
>> The price for XTBTC coins will plummet, Satoshi progressively dumping
>> his 1M stash over a year or it so will make sure that it doesn't recover
>> either.
> 
> Some XTBTC advocates may sell all their BTC for XTBTC and viceversa.
> But I'm afraid that what most currency speculators (thus most Bitcoin
> holders) will do is just sell both all their BTC and XTBTC for fiat,
> and wait for things to settle before deciding whether to re-enter or
> not.
> This could result in both currencies' prices going down to 1 usd cent,
> nobody knows.
> 
>> I cannot see how Bitcoin XT is but-not in a extremely weak position from
>> game theory.
> 
> Unfortunately it also puts Bitcoin core in an extremely weaker
> position than it was before the Schism hardfork.
> Even if XT fails in making blocks bigger, it may destroy Bitcoin.
> That's probably not the goal of Bitcoin XT, but I don't think Andresen
> and Hearn fully undesrtand the risks of a Schism hardfork (not to
> mention their "followers" in the interwebs).
> 
> Since we want to discard the assumption that Hearn and Andresen want
> to make Bitcoin centralized or destroy it, it's reasonable to conclude
> that have serious misunderstandings on how the global consensus works.
> This is consistent with some of their strong positions on Bitcoin Core
> policy defaults (like maintaining the first seen spending-conflict
> replacement policy [the dumbest possible one after "last seen"]
> forever).
> 
> On Mon, Aug 17, 2015 at 2:33 PM, Eric Lombrozo via bitcoin-dev
> <bitcoin-dev@lists.linuxfoundation.org> wrote:
>> Or can’t you create a transaction that’s still within the op count and sig ops limits but is larger than 1MB?
> 
> Yes, it seems the simplest way to permanently separate your BTC from
> your XTBTC is to move them all in transactions bigger than 1MB. You
> may need too many outputs to increase the size (thus also hurting the
> utxo size in Bitcoin XT), but that's just a side effect.