📅 Original date posted:2015-07-03
📝 Original message:If the freedom to pick architecture exists, Moxie is a nice, compact, easy
to audit alternative:
http://moxielogic.org/blog/pages/architecture.html
https://github.com/jgarzik/moxiebox
Scaling can occur at the core level, rather than hyper-pipelining, keeping
the architecture itself nice and clean and simple.
On Thu, Jul 2, 2015 at 11:13 PM, Jeremy Rubin <
jeremy.l.rubin.travel at gmail.com> wrote:
> Might I suggest that the min-spec, if developed, target the RISC-V Rocket
> architecture (running on FPGA, I suppose) as a reference point for
> performance? This may be much lower performance than desirable, however, it
> means that we don't lock people into using large-vendor chipsets which have
> unknown, or known to be bad, security properties such as Intel AMT.
>
> In general, targeting open hardware seems to me to be more critical than
> performance metrics for the long term health of Bitcoin, however,
> performance is still important.
>
> Does anyone know how the RISC-V FPGA performance stacks up to, say, a
> Raspberry Pi?
>
> On Thu, Jul 2, 2015 at 10:52 PM, Owen Gunden <ogunden at phauna.org> wrote:
>
>> 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
>>>
>>> _______________________________________________
>> bitcoin-dev mailing list
>> bitcoin-dev at lists.linuxfoundation.org
>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>>
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150702/b79de4df/attachment.html>;
Jeff Garzik [ARCHIVE] /
npub1kf…f3f58
2023-06-07 17:41:29
in reply to nevent1q…pkme
Author Public Key
npub1kf0ppcjaguxekg24yx6smgxlu73qn0k8lm0t2wrqc0scpl7u3sgsmf3f58Published at
2023-06-07 17:41:29Event JSON
{
"id": "8a8b27b9d4ba755a20fc1b53c74cc26b6c28b19d3a7db18637c87c6b868d323e",
"pubkey": "b25e10e25d470d9b215521b50da0dfe7a209bec7fedeb53860c3e180ffdc8c11",
"created_at": 1686152489,
"kind": 1,
"tags": [
[
"e",
"cbeb59b6768e318715a77120e4857024067bd925936ab9abad26dc3d4a343b49",
"",
"root"
],
[
"e",
"20389513c29dc1440c4b2425575f44a29d494be0a86039f1aeb1a30944b447bc",
"",
"reply"
],
[
"p",
"372c316761360b4ea20f2d7e81a59363b7e45b8e945a5381c3122049c2c4b84a"
]
],
"content": "📅 Original date posted:2015-07-03\n📝 Original message:If the freedom to pick architecture exists, Moxie is a nice, compact, easy\nto audit alternative:\n http://moxielogic.org/blog/pages/architecture.html\n https://github.com/jgarzik/moxiebox\n\nScaling can occur at the core level, rather than hyper-pipelining, keeping\nthe architecture itself nice and clean and simple.\n\n\n\nOn Thu, Jul 2, 2015 at 11:13 PM, Jeremy Rubin \u003c\njeremy.l.rubin.travel at gmail.com\u003e wrote:\n\n\u003e Might I suggest that the min-spec, if developed, target the RISC-V Rocket\n\u003e architecture (running on FPGA, I suppose) as a reference point for\n\u003e performance? This may be much lower performance than desirable, however, it\n\u003e means that we don't lock people into using large-vendor chipsets which have\n\u003e unknown, or known to be bad, security properties such as Intel AMT.\n\u003e\n\u003e In general, targeting open hardware seems to me to be more critical than\n\u003e performance metrics for the long term health of Bitcoin, however,\n\u003e performance is still important.\n\u003e\n\u003e Does anyone know how the RISC-V FPGA performance stacks up to, say, a\n\u003e Raspberry Pi?\n\u003e\n\u003e On Thu, Jul 2, 2015 at 10:52 PM, Owen Gunden \u003cogunden at phauna.org\u003e wrote:\n\u003e\n\u003e\u003e I'm also a user who runs a full node, and I also like this idea. I think\n\u003e\u003e Gavin has done some back-of-the-envelope calculations around this stuff,\n\u003e\u003e but nothing so clearly defined as what you propose.\n\u003e\u003e\n\u003e\u003e On 07/02/2015 08:33 AM, Mistr Bigs wrote:\n\u003e\u003e\n\u003e\u003e\u003e I'm an end user running a full node on an aging laptop.\n\u003e\u003e\u003e I think this is a great suggestion! I'd love to know what system\n\u003e\u003e\u003e requirements are needed for running Bitcoin Core.\n\u003e\u003e\u003e\n\u003e\u003e\u003e On Thu, Jul 2, 2015 at 6:04 AM, Jean-Paul Kogelman\n\u003e\u003e\u003e \u003cjeanpaulkogelman at me.com \u003cmailto:jeanpaulkogelman at me.com\u003e\u003e wrote:\n\u003e\u003e\u003e\n\u003e\u003e\u003e I’m a game developer. I write time critical code for a living and\n\u003e\u003e\u003e have to deal with memory, CPU, GPU and I/O budgets on a daily basis.\n\u003e\u003e\u003e These budgets are based on what we call a minimum specification (of\n\u003e\u003e\u003e hardware); min spec for short. In most cases the min spec is based\n\u003e\u003e\u003e on entry model machines that are available during launch, and will\n\u003e\u003e\u003e give the user an enjoyable experience when playing our games.\n\u003e\u003e\u003e Obviously, we can turn on a number of bells and whistles for people\n\u003e\u003e\u003e with faster machines, but that’s not the point of this mail.\n\u003e\u003e\u003e\n\u003e\u003e\u003e The point is, can we define a min spec for Bitcoin Core? The number\n\u003e\u003e\u003e one reason for this is: if you know how your changes affect your\n\u003e\u003e\u003e available budgets, then the risk of breaking something due to\n\u003e\u003e\u003e capacity problems is reduced to practically zero.\n\u003e\u003e\u003e\n\u003e\u003e\u003e\n\u003e\u003e\u003e\n\u003e\u003e\u003e _______________________________________________\n\u003e\u003e\u003e bitcoin-dev mailing list\n\u003e\u003e\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e\u003e\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e\u003e\u003e\n\u003e\u003e\u003e _______________________________________________\n\u003e\u003e bitcoin-dev mailing list\n\u003e\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e\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\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150702/b79de4df/attachment.html\u003e",
"sig": "23ea38ad9b16298379329ffc93a9bf3795c6be23ea5bd985f4c3f83482adf9ca5c31036d9456b9840e123076e6d19f112748275cdb5ae7ff03c480c1a275e7c0"
}