📅 Original date posted:2015-07-02
📝 Original message:I'm also a user who runs a full node, and I also like this idea. I think
Gavin has done some back-of-the-envelope calculations around this stuff,
but nothing so clearly defined as what you propose.
On 07/02/2015 08:33 AM, Mistr Bigs wrote:
> I'm an end user running a full node on an aging laptop.
> I think this is a great suggestion! I'd love to know what system
> requirements are needed for running Bitcoin Core.
>
> On Thu, Jul 2, 2015 at 6:04 AM, Jean-Paul Kogelman
> <jeanpaulkogelman at me.com <mailto:jeanpaulkogelman at me.com>> wrote:
>
> I’m a game developer. I write time critical code for a living and
> have to deal with memory, CPU, GPU and I/O budgets on a daily basis.
> These budgets are based on what we call a minimum specification (of
> hardware); min spec for short. In most cases the min spec is based
> on entry model machines that are available during launch, and will
> give the user an enjoyable experience when playing our games.
> Obviously, we can turn on a number of bells and whistles for people
> with faster machines, but that’s not the point of this mail.
>
> The point is, can we define a min spec for Bitcoin Core? The number
> one reason for this is: if you know how your changes affect your
> available budgets, then the risk of breaking something due to
> capacity problems is reduced to practically zero.
>
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
Owen Gunden [ARCHIVE] /
npub130…hyp4t
2023-06-07 15:41:29
in reply to nevent1q…rnpc
Author Public Key
npub130jddflllc905dlmj0pks9j6fdtld9eu0pql9gm86dxts7whrvxq5hyp4tPublished at
2023-06-07 15:41:29Event JSON
{
"id": "a2b5f6a13575b5fe7895c488d0f1ca18f7f3b95f0206bcafd581080122708178",
"pubkey": "8be4d6a7fffe0afa37fb93c368165a4b57f6973c7841f2a367d34cb879d71b0c",
"created_at": 1686152489,
"kind": 1,
"tags": [
[
"e",
"cbeb59b6768e318715a77120e4857024067bd925936ab9abad26dc3d4a343b49",
"",
"root"
],
[
"e",
"666687d030bf3a520732167eb3e08da528aa042185260f11a93746ffb397b082",
"",
"reply"
],
[
"p",
"3f309567f3bf9fe80a3f4757938eb8b06fece90dab3fb770f539c0399eabca4e"
]
],
"content": "📅 Original date posted:2015-07-02\n📝 Original message:I'm also a user who runs a full node, and I also like this idea. I think \nGavin has done some back-of-the-envelope calculations around this stuff, \nbut nothing so clearly defined as what you propose.\n\nOn 07/02/2015 08:33 AM, Mistr Bigs wrote:\n\u003e I'm an end user running a full node on an aging laptop.\n\u003e I think this is a great suggestion! I'd love to know what system\n\u003e requirements are needed for running Bitcoin Core.\n\u003e\n\u003e On Thu, Jul 2, 2015 at 6:04 AM, Jean-Paul Kogelman\n\u003e \u003cjeanpaulkogelman at me.com \u003cmailto:jeanpaulkogelman at me.com\u003e\u003e wrote:\n\u003e\n\u003e I’m a game developer. I write time critical code for a living and\n\u003e have to deal with memory, CPU, GPU and I/O budgets on a daily basis.\n\u003e These budgets are based on what we call a minimum specification (of\n\u003e hardware); min spec for short. In most cases the min spec is based\n\u003e on entry model machines that are available during launch, and will\n\u003e give the user an enjoyable experience when playing our games.\n\u003e Obviously, we can turn on a number of bells and whistles for people\n\u003e with faster machines, but that’s not the point of this mail.\n\u003e\n\u003e The point is, can we define a min spec for Bitcoin Core? The number\n\u003e one reason for this is: if you know how your changes affect your\n\u003e available budgets, then the risk of breaking something due to\n\u003e capacity problems is reduced to practically zero.\n\u003e\n\u003e\n\u003e\n\u003e _______________________________________________\n\u003e bitcoin-dev mailing list\n\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e",
"sig": "ce1b02d1bc5f6d8c2a194410448469e964331a803f7cc1c6a1650aa14a460df795b26c496499b3b4ad32ade09153d2c79569d3be6e0169ad3fcff1089e5cf178"
}