public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Addy Yeow <ayeowch@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Subject: [Bitcoin-development] 32 vs 64-bit timestamp fields
Date: Thu, 9 May 2013 09:39:10 +1000	[thread overview]
Message-ID: <CAA3bHnwWHAmvF3vWwakJXKBt9y6b1u0cc7j4AbQBCOy-h3a1XA@mail.gmail.com> (raw)

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

Cheers,
Addy



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

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-08 23:39 Addy Yeow [this message]
2013-05-08 23:42 ` [Bitcoin-development] 32 vs 64-bit timestamp fields Jeff Garzik
2013-05-08 23:44 ` Peter Todd
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=CAA3bHnwWHAmvF3vWwakJXKBt9y6b1u0cc7j4AbQBCOy-h3a1XA@mail.gmail.com \
    --to=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