📅 Original date posted:2015-06-22
📝 Original message:On Jun 22, 2015, at 11:18 AM, Gavin Andresen <gavinandresen at gmail.com> wrote:
The maximum size shall be 8,000,000 bytes at a timestamp of 2016-01-11 00:00:00 UTC (timestamp 1452470400), and shall double every 63,072,000 seconds (two years, ignoring leap years), until 2036-01-06 00:00:00 UTC (timestamp 2083190400). The maximum size of blocks in between doublings will increase linearly based on the block's timestamp. The maximum size of blocks after 2036-01-06 00:00:00 UTC shall be 8,192,000,000 bytes.
Since it's possible that block timestamps aren't chronological in order, what would happen if a block following a size increase trigger is back in the past before the size increase? Would that block have a lower size restriction again? Would using block height not be a more stable number to work with?
jp
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150622/2b279abf/attachment.html>;
Jean-Paul Kogelman [ARCHIVE] /
npub1sa…8y304
2023-06-07 15:39:53
in reply to nevent1q…yf5k
Author Public Key
npub1sa86gng3pvs3jgyt5majwcrhn8ck5qxgy9pjqxkh79u638cd7dys28y304Published at
2023-06-07 15:39:53Event JSON
{
"id": "e2a9112c428b44afc8ec4a54c3f17038339a78bc3f237108caee27b38fbb30ed",
"pubkey": "874fa44d110b2119208ba6fb27607799f16a00c82143201ad7f179a89f0df349",
"created_at": 1686152393,
"kind": 1,
"tags": [
[
"e",
"1936c15d372dc9e8a0eaf645dcff207375e90675dbebfadcf82370abc654737d",
"",
"root"
],
[
"e",
"d34a8c3252854ba66d37af3f9cb3c6b3d3c39c653f92e29e04a884841c71dbe3",
"",
"reply"
],
[
"p",
"8a718cc163bd0c956b748cfd134e84f90a27d5fdaccac045fbc8e7693f0080b8"
]
],
"content": "📅 Original date posted:2015-06-22\n📝 Original message:On Jun 22, 2015, at 11:18 AM, Gavin Andresen \u003cgavinandresen at gmail.com\u003e wrote:\n\nThe maximum size shall be 8,000,000 bytes at a timestamp of 2016-01-11 00:00:00 UTC (timestamp 1452470400), and shall double every 63,072,000 seconds (two years, ignoring leap years), until 2036-01-06 00:00:00 UTC (timestamp 2083190400). The maximum size of blocks in between doublings will increase linearly based on the block's timestamp. The maximum size of blocks after 2036-01-06 00:00:00 UTC shall be 8,192,000,000 bytes.\n \nSince it's possible that block timestamps aren't chronological in order, what would happen if a block following a size increase trigger is back in the past before the size increase? Would that block have a lower size restriction again? Would using block height not be a more stable number to work with?\n\njp\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150622/2b279abf/attachment.html\u003e",
"sig": "dd17a96eea0b2b1e28e4f12682eaf30da6de05392fcafb1e707608727dce668c7519aa460487662c81b5a9f315d53b518bb6619cae8f8704a1a15d2b06bf5e1b"
}