summaryrefslogtreecommitdiff
path: root/15/7175129c2befd114002f82299f35919d76fe6a
blob: 94e3d3d37e9410fe19d92d5fdd749c03d1c2dffe (plain)
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
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
	helo=mx.sourceforge.net)
	by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <drak@zikula.org>) id 1VdpMs-0008KX-LB
	for bitcoin-development@lists.sourceforge.net;
	Tue, 05 Nov 2013 22:45:02 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of zikula.org
	designates 209.85.212.179 as permitted sender)
	client-ip=209.85.212.179; envelope-from=drak@zikula.org;
	helo=mail-wi0-f179.google.com; 
Received: from mail-wi0-f179.google.com ([209.85.212.179])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1VdpMp-0004fJ-Km
	for bitcoin-development@lists.sourceforge.net;
	Tue, 05 Nov 2013 22:45:01 +0000
Received: by mail-wi0-f179.google.com with SMTP id hm4so2854002wib.0
	for <bitcoin-development@lists.sourceforge.net>;
	Tue, 05 Nov 2013 14:44:53 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20130820;
	h=x-gm-message-state:mime-version:in-reply-to:references:from:date
	:message-id:subject:to:content-type;
	bh=UfGk+tJoht8DhzVzdiqFzch3lUlO6fNnPNoKtQpowso=;
	b=nD84evRaTdQ14RarCM3mI2guyZnVB/blZ775h5UElzSfzZOYeAdNyAu9XfPZlPTFrB
	5XCah9qfVzZM7S/gzSDvYGFKhyIHl4ra39XvcvnHMzzmvwBLaDC58YBvmSp5QOyczw6j
	1KU2Y/0sJs+W2QKJ6pXB8V06+rBRawfRHBv/nXw1LdoygjbqsHivdbqk0RXzfI4k7O5e
	Jtgt3BDqmpKFAYbyr4NnCetgIkglHKxNqM3FX3bpu+BzIXZhrW/JhZwdhP9qIG7oZE3F
	ene+st9EVahaaNpfJWjh0xdb8BDF8Ra3ypG55aQsYDXqXen6Xm3pCP9uTYybhCnor18l
	sW+A==
X-Gm-Message-State: ALoCoQnbYXy030X5pDz0ZVtjgoV5y0AyNfBLFc9nU1AyQP5INXlo6FrHRGcDEqodaEr+NLoKwVBP
X-Received: by 10.180.198.5 with SMTP id iy5mr18567115wic.45.1383689747409;
	Tue, 05 Nov 2013 14:15:47 -0800 (PST)
MIME-Version: 1.0
Received: by 10.194.93.105 with HTTP; Tue, 5 Nov 2013 14:15:27 -0800 (PST)
In-Reply-To: <N1-9eAtMHauq2@Safe-mail.net>
References: <N1-9eAtMHauq2@Safe-mail.net>
From: Drak <drak@zikula.org>
Date: Tue, 5 Nov 2013 22:15:27 +0000
Message-ID: <CANAnSg2sUfRH0mYEir_XKUz-iOYRpdzNgM-AJ7t-H=SOa4wBig@mail.gmail.com>
To: bitcoin-development@lists.sourceforge.net
Content-Type: multipart/alternative; boundary=047d7b624e2adfc61004ea755fe5
X-Spam-Score: -0.5 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
	sender-domain
	-0.0 SPF_PASS               SPF: sender matches SPF record
	0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked.
	See
	http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
	for more information. [URIs: safe-mail.net]
	1.0 HTML_MESSAGE           BODY: HTML included in message
X-Headers-End: 1VdpMp-0004fJ-Km
Subject: Re: [Bitcoin-development] Possible Solution To SM Attack
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Tue, 05 Nov 2013 22:45:02 -0000

--047d7b624e2adfc61004ea755fe5
Content-Type: text/plain; charset=UTF-8

On 5 November 2013 20:51, <colj@safe-mail.net> wrote:

> Possible Solution:
> If N amount of blocks built of the same previous block are received within
> a time frame of T mine on the block with the lowest hash.
>
> Logic:
> In order for Alice to pull of this attack she not only has to propagate
> her blocks first she must also ensure her blocks are of the smallest hash.
>
> Alice would now have to decrease her target to pull of this attack. Since
> she has a lower target it will take her longer to find a valid block
> negating her time advantage.


If I understand the issue properly, this seems like a pretty elegant
solution: if two blocks are broadcast within a certain period of eachother,
chose the lower target. That's a provable fair way of randomly choosing the
winning block and would seem like a pretty simply patch.

Drak

--047d7b624e2adfc61004ea755fe5
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On 5 November 2013 20:51,=C2=A0<span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:colj@safe-mail.net" target=3D"_blank">colj@safe-mail.net</a>&g=
t;</span>=C2=A0wrote:<br><div class=3D"gmail_extra"><div class=3D"gmail_quo=
te"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bor=
der-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:sol=
id;padding-left:1ex">

Possible Solution:<br>If N amount of blocks built of the same previous bloc=
k are received within a time frame of T mine on the block with the lowest h=
ash.<br><br>Logic:<br>In order for Alice to pull of this attack she not onl=
y has to propagate her blocks first she must also ensure her blocks are of =
the smallest hash.<br>

<br>Alice would now have to decrease her target to pull of this attack. Sin=
ce she has a lower target it will take her longer to find a valid block neg=
ating her time advantage.</blockquote><div><br></div><div>If I understand t=
he issue properly, this seems like a pretty elegant solution: if two blocks=
 are broadcast within a certain period of eachother, chose the lower target=
. That&#39;s a provable fair way of randomly choosing the winning block and=
 would seem like a pretty simply patch.</div>

<div><br></div><div>Drak</div></div></div></div>

--047d7b624e2adfc61004ea755fe5--