Pieter Wuille [ARCHIVE] on Nostr: 📅 Original date posted:2013-05-09 📝 Original message:On Wed, May 08, 2013 at ...
📅 Original date posted:2013-05-09
📝 Original message:On Wed, May 08, 2013 at 10:42:44PM -0400, Peter Todd wrote:
> 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...
No, though that's also a possibility, but a backward-incompatible one.
What I mean is have a well-defined 64-bit timestamp for each block, but
only put the lowest 32 bit in the header. Under the condition:
* There is never a gap of more than 136 years between two blocks.
The actual 64-bit timestamp can be deterministically derived from the
header, by prefixing it with the lowest 32-bit value that does not
cause the result to violate the
at-least-above-the-median-of-the-previous-11-blocks rule.
--
Pieter
Published at
2023-06-07 15:01:34Event JSON
{
"id": "8113cadec829874f0c73e0f5bdaffa61720d89e2625d6d30733b4f3d23f5287a",
"pubkey": "5cb21bf5d7f25a9d46879713cbd32433bbc10e40ef813a3c28fe7355f49854d6",
"created_at": 1686150094,
"kind": 1,
"tags": [
[
"e",
"94096a540659922fb308765fd366df049294303f58802ee2f87aef70df5f594b",
"",
"root"
],
[
"e",
"3f3f56059ae8f47c4656cfbaa27fc51da47e0a31f45fa6dee918e22b96ce0de3",
"",
"reply"
],
[
"p",
"daa2fc676a25e3b5b45644540bcbd1e1168b111427cd0e3cf19c56194fb231aa"
]
],
"content": "📅 Original date posted:2013-05-09\n📝 Original message:On Wed, May 08, 2013 at 10:42:44PM -0400, Peter Todd wrote:\n\u003e Ah, shoot, I just realized we both got missed Pieter's point entirely:\n\u003e he means to change the meaning of the header timestamp to be relative\n\u003e time passed since the last block...\n\nNo, though that's also a possibility, but a backward-incompatible one.\n\nWhat I mean is have a well-defined 64-bit timestamp for each block, but\nonly put the lowest 32 bit in the header. Under the condition:\n\n* There is never a gap of more than 136 years between two blocks.\n\nThe actual 64-bit timestamp can be deterministically derived from the\nheader, by prefixing it with the lowest 32-bit value that does not\ncause the result to violate the\nat-least-above-the-median-of-the-previous-11-blocks rule.\n\n-- \nPieter",
"sig": "5631eeb24b89c55560ec20613f18b9de1b5bd444e40e78eae1fe471da947092fb971972e0299f778c7067678436846d50a21498094d88b31c0622c878944466b"
}