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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <timon.elviejo@gmail.com>) id 1RTBM2-0004VU-TA
for bitcoin-development@lists.sourceforge.net;
Wed, 23 Nov 2011 11:51:06 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.161.175 as permitted sender)
client-ip=209.85.161.175; envelope-from=timon.elviejo@gmail.com;
helo=mail-gx0-f175.google.com;
Received: from mail-gx0-f175.google.com ([209.85.161.175])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-MD5:128)
(Exim 4.76) id 1RTBM2-0004DR-Az
for bitcoin-development@lists.sourceforge.net;
Wed, 23 Nov 2011 11:51:06 +0000
Received: by ggnh4 with SMTP id h4so1697651ggn.34
for <bitcoin-development@lists.sourceforge.net>;
Wed, 23 Nov 2011 03:51:01 -0800 (PST)
MIME-Version: 1.0
Received: by 10.204.156.208 with SMTP id y16mr23849161bkw.72.1322049060349;
Wed, 23 Nov 2011 03:51:00 -0800 (PST)
Received: by 10.223.132.194 with HTTP; Wed, 23 Nov 2011 03:51:00 -0800 (PST)
In-Reply-To: <201111231130.58785.andyparkins@gmail.com>
References: <201111231035.48690.andyparkins@gmail.com>
<CAGQP0AEXrp3=j8WkQkUzJRhZYF6VxCsFz_ADXE8uz+d2YLfNcw@mail.gmail.com>
<201111231130.58785.andyparkins@gmail.com>
Date: Wed, 23 Nov 2011 12:51:00 +0100
Message-ID: <CAGQP0AEZ9CUNd9ERyMsx741bqjLptY4pPRU6EmxQcD7kR8bdbw@mail.gmail.com>
From: =?ISO-8859-1?Q?Jorge_Tim=F3n?= <timon.elviejo@gmail.com>
To: Andy Parkins <andyparkins@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -0.4 (/)
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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(timon.elviejo[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
2.5 FREEMAIL_REPLY From and body contain different freemails
-1.2 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1RTBM2-0004DR-Az
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Addressing rapid changes in mining power
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: Wed, 23 Nov 2011 11:51:07 -0000
With the current system, the timestamp can also be cheated, but miners
have no direct incentive to do it. With your system, they increase
their probability of mining a block by putting a false timestamp.
Also, where's the network clock you're talking about? Isn't it the
timestamps in the blockchain?
2011/11/23, Andy Parkins <andyparkins@gmail.com>:
> On 2011 November 23 Wednesday, Jorge Tim=F3n wrote:
>> 2011/11/23, Andy Parkins <andyparkins@gmail.com>:
>> > Let's abandon the idea of a target difficulty. Instead, every node ju=
st
>> >
>> > generates the most difficulty block it can. Simultaneously, every no=
de
>> > is listening for "the most difficult block generated before time T";
>> > with T being
>> > picked to be the block generation rate (10 minutes).
>>
>> A miner could try to obtain more difficulty out of time and cheat its
>> reported datetime (T).
>
> Just as with the current system.
>
> The defence is that on receipt of a block, its timestamp is checked again=
st
> the node's own clock and averaged network clock. Blocks out of that band
> are
> rejected.
>
>
> Andy
> --
> Dr Andy Parkins
> andyparkins@gmail.com
>
--=20
Jorge Tim=F3n
|
