public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Keagan McClelland <keagan.mcclelland@gmail.com>
To: Lonero Foundation <loneroassociation@gmail.com>,
	 Bitcoin Protocol Discussion
	<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP Proposal: Consensus (hard fork) PoST Datastore for Energy Efficient Mining
Date: Fri, 5 Mar 2021 14:11:02 -0700	[thread overview]
Message-ID: <CALeFGL31M5DAULLRtCwjPYHaPVqsVqREUg6WQ2-cuj23SNk=BA@mail.gmail.com> (raw)
In-Reply-To: <CA+YkXXwfS7eer5Za_ed9tCNdfOp4c3nV_X=mfXzoDxMm6BrizQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3595 bytes --]

It is important to understand that it is critical for the work to be
"useless" in order for the security model to be the same. If the work was
useful it provides an avenue for actors to have nothing at stake when
submitting a proof of work, since the marginal cost of block construction
will be lessened by the fact that the work was useful in a different
context and therefore would have been done anyway. This actually degrades
the security of the network in the process.

As a separate issue, proposing a hard fork in the hashing algorithm will
invalidate the enormous amount of capital expenditure by mining entities
and disincentivize future capital expenditure into mining hardware that may
compute these more "useful" proofs of work. This is because any change in
the POW algorithm will be considered unstable and subject to change in the
future. This puts the entire network at even more risk meaning that no
entity is tying their own interests to that of the bitcoin network at
large. It also puts the developers in a position where they can be bribed
by entities with a vested interest in deciding what the new "useful" proof
of work should be.

All of these things make the Bitcoin network worse off.

Keagan

On Fri, Mar 5, 2021 at 1:48 PM Lonero Foundation via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> Also in regards to my other email, I forgot to iterate that my
> cryptography proposal helps behind the efficiency category but also tackles
> problems such as NP-Completeness or Halting which is something the BTC
> network could be vulnerable to in the future. For sake of simplicity, I do
> want to do this BIP because it tackles lots of the issues in regards to
> this manner and can provide useful insight to the community. If things such
> as bigger block height have been proposed as hard forks, I feel at the very
> least an upgrade regarding the hashing algorithm and cryptography does at
> least warrant some discussion. Anyways I hope I can send you my BIP, just
> let me know on the preferred format?
>
> Best regards, Andrew
>
> On Fri, Mar 5, 2021, 10:12 AM Lonero Foundation <
> loneroassociation@gmail.com> wrote:
>
>> Hi, this isn't about the energy efficient argument in regards to
>> renewables or mining devices but a better cryptography layer to get the
>> most out of your hashing for validation. I do understand the arbitrariness
>> of it, but do want to still propose a document. Do I use the Media Wiki
>> format on GitHub and just attach it as my proposal?
>>
>> Best regards, Andrew
>>
>> On Fri, Mar 5, 2021, 10:07 AM Devrandom <c1.devrandom@niftybox.net>
>> wrote:
>>
>>> Hi Ryan and Andrew,
>>>
>>> On Fri, Mar 5, 2021 at 5:42 AM Ryan Grant via bitcoin-dev <
>>> bitcoin-dev@lists.linuxfoundation.org> wrote:
>>>
>>>>
>>>>   https://www.truthcoin.info/blog/pow-cheapest/
>>>>     "Nothing is Cheaper than Proof of Work"
>>>>     on | 04 Aug 2015
>>>>
>>>>
>>> Just to belabor this a bit, the paper demonstrates that the mining
>>> market will tend to expend resources equivalent to miner reward.  It does
>>> not prove that mining work has to expend *energy* as a primary cost.
>>>
>>> Some might argue that energy expenditure has negative externalities and
>>> that we should move to other resources.  I would argue that the negative
>>> externalities will go away soon because of the move to renewables, so the
>>> point is likely moot.
>>>
>>> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>

[-- Attachment #2: Type: text/html, Size: 5390 bytes --]

  reply	other threads:[~2021-03-05 21:11 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 [this message]
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
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='CALeFGL31M5DAULLRtCwjPYHaPVqsVqREUg6WQ2-cuj23SNk=BA@mail.gmail.com' \
    --to=keagan.mcclelland@gmail.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