path: root/65/01c89589a0e01de0e7d83986497e2ad7a36feb

Return-Path: <wordsgalore@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id A07A4958
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Fri, 13 Oct 2017 11:35:12 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-wm0-f67.google.com (mail-wm0-f67.google.com [74.125.82.67])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 8764D149
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Fri, 13 Oct 2017 11:35:11 +0000 (UTC)
Received: by mail-wm0-f67.google.com with SMTP id t69so20716054wmt.2
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Fri, 13 Oct 2017 04:35:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to
	:cc; bh=MGFXbYeCvUw83RMBNHXrdMZg9lgyBUXL+vKWmxoy1wI=;
	b=fAI2TI49xYi0qaJRmaWzEd1uPPRRPvmTfs26uRMQgmNQrS7kinRQjPONdH2w5PeYx1
	MeYruE31UhlArP1YGhF7F1vwpeZbRi2BSvLnD5RGtAEXkzZS7zEDPb3iI++cktV7Y+7m
	Is+TzIMMO3fqr2r7PD6xNZ0u0oECYYe8K/RR/yR88MjvItV+S9gP72FIfBN9PhrQ54mr
	XX7qhwWHIQ451fWYAOh+xVZ7BeasLZVX4/MLnyUrMqAMo7m7GCByLAauh0KxmJfZKeOD
	Y3TORM3LU3nVEVsZFpeNyrQuKVzHwVMPBDQtcv6w+Rs76jF/QqXXYPb68rXwHAyXgmR7
	M31w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:mime-version:in-reply-to:references:from:date
	:message-id:subject:to:cc;
	bh=MGFXbYeCvUw83RMBNHXrdMZg9lgyBUXL+vKWmxoy1wI=;
	b=D3dLrQ9tCMTStJ8hyWovBC5n7tQSYin73gex1bGqjDNHzQ+z1FzLSniTmPBztflH63
	U/EWJdxMXdQkqyXujR2uTYxJtm9952gV4XBwnKF5z6QKjwxHZdYlmfBtvhoU3OUXx9pO
	SJZAUmrSy12IRB6z9Gz8JIxuoRQ06Clew6FGQulZUUxfnXmxJGkgwN/BWVaQ8PqFlwDI
	HC4q1/X+bY9FrezO96gyIFmNxUsFbUUSA/9vFcGjPSw5PvFJAzVZGl4zeyrXaxJl197X
	CfOhKOJDTZPxyesrb/sgUXpYNbOEWNAAcquy7m8eQbkI3nl2Qm18rkuktXjn/ATNob+3
	tc8w==
X-Gm-Message-State: AMCzsaW7ch1o1vslTH6Neod3QvWwE0FvavlNJEuZAqk7IhtfSBAvfRAO
	enq/SH/sKHjhNPTXc9I4KyEqSNdW7Dzm2PgFH+/foQ==
X-Google-Smtp-Source: AOwi7QD7zNFxPdKHTdWdS3LjiwLXLawkEOhAaGSaH3lMQOV0KurqRbJUSj2uin6RDVjukdQwml3kvjR5O1OieRLygLc=
X-Received: by 10.80.243.145 with SMTP id g17mr1774719edm.42.1507894509893;
	Fri, 13 Oct 2017 04:35:09 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.80.173.10 with HTTP; Fri, 13 Oct 2017 04:35:09 -0700 (PDT)
In-Reply-To: <Hr8ORNHzR76wNhJHoagwXi2ewQ1qYSZScH0xeltVnqid2ljOowc2bj8-rkbdukpk9eyoPx1ReOZSUsNrcowRU9gL5UbKtblkQn2SUo06BHE=@protonmail.com>
References: <CADtTMvnr8SgSxV1Qcorv28TY=fR1yJdtAEtjkYvPJQ7pm8dBMQ@mail.gmail.com>
	<Hr8ORNHzR76wNhJHoagwXi2ewQ1qYSZScH0xeltVnqid2ljOowc2bj8-rkbdukpk9eyoPx1ReOZSUsNrcowRU9gL5UbKtblkQn2SUo06BHE=@protonmail.com>
