path: root/76/82ba433a8f7e860f13a9ecc568c1ee0f678c02

Return-Path: <akaramaoun@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id B42C4E71
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Fri, 14 Sep 2018 17:30:05 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-wm1-f54.google.com (mail-wm1-f54.google.com
	[209.85.128.54])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 771CB80A
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Fri, 14 Sep 2018 17:30:04 +0000 (UTC)
Received: by mail-wm1-f54.google.com with SMTP id s12-v6so2744306wmc.0
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Fri, 14 Sep 2018 10:30:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=mime-version:sender:in-reply-to:references:from:date:message-id
	:subject:to:cc:content-transfer-encoding;
	bh=76PURs5SwKQIXxl4egLw6rRF3v+sXEgCZrxdH4n7sSM=;
	b=swtbwfolOyfFsvQn7wzPaNGD14jDwN/mTmdcJaB32D3y68jlrmuk411q93xzL3xx0I
	HsIHivaHMF3GkCIRqqg1gmm5A+BlofOQIaKX+QPbXiv6hxWsAMSj12K4pQof3D2gPBW4
	p9KW+RUP3XCtKEC5wd8izt24HVepv77d4ZaajEGhWLUAtmNLaWfPhglnP+trofpMwENC
	3cLXiXYGCKlDwyqRmD75vyUwQ9ZwpY2EsOHfH2kH5I0Ms+ou72Xa4w+FJ8UzHRnoA2Ju
	zw828Yj85HaFZ3kRNOJG1I1NSl9whVTYCPZKLI/86etUxjiWakPKJBM4xa6G2+tm+iaZ
	eOfA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:mime-version:sender:in-reply-to:references:from
	:date:message-id:subject:to:cc:content-transfer-encoding;
	bh=76PURs5SwKQIXxl4egLw6rRF3v+sXEgCZrxdH4n7sSM=;
	b=QBa3Uirh325WtpUQES3rQuO9GrqmxNdX5+xeYI/ZepzJ5ZZij0qG5FCxWz9PSlY7ZE
	EM8z47Xa1z64TSynczT0/oq5VNpzsYnYPGLn0lFNzb41Q9NC42LbjQaAO5LM7Mruvnm4
	eD4ngw9P0bZdUbHFsxziHNZuOYsJESfuT+ZSyZQXNzRwprDZeQvUwOx4hF9YFLnd6vUU
	1knHNNiAlHqLUQZ8+JnSymsebaLDAJu8JhKKy/x2d06uiu857Lr60t/HaS83qyEvun51
	F44eBbRIwqyUt6tU1Hqx3zxidszridKBnfWUlElrHwA1qF1mgHIYcS+NcbjRQESQoeQm
	36Bg==
X-Gm-Message-State: APzg51CAnhqZl8KYkMDOYniTkEorcSLBB8Xcz7UIR5kpG8Bd7+VAFwsj
	9TxlchNVRj+V5x9AB3C84DzULt80nPlFxvoyW7E=
X-Google-Smtp-Source: ANB0VdaPm7N52JZdBcyAYmhdAC0WJbhhl1qzCnvfj8V47DTvBYHSm33pmHsK7HiiigwaYmFDPTxel15ZyEt08dkJ7MY=
X-Received: by 2002:a1c:1ec5:: with SMTP id
	e188-v6mr3272139wme.1.1536946202907; 
	Fri, 14 Sep 2018 10:30:02 -0700 (PDT)
MIME-Version: 1.0
Sender: akaramaoun@gmail.com
Received: by 2002:a1c:e1c4:0:0:0:0:0 with HTTP; Fri, 14 Sep 2018 10:30:02
	-0700 (PDT)
In-Reply-To: <CACiOHGzZ3VQVDsRdU6wsC+mqYJ6nTa4sm4snqDNTcR6x5XP2=Q@mail.gmail.com>
References: <CAL8tG=k+kXHMbQdUXO3BXKv7fQwp5t2QuaQut7sPUtEYgwzn0A@mail.gmail.com>
	<CAL8tG=mui_izrob0V66QqNzSJs1Lpbm0xxUYMpzb65-JR9QhRw@mail.gmail.com>
	<CACiOHGzZ3VQVDsRdU6wsC+mqYJ6nTa4sm4snqDNTcR6x5XP2=Q@mail.gmail.com>
From: Andrew <onelineproof@gmail.com>
Date: Fri, 14 Sep 2018 17:30:02 +0000
X-Google-Sender-Auth: NgjsgjyuAL_mtBfJLfG-JmdmmSc
Message-ID: <CAL8tG=kKwjbR4-rOn8K3-=myW5Nx6ugkyPWTTy9c+r0wrA6i0A@mail.gmail.com>
To: Moral Agent <ethan.scruples@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM 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: Fri, 14 Sep 2018 18:37:05 +0000
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
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 <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, 14 Sep 2018 17:30:05 -0000

(reposting to whole list instead of just him) @Moral Agent:
Interesting proposal though it introduces some elements
of proof of stake so it would be more controversial in my view. Also,
something needs to be explained about how this would not create an
attack where difficulty is frequently dropping by 25%, and suddenly we
find ourselves with a very low difficulty and PoW attacks can easily
happen. I need to analyse your proposal more, but I prefer to discuss
it on your blog instead of here just to limit the side topics and
focus only on my proposal.

