public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Sergio Demian Lerner <sergio.d.lerner@gmail•com>
To: Peter Todd <pete@petertodd•org>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] DPL is not only not enough, but brings unfounded confidence to Bitcoin users
Date: Fri, 14 Oct 2016 15:10:45 -0300	[thread overview]
Message-ID: <CAKzdR-pp0K-kqHWBP6A_+Ze0x3Ye5c94M+gz+Tue1Q-v4R5hog@mail.gmail.com> (raw)
In-Reply-To: <20161014105757.GA8049@fedora-21-dvm>

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

Oh God... here we go again..

>
> Again, lets remember that you personally proposed a BIP[1] that had the
> effect
> of aiding your ASICBOOST patent[2] without disclosing that fact in your
> BIP nor
> your pull-req[3].
>
> This is false. The first sentence of the BIP states: "There are incentives
for miners to find cheap, non-standard ways to generate new work which are
not in the best interest of the protocol".

The BIP actually PROTECTS the network from stealth Shared-Nonce mining and
the fact you rejected it made the Bitcoin network LESS secure because now
we just don't know at what extent it is in use.

Shared-nonce mining can be done with or without that BIP/pull-req.

We didn't disclose more in the BIP because it was not clear if shared-nonce
mining (the fact that Bitcoin had a design flaw) would have a negative
affect on Bitcoin price.

ASICBoost patent may be a patent that protects Bitcoiners from mining
centralization: ASICBoost is the only company that at this point showed
interest in licensing the technology. But I do not control ASICBoost nor
the patent so I cannot do anything about it.

I propose we as a community do a crowdfund to try to license it from that
company (or any other that wants to put theirs in the deal) and put all in
public domain.

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

  parent reply	other threads:[~2016-10-14 18:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-14 10:38 Sergio Demian Lerner
2016-10-14 10:57 ` Peter Todd
2016-10-14 11:51   ` Daniel Robinson
2016-10-14 12:31     ` Peter Todd
2016-10-15 10:01     ` Tom Zander
2016-10-14 18:10   ` Sergio Demian Lerner [this message]
2016-10-14 19:01   ` Nick ODell
2016-10-14 21:07     ` Daniel Robinson

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=CAKzdR-pp0K-kqHWBP6A_+Ze0x3Ye5c94M+gz+Tue1Q-v4R5hog@mail.gmail.com \
    --to=sergio.d.lerner@gmail$(echo .)com \
    --cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
    --cc=pete@petertodd$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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