1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
|
Return-Path: <laszlo@heliacal.net>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id EFB1CACC
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 18 Jun 2018 18:58:48 +0000 (UTC)
X-Greylist: delayed 00:09:35 by SQLgrey-1.7.6
Received: from mail3.heliacal.net (mail3.heliacal.net [91.234.48.203])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id A62261A0
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 18 Jun 2018 18:58:48 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heliacal.net;
s=t2678542rf; t=1529347752;
bh=A/mcT0sOBUELu2iZjidZCnMHZyez/o77So4iwTSBjRY=;
h=Subject:To:References:From:Date:In-Reply-To:From;
b=yatgch6nOq+Z7QY+FPKLqSnGIGyrpjne/a04P8NfYrFsZjtCjZGSfO8SCXodjChwE
09lFq7PWyRy0Yor7Ap1Pgk/P4ur3VCetEOUFT7W9Tdzdy3tZOuK9pUYa8Cpt53YWR7
JuNnyuCiQsRlSPQN8yJuHlfpJygwdKRsBB9srG6A=
To: bitcoin-dev@lists.linuxfoundation.org
References: <CAJRVQkDM390Y4sVzA8WwM93PY4UqUa8gvPKkT-iA2UcYL6FQ+g@mail.gmail.com>
From: Laszlo Hanyecz <laszlo@heliacal.net>
Message-ID: <52ead536-d173-f80b-3ffd-b586a591371f@heliacal.net>
Date: Mon, 18 Jun 2018 18:49:09 +0000
MIME-Version: 1.0
In-Reply-To: <CAJRVQkDM390Y4sVzA8WwM93PY4UqUa8gvPKkT-iA2UcYL6FQ+g@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID,DKIM_VALID_AU 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: Mon, 18 Jun 2018 20:44:00 +0000
Subject: Re: [bitcoin-dev] Miner dilution attack on Bitcoin - is that
something plausible?
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: Mon, 18 Jun 2018 18:58:49 -0000
On 2018-06-18 18:34, Артём Литвинович via bitcoin-dev wrote:
> Suppose a malicious actor were to acquire a majority of hash power, and
> proceed to use that hash power to produce valid, but empty blocks.
https://github.com/libbitcoin/libbitcoin/wiki/Empty-Block-Fallacy
|
