From: Pieter Wuille <bitcoin-dev@wuille•net>
To: Mike Brooks <m@ib•tc>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Progress on Miner Withholding - FPNC
Date: Thu, 08 Oct 2020 00:12:47 +0000 [thread overview]
Message-ID: <rhkjkcbglvbiQpSVK8NA0jUpRqfLj4zNnGiV0AWxcALnyJF5vHqEtw1Jf-GAq9yfjrnPSXV_p9SPDZgjoEaVIj4w6tJMbhhrQ5Xoyp7Us_I=@wuille.net> (raw)
In-Reply-To: <CALFqKjTY6d2nQtUe-NyyKJEYcWKEj1mfdQfAzKkB-NRDwYD5JQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 914 bytes --]
On Wednesday, October 7, 2020 1:31 PM, Mike Brooks via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org> wrote:
> But first of all, I'd like to say that the idea for FPNC came out of a conversation with ZmnSCPxj's in regards to re-org stability. When I had proposed blockchain pointers with the PubRef opcode, he took the time to explain to me concerns around re-orgs and why it is a bigger problem than I initially had thought — and I greatly appreciate this detail. After touching base with ZmnSCPxj and Greg Maxwell there is an overwhelming view that the current problems that face the network outweigh any theoretical ones.
Greg Maxwell isn't on this list, but assuming this is about the conversion you've had on Bitcoin Core's security disclosure list, I believe this is a misrepresentation. The discussion has been mostly around a DoS attack report which turned out to be a mistake.
Cheers,
--
Pieter
[-- Attachment #2: Type: text/html, Size: 1264 bytes --]
next prev parent reply other threads:[~2020-10-08 0:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 4:04 Mike Brooks
2020-10-08 0:12 ` Pieter Wuille [this message]
2020-10-09 0:16 ` Mike Brooks
2020-10-08 1:39 ` ZmnSCPxj
2020-10-08 9:18 ` Önder Gürcan
2020-10-08 23:05 ` Mike Brooks
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='rhkjkcbglvbiQpSVK8NA0jUpRqfLj4zNnGiV0AWxcALnyJF5vHqEtw1Jf-GAq9yfjrnPSXV_p9SPDZgjoEaVIj4w6tJMbhhrQ5Xoyp7Us_I=@wuille.net' \
--to=bitcoin-dev@wuille$(echo .)net \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=m@ib$(echo .)tc \
/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