From: ZmnSCPxj <ZmnSCPxj@protonmail.com>
To: Lonero Foundation <loneroassociation@gmail.com>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP Proposal: Consensus (hard fork) PoST Datastore for Energy Efficient Mining
Date: Wed, 17 Mar 2021 06:56:27 +0000 [thread overview]
Message-ID: <3eY-dfJ9c5qbmAL2gnRAkTFw_HYki0sNAwTtGptRleabpGhy7r5BApXD7qQs8OA63zAGrLha2ZIfGCbqyn1zHIbCaUgZv6Qmoqkz7M6mKV4=@protonmail.com> (raw)
In-Reply-To: <CA+YkXXzv2Q02uwAvdwOPjk=Lkj5jyYb6AtC5B25oGfVej0y6TA@mail.gmail.com>
Good morning Andrew,
> I wouldn't fully discount general purpose hardware or hardware outside of the realm of ASICS. BOINC (https://cds.cern.ch/record/800111/files/p1099.pdf) implements a decent distributed computing protocol (granted it isn't a cryptocurrency), but it far computes data at a much cheaper cost compared to the competition w/ decent levels of fault tolerance. I myself am running an extremely large scale open distributed computing pipeline, and can tell you for certain that what is out there is insane. In regards to the argument of generic HDDs and CPUs, the algorithmic implementation I am providing would likely make them more adaptable. More than likely, evidently there would be specialized HDDs similar to BurstCoin Miners, and 128-core CPUs, and all that. This could be inevitable, but the main point is providing access to other forms of computation along w/ ASICs. At the very least, the generic guys can experience it, and other infrastructures can have some form of compatibility.
What would the advantage of this be?
As I see it, changing the underlying algorithm is simply an attempt to reverse history, by requiring a new strain of specialization to be started instead of continuing the trend of optimizing SHA256d very very well.
I think it may be better to push *through* rather than *back*, and instead spread the optimization of SHA256d-specific hardware so widely that anyone with 2 BTC liquidity in one location has no particular advantage over anyone with 2 BTC liquidity in another location.
For one, I expect that there will be fewer patentable surprises remaining with SHA256d than any newer, much more complicated construction.
Regards,
ZmnSCPxj
next prev parent reply other threads:[~2021-03-17 6:56 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-04 23:42 [bitcoin-dev] BIP Proposal: Consensus (hard fork) PoST Datastore for Energy Efficient Mining Lonero Foundation
2021-03-05 13:42 ` Ryan Grant
[not found] ` <CAB0O3SVNyr_t23Y0LyT0mSaf6LONFRLYJ8qzO7rcdJFnrGccFw@mail.gmail.com>
2021-03-05 15:12 ` Lonero Foundation
2021-03-05 16:16 ` Lonero Foundation
2021-03-05 21:11 ` Keagan McClelland
2021-03-05 21:21 ` Lonero Foundation
2021-03-06 0:41 ` Keagan McClelland
2021-03-06 0:57 ` Lonero Foundation
2021-03-06 15:21 ` Ricardo Filipe
[not found] ` <CA+YkXXyP=BQ_a42J=RE7HJFcJ73atyrt4KWKUG8LbsbW=u4b5w@mail.gmail.com>
2021-03-08 23:40 ` Lonero Foundation
2021-03-11 15:29 ` Lonero Foundation
2021-03-12 15:02 ` Erik Aronesty
2021-03-12 16:54 ` Lonero Foundation
2021-03-12 22:37 ` email
2021-03-12 23:21 ` Lonero Foundation
2021-03-12 23:31 ` Lonero Foundation
2021-03-13 8:13 ` email
2021-03-13 15:02 ` Lonero Foundation
2021-03-13 15:45 ` yancy
2021-03-13 17:11 ` Lonero Foundation
2021-03-13 19:44 ` email
2021-03-14 5:45 ` Lonero Foundation
2021-03-17 0:24 ` Erik Aronesty
2021-03-17 5:05 ` ZmnSCPxj
2021-03-17 5:59 ` Lonero Foundation
2021-03-17 6:56 ` ZmnSCPxj [this message]
2021-03-17 7:06 ` Lonero Foundation
2021-03-14 12:36 ` LORD HIS EXCELLENCY JAMES HRMH
2021-03-14 14:32 ` Thomas Hartman
2021-03-16 18:22 ` Lonero Foundation
2021-03-15 2:02 ` Eric Martindale
2021-03-15 2:32 ` Lonero Foundation
[not found] ` <CA+YkXXyMUQtdSvjuMPQO71LpPb8qFdy-LTSrA8FEbeWMbPWa4w@mail.gmail.com>
2021-03-15 2:58 ` Lonero Foundation
2021-03-05 20:53 Eric Voskuil
[not found] <CA+YkXXzfEyeXYMyPKL20S+2VVRZVuHRT6eRgX56FBgG_A+uVSw@mail.gmail.com>
[not found] ` <12480994-451A-4256-8EFA-4741B3EC2006@voskuil.org>
2021-03-05 22:03 ` Lonero Foundation
2021-03-05 22:49 ` Eric Voskuil
2021-03-05 23:10 ` Lonero Foundation
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='3eY-dfJ9c5qbmAL2gnRAkTFw_HYki0sNAwTtGptRleabpGhy7r5BApXD7qQs8OA63zAGrLha2ZIfGCbqyn1zHIbCaUgZv6Qmoqkz7M6mKV4=@protonmail.com' \
--to=zmnscpxj@protonmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=loneroassociation@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox