Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of petertodd.org
	designates 62.13.148.113 as permitted sender)
	client-ip=62.13.148.113; envelope-from=pete@petertodd.org;
	helo=outmail148113.authsmtp.com; 
Date: Wed, 8 May 2013 22:42:44 -0400
From: Peter Todd <pete@petertodd.org>
To: John Dillon <john.dillon892@googlemail.com>
Message-ID: <20130509024244.GA5474@savin>
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>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="IS0zKkzwUGydFO0o"
Content-Disposition: inline
In-Reply-To: <CAPaL=UWBrc8VfHvmmKHoDH_D9G5_nPir8sLdYYF4ybsz3STD0A@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] 32 vs 64-bit timestamp fields
Precedence: list


--IS0zKkzwUGydFO0o
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, May 09, 2013 at 02:33:11AM +0000, John Dillon wrote:
> On Thu, May 9, 2013 at 1:57 AM, Peter Todd <pete@petertodd.org> wrote:
> > Remember that interpreting the timestamp on a block for the purposes of
> > timestamping is a lot more subtle than it appears at first.
>=20
> I actually just meant how Pieter Wuille was talking about a blocktime acc=
urate
> to only within 18 hours. :) But it is a nice writeup!
>=20
> In any case, for many things simple relative ordering is enough rather th=
an
> absolute time.

Ah, shoot, I just realized we both got missed Pieter's point entirely:
he means to change the meaning of the header timestamp to be relative
time passed since the last block...

Well, it was a nice writeup! Thanks for the correction re:
probabalistic; you are absolutely correct.

--=20
'peter'[:-1]@petertodd.org
00000000000000fb6d0ed7479069edef10b8bc598783e9d94bdb5cf9ae6a5f1c

--IS0zKkzwUGydFO0o
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQEcBAEBCAAGBQJRiw0kAAoJECSBQD2l8JH7+4EIALrqS9ExkY9T6hZcLv53gJVZ
ObqXzcS1ynlw/2kBJZMWB6svbtb5pP/JMuWWT6ycAWdylyjOwylLrKqhoAdJ9I+/
d1yzUYWA2FU3qJfJYC2kimDn2yrTOWewH8wc7I+wnYKnojIXR3kkKnHruq6FiWSj
m+Pm4kPpQfgwD2UyNJ8jtbrFEAAFnpjq5aL+O8xsxUswVD2rBl70nYrrXTN21cnG
0yyusvyCtWjJGMjYDV3Iupd1hxuv6IW69cyAFJw62Qj8I3H4p1uotfK1BrRgcuEO
L+YGr2gPbeyMbaHPMjUiYTTkfDYub3wFTFQQjiPc8ec0WOql4CaRV3EKyT3BoFI=
=9pRx
-----END PGP SIGNATURE-----

--IS0zKkzwUGydFO0o--