public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Peter Todd <pete@petertodd.org>
To: Addy Yeow <ayeowch@gmail.com>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] 32 vs 64-bit timestamp fields
Date: Wed, 8 May 2013 19:44:22 -0400	[thread overview]
Message-ID: <20130508234422.GA30870@savin> (raw)
In-Reply-To: <CAA3bHnwWHAmvF3vWwakJXKBt9y6b1u0cc7j4AbQBCOy-h3a1XA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 628 bytes --]

On Thu, May 09, 2013 at 09:39:10AM +1000, Addy Yeow 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

Who knows?

Satoshi used 32-bits and those fields can't be changed now without every
single Bitcoin user changing all at once. (a "hard-fork" change)

We'll probably need to do one of those eventually for other reasons, so
we might as well leave fixing the timestamps until then.

-- 
'peter'[:-1]@petertodd.org
000000000000002a9a85a940c4da2951c3e91a043a44805fa286b336364d9daa

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

  parent reply	other threads:[~2013-05-08 23:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-08 23:39 [Bitcoin-development] 32 vs 64-bit timestamp fields Addy Yeow
2013-05-08 23:42 ` Jeff Garzik
2013-05-08 23:44 ` Peter Todd [this message]
2013-05-09  1:00   ` John Dillon
2013-05-09  1:08     ` Jeff Garzik
2013-05-09  1:13       ` Pieter Wuille
2013-05-09  1:27         ` John Dillon
2013-05-09  1:57           ` Peter Todd
2013-05-09  2:33             ` John Dillon
2013-05-09  2:42               ` Peter Todd
2013-05-09 11:12                 ` Pieter Wuille
2013-05-09 15:40                   ` Mike Hearn
2013-05-09 15:43                     ` Jeff Garzik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130508234422.GA30870@savin \
    --to=pete@petertodd.org \
    --cc=ayeowch@gmail.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox