Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 49BB9E25 for ; Mon, 17 Sep 2018 19:36:20 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-pl1-f194.google.com (mail-pl1-f194.google.com [209.85.214.194]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 4A0C142D for ; Mon, 17 Sep 2018 19:36:19 +0000 (UTC) Received: by mail-pl1-f194.google.com with SMTP id u11-v6so7896207plq.5 for ; Mon, 17 Sep 2018 12:36:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=voskuil-org.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Nrv1L6y9kwOdRdQc6e3YqF4CGEnEa7JcqmIQ58umFAs=; b=OR+04l8QU3O8Rrk2nUDgtTUIYw8ccKTG1MhWloV16HH31rvBZT2XlbQ1OXe9rmZiHE IecM9ZEiSkxcE9MAS/pN4zvc4x9Nznaa4i4Q0j+DKUoKbn0tLmKZKOQgA3ulf/ogXEIR owBotuE50TBkCWsm4VHQBu3tPD7vMmnWrv4voVCbz+Y+39hcjUn5kOQ1YxYj8iGs3cJo 7kkBbwjRLM2WGxUwJfb+dVV5sVKayaBCHvQT6WEpM4USfZwjFShXx1xOocQJYfLfJrTk CTDJFYIdOp1THK1jtJhcdDQtRQgg9e18IaJqnXbQspNJ/pCOxBYuJ5qXMlhAPshm7s4F /NMQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Nrv1L6y9kwOdRdQc6e3YqF4CGEnEa7JcqmIQ58umFAs=; b=AcNapmS9vKhOSzzwG48UP/6PVx6k1GgJbNYC+17lI6amtB3SnqSUHUF+CKhH3EROKR uhAWAfOIQnxsZ7EN3l3OhfXrxPURDheb4kJsXDx9T7aXgP9K1FIwE1rCdQeg8aL0hYp6 O11Wdy8dci+jTbAMhxPGkxPNb2/S+xlFs82qseCum2NFrmtyGaV633qQF953vTwnL1dt DfufWKDhck4gM5DKzwYwpkfXPZBNJ/yRtjnpaGJG3qTIeM5ZpcexuyBeTKy0JSkq7VB6 oH3R80wpq0jxRh+geN5v8JJGmGSyVJKEXKSI4frM4Y6nJYwWIQ67/BIAAEalfwL9QbDz R3rQ== X-Gm-Message-State: APzg51BDl5Nh+bFyovd7a5gRulXfLq2B4EvCURgk/H/BuT//KEQqe8+2 1cvpU14lPZVjISNLdmdqtxWp7Q== X-Google-Smtp-Source: ANB0VdYJaBoSWP0ilfS/NVJrNmKamcx3d0eECQGo7eWvnHUVRbzeyR5yrXlkHNnw3p7adF3YteijYA== X-Received: by 2002:a17:902:6ac5:: with SMTP id i5-v6mr26274167plt.232.1537212978722; Mon, 17 Sep 2018 12:36:18 -0700 (PDT) Received: from ?IPv6:2600:380:4478:499a:d987:c483:a891:25c4? ([2600:380:4478:499a:d987:c483:a891:25c4]) by smtp.gmail.com with ESMTPSA id q26-v6sm27513435pfj.127.2018.09.17.12.36.17 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 17 Sep 2018 12:36:17 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) From: Eric Voskuil X-Mailer: iPhone Mail (15G77) In-Reply-To: Date: Mon, 17 Sep 2018 12:36:15 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <49CC1792-9397-4506-B2FC-F3B6C14EA355@voskuil.org> References: To: Andrew X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, MIME_QP_LONG_LINE, RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org X-Mailman-Approved-At: Tue, 18 Sep 2018 04:32:16 +0000 Cc: Bitcoin Protocol Discussion Subject: Re: [bitcoin-dev] Selfish Mining Prevention X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Sep 2018 19:36:20 -0000 > Once hashrate gets large enough, no new miners (additional hashrate) will want to join since their share of the hashrate is too small to make a profit. The share (hash power) of a miner is proportional to capital investment, not= the newness of that investment. The efficiency of a new mine (inclusive of p= ooling pressures) can certainly be sufficient to outperform other miners, re= sulting in the departure of the latter, thus not preventing the entry of the= former. The point you should be making here is that energy consumption is regulated b= y the cost of capital (in addition to reward value and the cost of energy). Note that higher efficiency mining does not reduce energy consumption, nor d= oes variation in the necessary cost of mining hardware. The total energy cos= t is the control, not the hash rate. This is of course why proof-of-memory (= space) is pointless. It simply shifts most of the energy cost to hardware ma= nufacture, shipment, etc. e On Sep 17, 2018, at 06:18, Andrew wrote: >> I see what you say, however, since the proposal as I have read it says "A= nd this will keep happening as long as hashrate keeps rising," - what actual= ly happens in the case hashrate stagnates or falls? >=20 > In general, a target hashrate can be set by users (can be less or more > than the peak hashrate). As long as hashrate is rising and still > didn't reach the target, miners will incrementally get the reserve > fees. Once the "contract" times out, the remaining part can be used as > fees by the users who created the reserve fee "contract". So if > hashrate remains the same or falls, then users get the reserve fees > back. >=20 > I agree that we can't stop people from being greedy. If they are not > Bitcoin mining, they will try to put their energy to earn in some > other way...The hashrate is related the demand for Bitcoin (price) and > the amount of fees/subsidies the miners will get paid. For every level > of mining rewards (based on demand) there exists a limit on the > hashrate. Once hashrate gets large enough, no new miners (additional > hashrate) will want to join since their share of the hashrate is too > small to make a profit. >=20 > Also with merge mining and proof of space we can be quite efficient in > the future. But of course I sympathize with the "don't be greedy" > philosophy, and it can be good to educate people to use less resources > than they need, just I think it's a bit outside of the scope of what > the Bitcoin software protocol does.