📅 Original date posted:2015-10-02
📝 Original message:> On Oct 2, 2015, at 1:20 AM, Jorge Timón via bitcoin-dev <bitcoin-dev at lists.linuxfoundation.org> wrote:
> On Oct 2, 2015 10:03 AM, "Daniele Pinna via bitcoin-dev" <bitcoin-dev at lists.linuxfoundation.org <mailto:bitcoin-dev at lists.linuxfoundation.org>> wrote:
> > should an algorithm that guarantees protection from ASIC/FPGA optimization be found.
> This is demonstrably impossible: anything that can be done with software can be done with hardware. This is computer science 101. And specialized hardware can always be more efficient, at least energy-wise.
>
I encourage Alex and Dmitry to consider submitting their paper to Ledger, where it will be reviewed objectively and with an open mind. The authors have motivated their work, framed it in its scholarly context, and made explicit the contributions their paper makes. Their manuscript, "Asymmetric proof-of-work based on the Generalized Birthday problem," clearly represents a great deal of work by the authors and I commend them for their efforts.
In the link Adam Back provided, Greg Maxwell mentioned that “it is far from clear that 'memory hardness' is actually a useful goal.” I agree with this statement; however, regardless of whether memory hardness turns out to be a useful goal in regards to cryptocurrency or not, a paper analyzing memory-hard proof-of-work schemes is certainly useful in helping us to figure that out.
Best regards,
Peter
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20151002/7b817d44/attachment.html>;
Peter R [ARCHIVE] /
npub1vx…lz2gn
2023-06-07 17:42:17
in reply to nevent1q…vwp2
Author Public Key
npub1vxzlqg5f7ykqr3hheqxdcqe35q02a8rr2mez30sjaldhlvu4hsvsqlz2gnPublished at
2023-06-07 17:42:17Event JSON
{
"id": "17edcbe9b0f1630c6e5152de0134bc2f8cccc334233abbb051c71f35f6f041ce",
"pubkey": "6185f02289f12c01c6f7c80cdc0331a01eae9c6356f228be12efdb7fb395bc19",
"created_at": 1686159737,
"kind": 1,
"tags": [
[
"e",
"2b79b58114f32b2079d86393874136c9ba3a04ef542325625ff3b84f1b55c376",
"",
"root"
],
[
"e",
"b58a0df9a50995b9aa82e878825ff585647afc5e7e63b0f07708b7aa812de155",
"",
"reply"
],
[
"p",
"498a711971f8a0194289aee037a4c481a99e731b5151724064973cc0e0b27c84"
]
],
"content": "📅 Original date posted:2015-10-02\n📝 Original message:\u003e On Oct 2, 2015, at 1:20 AM, Jorge Timón via bitcoin-dev \u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e On Oct 2, 2015 10:03 AM, \"Daniele Pinna via bitcoin-dev\" \u003cbitcoin-dev at lists.linuxfoundation.org \u003cmailto:bitcoin-dev at lists.linuxfoundation.org\u003e\u003e wrote:\n\u003e \u003e should an algorithm that guarantees protection from ASIC/FPGA optimization be found.\n\u003e This is demonstrably impossible: anything that can be done with software can be done with hardware. This is computer science 101. And specialized hardware can always be more efficient, at least energy-wise.\n\u003e \nI encourage Alex and Dmitry to consider submitting their paper to Ledger, where it will be reviewed objectively and with an open mind. The authors have motivated their work, framed it in its scholarly context, and made explicit the contributions their paper makes. Their manuscript, \"Asymmetric proof-of-work based on the Generalized Birthday problem,\" clearly represents a great deal of work by the authors and I commend them for their efforts. \n\nIn the link Adam Back provided, Greg Maxwell mentioned that “it is far from clear that 'memory hardness' is actually a useful goal.” I agree with this statement; however, regardless of whether memory hardness turns out to be a useful goal in regards to cryptocurrency or not, a paper analyzing memory-hard proof-of-work schemes is certainly useful in helping us to figure that out. \n\nBest regards,\nPeter\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20151002/7b817d44/attachment.html\u003e",
"sig": "a8cdba878199ef7eb67ca3e1ba9525b35e0a90d095acfe6e3f118dbe733972df357d071d7c8cbd08c0fc1e3851af9bd193f9a88440cb454ceb2f58c86a49764b"
}