From: Pieter Wuille <bitcoin-dev@wuille•net>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Revisiting squaredness tiebreaker for R point in BIP340
Date: Thu, 27 Aug 2020 01:10:21 +0000 [thread overview]
Message-ID: <DwS85N0KtcuFE7n5tHOg9C_nq1JSMg9qqpuhQn3mJhhTnLbvh6yHHxj8aqDzwHFNO9LnbHIQ-NsVevhxqUlHP1gL5iB-NpSdaLwt_s6ymGc=@wuille.net> (raw)
In-Reply-To: <CAFmfg2uL-gCV+1e1rf8+ywSUcEGTA01PP4jm+8kYub7R9E9hNw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1072 bytes --]
On Friday, August 21, 2020 1:50 AM, John Newbery via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org> wrote:
> Summary: We should change the proposal and implementation to use even tie-breakers everywhere.
>
> John #notoquadraticresiduetiebreakers Newbery
Thanks Nadav, Lloyd, John, and those who commented privately,
As the comments we've received have been unanimously in favor of changing, here is the PR for doing so: https://github.com/bitcoin/bips/pull/982
I'm very happy with this outcome, as it's indeed a significant reduction in the mental overhead needed for explaining the design decisions (the entire optimization section from the BIP can be removed, as those are no longer relevant to inform the decisions).
There is still some ongoing discussion about another change, namely permitting the use of messages that aren't exactly 32 bytes in length: https://github.com/sipa/bips/issues/207, but that would be a strict superset of what is permitted now, and have no impact on its use in BIP341/BIP342.
Cheers,
--
Pieter #thefinalfinalfinalbip340 Wuille
[-- Attachment #2: Type: text/html, Size: 1535 bytes --]
prev parent reply other threads:[~2020-08-27 1:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-12 18:49 Pieter Wuille
2020-08-12 20:19 ` Nadav Kohen
2020-08-13 5:31 ` Lloyd Fournier
2020-08-19 23:16 ` Pieter Wuille
2020-08-21 8:50 ` John Newbery
2020-08-27 1:10 ` Pieter Wuille [this message]
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='DwS85N0KtcuFE7n5tHOg9C_nq1JSMg9qqpuhQn3mJhhTnLbvh6yHHxj8aqDzwHFNO9LnbHIQ-NsVevhxqUlHP1gL5iB-NpSdaLwt_s6ymGc=@wuille.net' \
--to=bitcoin-dev@wuille$(echo .)net \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.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