📅 Original date posted:2014-04-10
📝 Original message:On Thu, Apr 10, 2014 at 1:37 PM, Mike Hearn <mike at plan99.net> wrote:
> Chain pruning is probably a separate thread, changing subject.
>
>
>> Reason is that the actual blocks available are likely to change
>> frequently (if
>> you keep the last week of blocks
>
>
> I doubt anyone would specify blocks to keep in terms of time. More likely
> it'd be in terms of megabytes, as that's the actual resource constraint on
> nodes.
>
Well with bitcoin, (average) time, number of blocks and (maximum) size are
all related to each other so it doesn't matter how it is specified, it's
always possible to give estimates of all three.
As for implementation it indeed makes most sense to work with block ranges.
> Given a block size average it's easy to go from megabytes to num_blocks,
> so I had imagined it'd be a new addr field that specifies how many blocks
> from the chain head are stored. Then you'd connect to some nodes and if
> they indicate their chain head - num_blocks_stored is higher than your
> current chain height, you'd do a getaddr and go looking for nodes that are
> storing far enough back.
>
This assumes that nodes will always be storing the latest blocks. For
dynamic nodes that take part in the consensus this makes sense.
Just wondering: Would there be a use for a [static] node that, say, always
serves only the first 100000 blocks? Or, even, a static range like block
100000 - 200000?
Wladimir
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140410/d9a682b3/attachment.html>;
Wladimir [ARCHIVE] /
npub1xq…ymc2p
2023-06-07 15:18:28
in reply to nevent1q…ctrd
Author Public Key
npub1xqshkqv2g7uea4xzqwvmgjcz7u8vfavw6aazs999v0azsv3w7u3qpymc2pSeen on
wss://relay.noswhere.comPublished at
2023-06-07 15:18:28Event JSON
{
"id": "649c04559980f0ef3f196dc260685da956f48ce9e7a03a9919000fb49ed211d1",
"pubkey": "30217b018a47b99ed4c20399b44b02f70ec4f58ed77a2814a563fa28322ef722",
"created_at": 1686151108,
"kind": 1,
"tags": [
[
"e",
"aae8a2dedee78eef571f285fef23331d89c84b104c87b098618414541001d13e",
"",
"root"
],
[
"e",
"b1e4aa05c99755fba4c7519a74c8261e1841b2c5f66da0c8245c0a123b3803d4",
"",
"reply"
],
[
"p",
"f2c95df3766562e3b96b79a0254881c59e8639f23987846961cf55412a77f6f2"
]
],
"content": "📅 Original date posted:2014-04-10\n📝 Original message:On Thu, Apr 10, 2014 at 1:37 PM, Mike Hearn \u003cmike at plan99.net\u003e wrote:\n\n\u003e Chain pruning is probably a separate thread, changing subject.\n\u003e\n\u003e\n\u003e\u003e Reason is that the actual blocks available are likely to change\n\u003e\u003e frequently (if\n\u003e\u003e you keep the last week of blocks\n\u003e\n\u003e\n\u003e I doubt anyone would specify blocks to keep in terms of time. More likely\n\u003e it'd be in terms of megabytes, as that's the actual resource constraint on\n\u003e nodes.\n\u003e\n\nWell with bitcoin, (average) time, number of blocks and (maximum) size are\nall related to each other so it doesn't matter how it is specified, it's\nalways possible to give estimates of all three.\n\nAs for implementation it indeed makes most sense to work with block ranges.\n\n\n\u003e Given a block size average it's easy to go from megabytes to num_blocks,\n\u003e so I had imagined it'd be a new addr field that specifies how many blocks\n\u003e from the chain head are stored. Then you'd connect to some nodes and if\n\u003e they indicate their chain head - num_blocks_stored is higher than your\n\u003e current chain height, you'd do a getaddr and go looking for nodes that are\n\u003e storing far enough back.\n\u003e\n\nThis assumes that nodes will always be storing the latest blocks. For\ndynamic nodes that take part in the consensus this makes sense.\n\nJust wondering: Would there be a use for a [static] node that, say, always\nserves only the first 100000 blocks? Or, even, a static range like block\n100000 - 200000?\n\nWladimir\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140410/d9a682b3/attachment.html\u003e",
"sig": "891152c07152542f11d410778f2f864be3d0d41a0c5331fc53a209893beaefab92636cc865da0a87ac37e2497f62d3a1f50107d50826caa11a66e12b076b5ced"
}