Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
	helo=mx.sourceforge.net)
	by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <jgarzik@exmulti.com>) id 1UaT0M-0001Uy-Ii
	for bitcoin-development@lists.sourceforge.net;
	Thu, 09 May 2013 15:43:38 +0000
X-ACL-Warn: 
Received: from mail-pa0-f51.google.com ([209.85.220.51])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1UaT0L-0001gr-GA
	for bitcoin-development@lists.sourceforge.net;
	Thu, 09 May 2013 15:43:38 +0000
Received: by mail-pa0-f51.google.com with SMTP id ld10so2199535pab.38
	for <bitcoin-development@lists.sourceforge.net>;
	Thu, 09 May 2013 08:43:31 -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=YqEXIDoTOMvCm9/Ng4jNyUqcUSUrHUph6Jqo250UfUY=;
	b=miBkl9qIJtEsKbzPyZXxqFO1aBCEzD5CLsU4GMUm4lfdVVPKPJB8NNOqqnDn6T7v9I
	xVyYPpr+u/sUluO7aZ5NOducqcHHg3Oo7m+q0pWFeTlJLrrxgb1FzgRNR4upw8hq+mdw
	EWN1kRMw3Nm8wOd1LHHW9AUzo9LrycY43ps2v7kOXvW+BkpQFqPEx0Uv0xir2eciHJzl
	JZbntpnrP3uDzrI2rHze00DbTb1VIiNzTlA9/08q8tJ4mD9sXmAs6L9Z5SM7ootqN/bv
	dHxAVP7ciGASjqZpwC0c+YnMQmSSJR4MHgxxlgMrUbJN3EFodFxVA2kZFBQjQbcVpsAU
	qPZw==
MIME-Version: 1.0
X-Received: by 10.68.99.163 with SMTP id er3mr13303412pbb.36.1368114211558;
	Thu, 09 May 2013 08:43:31 -0700 (PDT)
Received: by 10.68.240.106 with HTTP; Thu, 9 May 2013 08:43:31 -0700 (PDT)
X-Originating-IP: [99.43.178.25]
In-Reply-To: <CANEZrP3Ja7ZAh65yJvH+juPkOF2-qxSxHKz+Zp_5hH6Hw9yyZw@mail.gmail.com>
References: <CAA3bHnwWHAmvF3vWwakJXKBt9y6b1u0cc7j4AbQBCOy-h3a1XA@mail.gmail.com>
	<20130508234422.GA30870@savin>
	<CAPaL=UVNSM1W-vDt_kWUprMCt_LVTHfdiUkf0Aem1FAoD+4Qxw@mail.gmail.com>
	<CA+8xBpf-A7z8ffbLjoRRuK56KHJ4xHUyNSca5yOJHx6tQB=T7A@mail.gmail.com>
	<20130509011338.GA8708@vps7135.xlshosting.net>
	<CAPaL=UW_uvMpLx2sv4o3yONcAnY8xwLQWT2Act6por7CdHBJNw@mail.gmail.com>
	<20130509015731.GA26423@savin>
	<CAPaL=UWBrc8VfHvmmKHoDH_D9G5_nPir8sLdYYF4ybsz3STD0A@mail.gmail.com>
	<20130509024244.GA5474@savin>
	<20130509111247.GA18521@vps7135.xlshosting.net>
	<CANEZrP3Ja7ZAh65yJvH+juPkOF2-qxSxHKz+Zp_5hH6Hw9yyZw@mail.gmail.com>
Date: Thu, 9 May 2013 11:43:31 -0400
Message-ID: <CA+8xBpfQ9Tg2u2ZGUh239qfgWCo3LArZz==T=MrTF02G7G+pdA@mail.gmail.com>
From: Jeff Garzik <jgarzik@exmulti.com>
To: Mike Hearn <mike@plan99.net>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQm8/7yPCA/s5lEXMKg9X3KKs/dVEo/OzHI+Nv4f/DPxVfwKB6UL2bJEuwDtOGLIafajr3b9
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: 1UaT0L-0001gr-GA
Cc: Bitcoin Dev <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: Thu, 09 May 2013 15:43:38 -0000

On Thu, May 9, 2013 at 11:40 AM, Mike Hearn <mike@plan99.net> wrote:
> 2038 issues only apply to use of signed timestamps, I thought we treat
> this field as unsigned? Is it really a big deal?

Not a big deal at all, no.
-- 
Jeff Garzik
exMULTI, Inc.
jgarzik@exmulti.com