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 <jgarzik@exmulti.com>) id 1UaE0k-0002Rc-Uc
	for bitcoin-development@lists.sourceforge.net;
	Wed, 08 May 2013 23:43:03 +0000
X-ACL-Warn: 
Received: from mail-pa0-f52.google.com ([209.85.220.52])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1UaE0j-0004BP-LM
	for bitcoin-development@lists.sourceforge.net;
	Wed, 08 May 2013 23:43:02 +0000
Received: by mail-pa0-f52.google.com with SMTP id bg2so1682706pad.25
	for <bitcoin-development@lists.sourceforge.net>;
	Wed, 08 May 2013 16:42:55 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=mime-version:x-received:x-originating-ip:in-reply-to:references
	:date:message-id:subject:from:to:cc:content-type:x-gm-message-state;
	bh=X322p14t8C7Ppp4LLCKQF11AcnGiF6oiLq4+ARQzmUA=;
	b=KejHvkP8WYMBV1C3NsnTYm2cm2prjY0CVxEu+1NDAYTx4UE4jFBy+x+pDHoeZE12oh
	sFXBgd70xHvFPK4ig04LCev/LX3A6sy8uOk7qfnJBbM9Ozu35qGiNridgcjBceabvnSf
	mv2mKTNrVthSBxaBERpjKTetOu2G4Jwk2kdikAELDslcx6FzHegivHMGmvq6qs1IcPtd
	V6XK+1CKVihIRVe785c9N10oLJOJdv66jUByh5p+m0bxw/s67ip5tri91wo2AzVucPIm
	HA+Soo7m9DKr4VNxq3xHKHg3pdq60necatisna68kkYdi9ATOlegDE5UQH9J9tHOM+Dq
	Ak1g==
MIME-Version: 1.0
X-Received: by 10.66.164.232 with SMTP id yt8mr10477821pab.21.1368056575762;
	Wed, 08 May 2013 16:42:55 -0700 (PDT)
Received: by 10.68.240.106 with HTTP; Wed, 8 May 2013 16:42:55 -0700 (PDT)
X-Originating-IP: [99.43.178.25]
In-Reply-To: <CAA3bHnwWHAmvF3vWwakJXKBt9y6b1u0cc7j4AbQBCOy-h3a1XA@mail.gmail.com>
References: <CAA3bHnwWHAmvF3vWwakJXKBt9y6b1u0cc7j4AbQBCOy-h3a1XA@mail.gmail.com>
Date: Wed, 8 May 2013 19:42:55 -0400
Message-ID: <CA+8xBpdC1t6G278Jt02jferoXen=7LKTRdVhdC4jPiOUdvMSnw@mail.gmail.com>
From: Jeff Garzik <jgarzik@exmulti.com>
To: Addy Yeow <ayeowch@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQk7ACqynd4N/IxcdukkvrpMblIuaui2VRktabK13PYhY9BffG2aTnfyeMfLWFMnekf0DN/4
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
X-Headers-End: 1UaE0j-0004BP-LM
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] 32 vs 64-bit timestamp fields
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, 08 May 2013 23:43:03 -0000

On Wed, May 8, 2013 at 7:39 PM, Addy Yeow <ayeowch@gmail.com> wrote:
> Hi list,
>
> Can someone explain why do we have 32-bit and 64-bit timestamp fields
> instead of all being 64-bit?
>
> https://en.bitcoin.it/wiki/Protocol_specification

Hysterical raisins.

-- 
Jeff Garzik
exMULTI, Inc.
jgarzik@exmulti.com