summaryrefslogtreecommitdiff
path: root/3c/bbd6a9b11efe87c3e6137dabe7b177c15b0f67
blob: 676c9694952f36d39f324d8cb09de7698ca32c1c (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
Return-Path: <jl2012@xbt.hk>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 579C9B75
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed, 14 Dec 2016 11:12:56 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from sender163-mail.zoho.com (sender163-mail.zoho.com
	[74.201.84.163])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id DC7AAA0
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed, 14 Dec 2016 11:12:55 +0000 (UTC)
Received: from [172.21.35.100] (223.197.116.5 [223.197.116.5]) by
	mx.zohomail.com with SMTPS id 1481713969429329.72784879231926;
	Wed, 14 Dec 2016 03:12:49 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Johnson Lau <jl2012@xbt.hk>
In-Reply-To: <201612141107.16613.luke@dashjr.org>
Date: Wed, 14 Dec 2016 19:12:45 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <58C5DFB7-BFC8-4B88-8B4B-0449E9DC6177@xbt.hk>
References: <FB8593E6-3CD7-46D5-8FC8-A73A0EF1AE9A@xbt.hk>
	<22457494.p1MjVfM24j@cherry>
	<8690A056-F1F9-480A-8C95-E1BF3D8417B2@xbt.hk>
	<201612141107.16613.luke@dashjr.org>
To: Luke Dashjr <luke@dashjr.org>
X-Mailer: Apple Mail (2.3124)
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE
	autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.org
Cc: bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Forcenet: an experimental network with a new
	header format
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: Wed, 14 Dec 2016 11:12:56 -0000


> On 14 Dec 2016, at 19:07, Luke Dashjr <luke@dashjr.org> wrote:
>=20
> On Wednesday, December 14, 2016 11:01:58 AM Johnson Lau via =
bitcoin-dev wrote:
>> There is no reason to use a timestamp beyond 4 bytes.
>=20
> Actually, there is: lock times... my overflow solution doesn't have a =
solution=20
> to that. :x


You could steal a few bits form tx nVersion through a softfork=