summaryrefslogtreecommitdiff
path: root/89/9f8e1ec144df330bddfb9a9a8069a89187a58a
blob: 09869fe1f072a3f3776ebddde083d87747da9709 (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
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 <luke@dashjr.org>) id 1RELUy-0001WK-0P
	for bitcoin-development@lists.sourceforge.net;
	Thu, 13 Oct 2011 13:39:00 +0000
X-ACL-Warn: 
Received: from zinan.dashjr.org ([173.242.112.54])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
	id 1RELUx-0003uq-89 for bitcoin-development@lists.sourceforge.net;
	Thu, 13 Oct 2011 13:38:59 +0000
Received: from ishibashi.localnet (fl-184-4-160-40.dhcp.embarqhsd.net
	[184.4.160.40]) (Authenticated sender: luke-jr)
	by zinan.dashjr.org (Postfix) with ESMTPSA id BA9332040B2
	for <bitcoin-development@lists.sourceforge.net>;
	Thu, 13 Oct 2011 13:38:53 +0000 (UTC)
From: "Luke-Jr" <luke@dashjr.org>
To: bitcoin-development@lists.sourceforge.net
Date: Thu, 13 Oct 2011 09:38:32 -0400
User-Agent: KMail/1.13.7 (Linux/2.6.39-gentoo; KDE/4.6.5; x86_64; ; )
References: <CABsx9T18uavGck3oCj=wkm3fe==N9DOAM+xN21+L8uS=sHb_kw@mail.gmail.com>
In-Reply-To: <CABsx9T18uavGck3oCj=wkm3fe==N9DOAM+xN21+L8uS=sHb_kw@mail.gmail.com>
X-PGP-Key-Fingerprint: CE5A D56A 36CC 69FA E7D2 3558 665F C11D D53E 9583
X-PGP-Key-ID: 665FC11DD53E9583
X-PGP-Keyserver: x-hkp://subkeys.pgp.net
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
Message-Id: <201110130938.35014.luke@dashjr.org>
X-Spam-Score: -0.5 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	-0.5 RP_MATCHES_RCVD Envelope sender domain matches handover relay
	domain
X-Headers-End: 1RELUx-0003uq-89
Subject: Re: [Bitcoin-development] State of Bitcoin Development: October
	Brain Dump
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: Thu, 13 Oct 2011 13:39:00 -0000

On Thursday, October 13, 2011 9:32:48 AM Gavin Andresen wrote:
> =95 Tighten up block-time rules to fix the potential "timejacking" attack.

Once again, this does not fix anything (they're already strict enough for t=
he=20
2-week window), and just creates new problems.

> =95 Work on 'discouraging' blocks/transactions to punish
> bad-for-the-common-good-but-good-for-me behaviors from miners or
> nodes.

=46lawed concept. Only even potentially useful for extreme cases (ie, a min=
er=20
intentionally making lots of 1 MB blocks of junk).