From: Scott Roberts <wordsgalore@gmail.com>
Date: Fri, 13 Oct 2017 07:35:09 -0400
Message-ID: <CADtTMvnrZp=JD4rkXQOZAPNS9BMNMqnTyfA65PRzZhWs+VxgHA@mail.gmail.com>
To: ZmnSCPxj <ZmnSCPxj@protonmail.com>
Content-Type: text/plain; charset="UTF-8"
X-Spam-Status: No, score=0.4 required=5.0 tests=DKIM_SIGNED,DKIM_VALID,
	DKIM_VALID_AU,FREEMAIL_FROM,LOTS_OF_MONEY,RCVD_IN_DNSWL_NONE,
	RCVD_IN_SORBS_SPAM,T_MONEY_PERCENT autolearn=disabled version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.org
X-Mailman-Approved-At: Fri, 13 Oct 2017 11:52:53 +0000
Cc: "bitcoin-dev@lists.linuxfoundation.org"
	<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] New difficulty algorithm part 2
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol 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: Fri, 13 Oct 2017 11:35:12 -0000

Yes, the current price ratio indicates there is no need for a new
difficulty algorithm. I do not desire to fork before a disaster, or to
otherwise employ a new difficulty before a fork is otherwise needed.

A 2-week delay in difficulty response is a 2 week error in
measurement. Slow response generally means less intelligence.

My goal is not to have a bunch of BTC clones that merchants and buyers
use equally, but to have a  better difficulty algorithm in place to be
used in the next BTC "Core" fork. If not for the current situation,
then for future security.

>  This is a massive departure from the conception of Bitcoin as having a fixed limit and effectively becoming deflationary.

You mean multiple forks is inflationary. The current limit in quantity
is deflationary because the use of the coin is rising faster than its
mining is producing (see velocity of money). Constant value is defined
as being neither. Bitcoin's deflationary quality created a massive
marketing advantage as well as paid the creator about million dollars
an hour. If it suddenly were able to be a constant value coin, its use
in the marketplace and as a real store of value would skyrocket and
the cries of "Ponzi scheme" would stop. The trick is in determining
constant value without a 3rd party such as an index of a basket of
commodities (which both Keynes and von Mises wanted, but was scuttled
by the U.S. at Bretton Woods).

