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
--
Learn Graph Databases - Download FREE
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, May 8, 2013 at 11:44 PM, Peter Todd p...@petertodd.org wrote:
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
On Wed, May 08, 2013 at 09:08:34PM -0400, Jeff Garzik wrote:
On Wed, May 8, 2013 at 9:00 PM, John Dillon
john.dillon...@googlemail.com wrote:
Perhaps Satoshi did this delibrately, knowing that at some point a hard-fork
would be a good idea, so that we all would have a good excuse to do one?
On Thu, May 09, 2013 at 01:27:33AM +, John Dillon wrote:
There's also no need: 32 bits is plenty of precision. Hell, even 16 bits
would
do (assuming there's never more than a 65535s (about 18 hours) gap between
two
blocks). Just assume the full 64-bit time is the smallest one that
On Thu, May 09, 2013 at 02:33:11AM +, John Dillon wrote:
On Thu, May 9, 2013 at 1:57 AM, Peter Todd p...@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.
I actually just meant how
6 matches
Mail list logo
