📅 Original date posted:2015-05-29
📝 Original message:>
> If the plan is a fix once and for all, then that should be changed too.
> It could be set so that it is at least some multiple of the max block size
> allowed.
>
Well, but RAM is not infinite :-) Effectively what these caps are doing is
setting the minimum hardware requirements for running a Bitcoin node.
That's OK by me - I don't think we are actually going to exhaust the
hardware abilities of any reasonable computer any time soon, but still,
having the software recognise the finite nature of a computing machine
doesn't seem unwise.
> That system can send a block of any size. It would require a change to
> the processing of any merkleblocks received.
>
Not "any" size because, again, the remote node must buffer things up and
have the transaction data actually in memory in order to digest it. But a
much larger size, yes.
However, that's a bigger change.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150529/6aebe66a/attachment.html>;
Mike Hearn [ARCHIVE] /
npub17t…4qgyd
2023-06-07 15:34:06
in reply to nevent1q…d2u8
Author Public Key
npub17ty4mumkv43w8wtt0xsz2jypck0gvw0j8xrcg6tpea25z2nh7meqf4qgydPublished at
2023-06-07 15:34:06Event JSON
{
"id": "78e145a43abc8bb069d76fbb1a10b36fd1d649b2d60fab1c04237747890d4477",
"pubkey": "f2c95df3766562e3b96b79a0254881c59e8639f23987846961cf55412a77f6f2",
"created_at": 1686152046,
"kind": 1,
"tags": [
[
"e",
"aec396df7693e37c124fbd2891fe6c4a3b28f46e7fbc3f304a7b1d78d2f5ffbe",
"",
"root"
],
[
"e",
"c2351e4dd36239016ad820b35c86f4cb033fa474b263f95d2199d9f34cbdd133",
"",
"reply"
],
[
"p",
"46986f86b97cc97829a031b03209644d134b939d0163375467f0b1363e0d875e"
]
],
"content": "📅 Original date posted:2015-05-29\n📝 Original message:\u003e\n\u003e If the plan is a fix once and for all, then that should be changed too.\n\u003e It could be set so that it is at least some multiple of the max block size\n\u003e allowed.\n\u003e\n\nWell, but RAM is not infinite :-) Effectively what these caps are doing is\nsetting the minimum hardware requirements for running a Bitcoin node.\n\nThat's OK by me - I don't think we are actually going to exhaust the\nhardware abilities of any reasonable computer any time soon, but still,\nhaving the software recognise the finite nature of a computing machine\ndoesn't seem unwise.\n\n\n\u003e That system can send a block of any size. It would require a change to\n\u003e the processing of any merkleblocks received.\n\u003e\n\nNot \"any\" size because, again, the remote node must buffer things up and\nhave the transaction data actually in memory in order to digest it. But a\nmuch larger size, yes.\n\nHowever, that's a bigger change.\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150529/6aebe66a/attachment.html\u003e",
"sig": "30ef44ab1e3048ac2bde7814d4af99061bd2c84446a324669fa682c57b259b0d5efb43297aaa3424bb485d29cba88f5056039ceef192f2c98824c0a7636ea206"
}