On Fri, Oct 13, 2017 at 12:45 AM, ZmnSCPxj <ZmnSCPxj@protonmail.com> wrote:
> Good morning,
>
>
>>ZmnSCPxj wrote:
>>> Thus even if the unwanted chain provides 2 tokens as fee per block,
>>> whereas the wanted chain provides 1 token as fee per block, if the
>>> unwanted chain tokens are valued at 1/4 the wanted chain tokens, miners
>>> will still prefer the wanted chain regardless.
>>
>>This is a good point I was not thinking about, but your math assumes
>>1/2 price for a coin that can do 2x more transactions. Holders like
>>Roger Ver have an interest in low price and more transactions. A coin
>>with 2x more transactions, 22% lower price, and 22% lower fees per
>>coin transferred will attract more merchants, customers, and miners
>>(they get 50% more total fees) and this will in turn attract more
>>hodlers and devs. This assumes it outweighs hodler security concerns.
>>Merchants and customers, to the extent they are not long term hodlers,
>>are not interested in price as much as stability, so they are somewhat
>>at odds with hodlers.
>
> As of this moment, BT1 / BT2 price ratio in BitFinex is slightly higher than
> 7 : 1.  Twice the transaction rate cannot overcome this price ratio
> difference.  Even if you were to claim that the BitFinex data is off by a
> factor of 3, twice the transaction rate still cannot overcome the price
> ratio difference.  Do you have stronger data than what is available on
> BitFinex?  If not, your assumptions are incorrect and all conclusions
> suspect.
>
>
>>Bitcoin consensus truth is based on "might is right". Buyers and
>>sellers of goods and services ("users") can shift some might to miners
>>via fees, to the chagrin of hodlers who have more interest in security
>>and price increases. Some hodlers think meeting user needs is the
>>source of long term value. Others think mining infrastructure is.
>
> Mining infrastructure follows price.  If bitcoins were still trading at 1
> USD per coin, nobody will build mining infrastructure to the same level as
> today, with 5000 USD per coin.
>
> Price will follow user needs, i.e. demand.
>
>>You
>>seem to require hodlers to correctly identify and rely solely on good
>>developers.
>
> For the very specific case of 2X, it is very easy to make this
> identification.  Even without understanding the work being done, one can
> reasonably say that it is far more likely that a loose group of 100 or more
> developers will contain a few good or excellent developers, than a group of
> a few developers containing a similar number of good or excellent
> developers.
>
> User needs will get met only on the chain that good developers work on.
> Bitcoin today has too many limitations: viruses on Windows can steal all
> your money, fee estimates consistently overestimate, fees rise during
> spamming attacks, easy to lose psuedonymity, tiny UTXOs are infeasible to
> spend, cannot support dozens of thousands of transactions per second.
> Rationally, long-term hodlers will select a chain with better developers who
> are more likely to discover or innovate methods to reduce, eliminate, or
> sidestep those limitations.  Perhaps the balance will change in the future,
> but it is certainly not the balance now, and thus any difficulty algorithm
> change in response to the current situation will be premature, and far more
> likely to cause disaster than avert one.
>
>>Whatever combination of these is the case, bad money can
>>still drive out good, especially if the market determination is not
>>efficient.
>>
>>A faster measurement of hashrate for difficulty enables the economic
>>determination to be more efficient and correct. It prevents the
>>biggest coin from bullying forks that have better ideas. Conversely,
>>it prevents miners from switching to an inferior coin simply because
>>it provides them with more "protection money" from fees that enables
>>them to bully Bitcoin Core out of existence, even in the presence of a
>>slightly larger hodler support.
>
> This requires that all chains follow the same difficulty adjustment: after
> all, it is also entirely the possibility that 2X will be the lower-hashrate
> coin in a few months, with the Core chain bullying them out of existence.
> Perhaps you should cross-post your analysis to bitcoin-segwit2x also.  After
> all, the 2X developers should also want to have faster price discovery of
> the true price of 2X, away from the unfavorable (incorrect?) pricing on
> BitFinex.
>
>>Devs are a governing authority under the influence of users, hodlers,
>>and miners. Miners are like banks lobbying government for higher total
>>fees. Hodlers are the new 1%, holding 90% of the coin, lobbying both
>>devs and users for security, but equally interested in price
>>increases. Users are "the people" that devs need to protect against
>>both hodlers and miners. They do not care about price as long as it is
>>stable. They do not want to become the 99% owning 10% of the coin or
>>have to pay unecessary fees merely for their coin to be the biggest
>>bully on the block. A faster responding difficulty will take a lot of
>>hot air out of the bully. It prevents miners from being able to
>>dictate that only coins with high fees are allowed. They are less
>>able to destroy small coins that have a fast defense.
>>
>>The 1% and banks would starve the people that feed them to death if
>>they were allowed complete control of the government. Are hodlers and
>>miners any wiser?
>
> Are developers any wiser, either?
>
> Then consider this wisdom: The fewer back-incompatible changes to a coin,
> the better.  Hardforks of any kind are an invitation to disaster and, at
> this point, require massive coordination effort which cannot be feasibly
> done within a month.  Fast market determination can be done using off-chain
> methods (such as on-exchange trades), and are generally robust against
> temporary problems on-chain, although admittedly there is a counterparty
> risk involved.  The coin works, and in general there is usually very little
> need to fix it, especially using dangerous hardforks.
>
>>Devs need to strive for an expansion of the coin
>>quantity to keep value constant which is the foundation of the 5
>>characteristics of an ideal currency.
>
> Is that your goal?  This is a massive departure from the conception of
> Bitcoin as having a fixed limit and effectively becoming deflationary.  It
> will also lead to massive economic distortions in favor of those who receive
> newly-minted coins.  I doubt any developer would want to have this property.
>
> Regards,
> ZmnSCPxj