From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 7FD98360 for ; Fri, 24 Mar 2017 16:27:50 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-it0-f50.google.com (mail-it0-f50.google.com [209.85.214.50]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 40AE719B for ; Fri, 24 Mar 2017 16:27:49 +0000 (UTC) Received: by mail-it0-f50.google.com with SMTP id 190so5840919itm.0 for ; Fri, 24 Mar 2017 09:27:49 -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; bh=MEMIdqBQwA58R8GT5mO/STdql6fxsZplIvnOjTjIdpM=; b=mlGG19VPPk3o8YZcxISdWjB4Su/cq/o9y3EhwwPSv63XUtu6WIrItiO2/P5H6Y1pc0 /ENAtQWdHoQsv/Kb8iCtI1X4/RnF+ARqDlXaMXFhHdFehEojXE/I7zePcELBUngk2NGh +Njk2qDumyhttsVpmA7s8TMmKQVY8J6FmHBa3NfB0zr6Breop5PYSXWazHGf155qqve0 4F4MGH7oY9vlZli9xjHjjF3wdoPKn+XoX1C9rAqFSHM/er3Yys6bvU2LKcLtbQYFeuSR iacWhfdnrpb34xb8d3imaOpgu3EbehjE1Y2G4VZYH8FVW+2QFx82IVqfVUm3ilwbNJjj eufQ== 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; bh=MEMIdqBQwA58R8GT5mO/STdql6fxsZplIvnOjTjIdpM=; b=jsAsg2kx5eOqALD9Hg1nunGLSNEdiHHZv88Iez4CWBL8j+PX9nX8iDT94ULx2NFWAj 6ecgtwSgxkiDrWrISBo6vmL8l00jhMpI1BVcQ3Xjm8Z7XuAulRc4fTZvEN/mBCGBYXWa zjIH7/m7+d79mP3K/dAds3J4a/A5Ie14Z7DtLdW5aD3u8+G276O22GO+6cNDxY9eGdOh gMZEY3K86quMf2IXYJssbsJA+Bzfvfi2hLrvzligHDP3cvMqKZAF4PiOCWiK++mxNqtH dx6LsqJhCoMK+ys9Jnila5eTz9+nwutdqZ+jq5e8k+Oyuo9tGVuHSNwLIQahI9kC/0NZ q4jA== X-Gm-Message-State: AFeK/H2lQB/ga1wdUz0IrRn2jGwGjnjcEciUu4pYWxuTN0e4ogtZ5VqzMZgQRxQH9bYtdUExQ9kj/RpCffQ4CQ== X-Received: by 10.36.40.4 with SMTP id h4mr3813305ith.62.1490372868212; Fri, 24 Mar 2017 09:27:48 -0700 (PDT) MIME-Version: 1.0 Received: by 10.79.162.7 with HTTP; Fri, 24 Mar 2017 09:27:47 -0700 (PDT) Received: by 10.79.162.7 with HTTP; Fri, 24 Mar 2017 09:27:47 -0700 (PDT) In-Reply-To: <5b9ba6c4-6d8f-9c0b-2420-2be6c30f87b5@cannon-ciota.info> References: <5b9ba6c4-6d8f-9c0b-2420-2be6c30f87b5@cannon-ciota.info> From: =?UTF-8?Q?Emin_G=C3=BCn_Sirer?= Date: Fri, 24 Mar 2017 09:27:47 -0700 Message-ID: To: Bitcoin Dev , CANNON Content-Type: multipart/alternative; boundary=001a1143d9fe649fb0054b7c79b2 X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HTML_MESSAGE, HTML_OBFUSCATE_05_10, RCVD_IN_DNSWL_LOW,RCVD_IN_SORBS_SPAM 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: Sat, 25 Mar 2017 04:46:32 +0000 Subject: Re: [bitcoin-dev] Defending against empty or near empty blocks from malicious miner takeover? 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: Fri, 24 Mar 2017 16:27:50 -0000 --001a1143d9fe649fb0054b7c79b2 Content-Type: text/plain; charset=UTF-8 Because there's no consensus on the contents of the mempool, this approach is unsafe and will lead to forks. It also opens a new attack vector where people can time the flood of new transactions with the discovery of a block by a competitor, to orphan the block and to fork the chain. The technical defense against an attacking majority of miners is to change the PoW, effectively moving the community off into a new altcoin where the attackers, hopefully, don't have majority hash power. - egs Sent from my phone, please compensate for autocorrect errors. On Mar 24, 2017 9:06 AM, "CANNON via bitcoin-dev" < bitcoin-dev@lists.linuxfoundation.org> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > When the original white paper was written the idea was that nodes > would be miners at same time. That the distribution of mining power > being mostly on par with the distribution of nodes if I understand > correctly. The problem we face now I fear, is the mining power > becoming centralized. Even if every bitcoin node invested a $1000 > into mining power and mined at a loss, it still would not even > make a dent in hash distribution. Currently there are around 6000 > known nodes. If each node invested $1000 for say 10 ths of hashing > power. At current hashrate of around 3,674,473,142 GH/s this would > only make up %16 of hash power. This is out of balance as while > nodes are distributed mining power is becoming very centralized > due to the creation of monopolization of ASICs. The problem we > are facing is a small group of a couple people whom control a > large amount and growing of hash power. At time of this writing > it has quickly risen to 39% and at current rate will soon become > 50% of hashing power that is controlled by a small group of a few > people. Their intentions are too hijack the bitcoin network to a > cryptocurrency that suits their dangerous agenda. Dangerous because > their plan would centralize power of consensus as I understand it, > to themselves the miners. Dangerous also because the code base of > the attempting subverters is buggy, insecure, and reckless from a > technological standpoint. Even though they only have very minute > amount of nodes compared to legitimate bitcion nodes, the danger > is that they are very quickly taking over in mining power. While > it is true that nodes will not accept invalid blocks that would be > attempted to be pushed by the conspirators, they are threatening to > attack the valid (or in their words, "minority chain") by dedicating > some mining power soley to attacking the valid chain by mining empty > blocks and orphaning the valid chain. So even though the majority > of nodes would be enforcing what blocks are valid and as a result > block the non-compliant longer chain, the conspiring miner can simply > (as they are currently threatening to) make the valid chain unuseable > by mining empty blocks. > > If a malicious miner with half or majority control passes invalid > blocks, the worst case scenario is a hardfork coin split in which > the non-compliant chain becomes an alt. However the problem is that > this malicious miner is very recently threatening to not just simply > fork, but to kill the valid chain to force economic activity to the > adversary controlled chain. If we can simply defend against attacks > to the valid chain, we can prevent the valid chain from dying. > > While empty or near empty blocks would generally be protected by > the incentive of miners to make money. The threat is there if the > malicious miner with majority control is willing to lose out on > these transaction fees and block reward if their intention is to > suppress it to force the majority onto their chain. > > Proposal for potential solution Update nodes to ignore empty blocks, > so this way mined empty blocks cannot be used to DOS attack the > blockchain. But what about defense from say, blocks that are > not empty but intentionally only have a couple transactions > in it? Possible to have nodes not only ignore empty blocks, > but also blocks that are abnormally small compared to number of > valid transactions in mempool? > > For example would be something like this: > If block = (empty OR <%75 of mempool) THEN discard > This threshold just an example. > > What would be any potentials risks > and attacks resulting from both having such new rulesets and not > doing anything? > > Lets assume that the first problem of blocking empty or near empty > blocks has been mitigated with the above proposed solution. How > likely and possible would it be for a malicious miner with lots of > mining power to orphan the chain after so many blocks even with > non empty blocks? Is there a need to mitigate this? > If so is it possible? > > Time is running short I fear. There needs to be discussion on various > attacks and how they can be guarded against along with various > other contingency plans. > > - -- > Cannon > PGP Fingerprint: 2BB5 15CD 66E7 4E28 45DC 6494 A5A2 2879 3F06 E832 > Email: cannon@cannon-ciota.info > > NOTICE: ALL EMAIL CORRESPONDENCE NOT SIGNED/ENCRYPTED WITH PGP SHOULD > BE CONSIDERED POTENTIALLY FORGED, AND NOT PRIVATE. > If this matters to you, use PGP. > -----BEGIN PGP SIGNATURE----- > > iQIcBAEBCgAGBQJY1UH/AAoJEAYDai9lH2mw2QYQALDLBxjdO5WTG7VXfuAE476p > D3o1MMGw23tb+DFUO5WV6aFqfy3VSxbVXz6UuWbj6kHgp3ys6qxg5TX0Dy8tKSZM > V28kovuS/pfen4gTxw1FCNff7YVW1R8QX+cSYxSD5EoEaTbpIPgi8zMusDxUVZk2 > WG3ItoyvkLvoNIYGDcU3gR3UkjDS5lOPiHu5BKSj1dEiibOXhr8JEBCznfUSyxCG > TjVRJaUPlwCU06nad8jAZiDrsW3l866iNkBKaMzMavYuMLvCGIdRkbf54B2ZlIT/ > S/owusxqeIdQpydi/3ydnrqyeWo3znMnn+oOvdvfYEHKLts6gar3Zv8cZ40yYSIE > z7C7GQFIo5TYDUNOk+2VE7NNtdX39Wj3gJql/305miaIt0qMsf1D30ODjePwyxUQ > LQ96ZeF1K/0RSTN5TFvLjV9ZmaaN/tFm3kx0PunptJaZT8d9EgMeHREjCF4di04A > 6Dp3Qeug41X/zdIc2AM387QnPwmGB1TpfrY9qgvcrIe26T6An2V5LHwVmslCX3ui > DYAl0o5ODQqnnakF1FIrr1blMVqm7FqDPQc1I5TfzQuxX2+x+5zdrciPC2HUMCMQ > jMujge5IdGL3kjEwjt+M6kqLu0/T0fhdUetb2DWrRJUcEVoIaiUL7qLJC+4KMR3d > Gu3oWoE1ld+BC6At28AD > =SSuj > -----END PGP SIGNATURE----- > _______________________________________________ > bitcoin-dev mailing list > bitcoin-dev@lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev > --001a1143d9fe649fb0054b7c79b2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Because there's no consensus on the contents of the m= empool, this approach is unsafe and will lead to forks. It also opens a new= attack vector where people can time the flood of new transactions with the= discovery of a block by a competitor, to orphan the block and to fork the = chain.

The technical defense a= gainst an attacking majority of miners is to change the PoW, effectively mo= ving the community off into a new altcoin where the attackers, hopefully, d= on't have majority hash power.

- egs

Sent from my phone, please compensate for autocorrect= errors.

On Mar 24, 2017 9:06 AM, "CANNON via bitcoin-dev" <<= a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.l= inuxfoundation.org> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

When the original white paper was written the idea was that nodes
would be miners at same time. That the distribution of mining power
being mostly on par with the distribution of nodes if I understand
correctly. The problem we face now I fear, is the mining power
becoming centralized. Even if every bitcoin node invested a $1000
into mining power and mined at a loss, it still would not even
make a dent in hash distribution. Currently there are around 6000
known nodes. If each node invested $1000 for say 10 ths of hashing
power. At current hashrate of around 3,674,473,142 GH/s this would
only make up %16 of hash power. This is out of balance as while
nodes are distributed mining power is becoming very centralized
due to the creation of monopolization of ASICs. The problem we
are facing is a small group of a couple people whom control a
large amount and growing of hash power. At time of this writing
it has quickly risen to 39% and at current rate will soon become
50% of hashing power that is controlled by a small group of a few
people. Their intentions are too hijack the bitcoin network to a
cryptocurrency that suits their dangerous agenda. Dangerous because
their plan would centralize power of consensus as I understand it,
to themselves the miners. Dangerous also because the code base of
the attempting subverters is buggy, insecure, and reckless from a
technological standpoint. Even though they only have very minute
amount of nodes compared to legitimate bitcion nodes, the danger
is that they are very quickly taking over in mining power. While
it is true that nodes will not accept invalid blocks that would be
attempted to be pushed by the conspirators, they are threatening to
attack the valid (or in their words, "minority chain") by dedicat= ing
some mining power soley to attacking the valid chain by mining empty
blocks and orphaning the valid chain. So even though the majority
of nodes would be enforcing what blocks are valid and as a result
block the non-compliant longer chain, the conspiring miner can simply
(as they are currently threatening to) make the valid chain unuseable
by mining empty blocks.

If a malicious miner with half or majority control passes invalid
blocks, the worst case scenario is a hardfork coin split in which
the non-compliant chain becomes an alt. However the problem is that
this malicious miner is very recently threatening to not just simply
fork, but to kill the valid chain to force economic activity to the
adversary controlled chain. If we can simply defend against attacks
to the valid chain, we can prevent the valid chain from dying.

While empty or near empty blocks would generally be protected by
the incentive of miners to make money. The threat is there if the
malicious miner with majority control is willing to lose out on
these transaction fees and block reward if their intention is to
suppress it to force the majority onto their chain.

Proposal for potential solution Update nodes to ignore empty blocks,
so this way mined empty blocks cannot be used to DOS attack the
blockchain. But what about defense from say, blocks that are
not empty but intentionally only have a couple transactions
in it? Possible to have nodes not only ignore empty blocks,
but also blocks that are abnormally small compared to number of
valid transactions in mempool?

For example would be something like this:
If block =3D (empty OR=C2=A0 <%75 of mempool) THEN discard
This threshold just an example.

What would be any potentials risks
and attacks resulting from both having such new rulesets and not
doing anything?

Lets assume that the first problem of blocking empty or near empty
blocks has been mitigated with the above proposed solution. How
likely and possible would it be for a malicious miner with lots of
mining power to orphan the chain after so many blocks even with
non empty blocks? Is there a need to mitigate this?
If so is it possible?

Time is running short I fear. There needs to be discussion on various
attacks and how they can be guarded against along with various
other contingency plans.

- --
Cannon
PGP Fingerprint: 2BB5 15CD 66E7 4E28 45DC 6494 A5A2 2879 3F06 E832
Email: cannon@cannon-ciota.info=

NOTICE: ALL EMAIL CORRESPONDENCE NOT SIGNED/ENCRYPTED WITH PGP SHOULD
BE CONSIDERED POTENTIALLY FORGED, AND NOT PRIVATE.
If this matters to you, use PGP.
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJY1UH/AAoJEAYDai9lH2mw2QYQALDLBxjdO5WTG7VXfuAE476p<= br> D3o1MMGw23tb+DFUO5WV6aFqfy3VSxbVXz6UuWbj6kHgp3ys6qxg5TX0Dy8tKSZM<= br> V28kovuS/pfen4gTxw1FCNff7YVW1R8QX+cSYxSD5EoEaTbpIPgi8zMusDxUVZk2<= br> WG3ItoyvkLvoNIYGDcU3gR3UkjDS5lOPiHu5BKSj1dEiibOXhr8JEBCznfUSyxCG<= br> TjVRJaUPlwCU06nad8jAZiDrsW3l866iNkBKaMzMavYuMLvCGIdRkbf54B2ZlIT/<= br> S/owusxqeIdQpydi/3ydnrqyeWo3znMnn+oOvdvfYEHKLts6gar3Zv8cZ40yYSIE<= br> z7C7GQFIo5TYDUNOk+2VE7NNtdX39Wj3gJql/305miaIt0qMsf1D30ODjePwyxUQ<= br> LQ96ZeF1K/0RSTN5TFvLjV9ZmaaN/tFm3kx0PunptJaZT8d9EgMeHREjCF4di04A<= br> 6Dp3Qeug41X/zdIc2AM387QnPwmGB1TpfrY9qgvcrIe26T6An2V5LHwVmslCX3ui<= br> DYAl0o5ODQqnnakF1FIrr1blMVqm7FqDPQc1I5TfzQuxX2+x+5zdrciPC2HUMCMQ<= br> jMujge5IdGL3kjEwjt+M6kqLu0/T0fhdUetb2DWrRJUcEVoIaiUL7qLJC+4KMR3d<= br> Gu3oWoE1ld+BC6At28AD
=3DSSuj
-----END PGP SIGNATURE-----
_______________________________________________
bitcoin-dev mailing list
bitcoin-dev@lists.= linuxfoundation.org
https://lists.linuxfoundation.org= /mailman/listinfo/bitcoin-dev
--001a1143d9fe649fb0054b7c79b2--