No one has yet given me a good reason for why not to support my proposal...

On Fri, Sep 14, 2018 at 2:49 PM, Moral Agent <ethan.scruples@gmail.com> wro=
te:
> You might be interested in an idea I wrote about that is in a similar spi=
rit
> here:
>
> https://medium.com/coinmonks/taming-large-miners-with-helper-blocks-6ae67=
ac242f6
>
> From the article:
>
> When a block is solved, it randomly selects one satoshi from the utxo set
> and gives whomever controls that satoshi the power to generate a =E2=80=
=9CHelper
> Block=E2=80=9D. The Helper Block commits to a subset of transactions for =
inclusion
> in the next block. A miner can accept the Helper Block by including the
> suggested transactions and giving the associated transaction fees to a
> payment address specified in the Helper Block. Miners who do not use a
> Helper Block must satisfy a 25% higher difficulty.
>
> On Fri, Sep 14, 2018 at 9:56 AM Andrew via bitcoin-dev
> <bitcoin-dev@lists.linuxfoundation.org> wrote:
>>
>> I discussed this more at bitcointalk:
>> https://bitcointalk.org/index.php?topic=3D4998410.0
>>
>> The attacks I'm interested in preventing are not only selfish mining
>> and collusion, but also more subtle attacks like block withholding,
>> and in general anything that aims to drive out the competition in
>> order to increase hashrate fraction. I also scrapped the idea of
>> changing the block subsidies, and I am only focuses on fees.
>>
>> You can read more about the motivation and details in the bitcointalk
>> thread, but my proposal in short would be to add the concept of
>> "reserve fees". When a user makes a transaction, for each txout
>> script, they can add parameters that specify the fraction of the total
>> fee that is held in "reserve" and the time it is held in "reserve"
>> (can set a limit of 2016 blocks). This "reserve" part of the fee will
>> be paid to miners if the hashrate rises. So if hashrate is currently h
>> and peak hashrate (from past year) is p, then for each period (1 day),
>> a new hashrate is calculated h1, and if h1 > h, then the fraction
>> (h1-h)/p from the reserve fees created in the past 2016 blocks will be
>> released to miners for that period (spread out over the 144 blocks in
>> that period). And this will keep happening as long as hashrate keeps
>> rising, until the "contract" expires, and the leftover part can be
>> used by the owner of the unspent output, but it can only be used for
>> paying fees, not as inputs for future transactions (to save on block
>> space).
>>
>> This should incentivize miners to not drive out the competition, since
>> if they do, there will be less of these reserve fees given to miners.
>> Yes in the end the miners will get all the fees, but with rising
>> hashrate they get an unconditional subsidy that does not require
>> transactions, thus more space for transactions with fees.
>>
>> I can make a formal BIP and pull request, but I need to know if there
>> is interest in this. Now fees don't play such a large part of the
>> block reward, but they will get more important, and this change
>> wouldn't force anything (would be voluntary by each user), just miners
>> have to agree to it with a soft fork (so they don't spend from the
>> anyone-can-spend outputs used for reserve fees). Resource requirements
>> for validation are quite small I believe.
>>
>> On Sat, Sep 1, 2018 at 12:11 AM, Andrew <onelineproof@gmail.com> wrote:
>> > As I understand, selfish mining is an attack where miners collude to
>> > mine at a lower hashrate then with all miners working independently.
>> > What are the current strategies used to prevent this and what are the
>> > future plans?
>> >
>> > One idea I have is to let the block reward get "modulated" according
>> > to peak hashrate. Say p is the peak hashrate for 365 periods (1 year)
>> > consisting of 144 blocks, h is the hashrate of the last 144 block (1
>> > day) period, and r is the base subsidy (12.5 BTC currently). You can
>> > then make the max block reward 0.5 r (1 + h/p). So if hashrate is at
>> > peak you get the full reward. Otherwise you get less, down to a min of
>> > 0.5 r.
>> >
>> > If miners were to collude to mine at a lower than peak hashrate, then
>> > they may be able to do it profitably for 144 blocks, but after that,
>> > the reward would get modulated and it wouldn't be so much in their
>> > interest to continue mining at the lower hashrate.
>> >
>> > What flaws are there with this? I know it could be controversial due
>> > to easier mining present for early miners, so maybe it would have to
>> > be done in combination with a new more dynamic difficulty adjustment
>> > algorithm. But I don't see how hashrate can continue rising
>> > indefinitely, so a solution should be made for selfish mining.
>> >
>> > Also when subsidies stop and a fee market is needed, I guess a portion
>> > of the fees can be withheld for later if hashrate is not at peak.
>> >
>> >
>> > --
>> > PGP: B6AC 822C 451D 6304 6A28  49E9 7DB7 011C D53B 5647
>>
>>
>>
>> --
>> PGP: B6AC 822C 451D 6304 6A28  49E9 7DB7 011C D53B 5647
>> _______________________________________________
>> bitcoin-dev mailing list
>> bitcoin-dev@lists.linuxfoundation.org
>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev



--=20
PGP: B6AC 822C 451D 6304 6A28  49E9 7DB7 011C D53B 5647