From: "Russell O'Connor" <roconnor@blockstream•io>
To: Luke Dashjr <luke@dashjr•org>
Cc: Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>,
Russell O'Connor <roconnor@blockstream•com>,
Kalle Alm <kalle.alm@gmail•com>
Subject: Re: [bitcoin-dev] BIP 117 Feedback
Date: Tue, 16 Jan 2018 03:39:28 -0500 [thread overview]
Message-ID: <CAMZUoKkb1zcw7N=_Gn3_0miuNVP_LKSYkbeA-U2Yt8+b2G+b7w@mail.gmail.com> (raw)
In-Reply-To: <201801160415.55197.luke@dashjr.org>
[-- Attachment #1: Type: text/plain, Size: 1363 bytes --]
On Mon, Jan 15, 2018 at 11:15 PM, Luke Dashjr <luke@dashjr•org> wrote:
> On Tuesday 16 January 2018 1:06:14 AM Rusty Russell via bitcoin-dev wrote:
> > The rule AFAICT is "standard transactions must still work". This was
> > violated with low-S, but the transformation was arguably trivial.
> >
> > OTOH, use of altstack is completely standard, though in practice it's
> > unused and so only a theoretical concern.
>
> I'm not aware of a single standard/BIP that uses the altstack at all.
>
By "standard transaction" here, Rusty means that (P2SH or Segwit) scripts
that use the alt-stack pass the standardness checks and will be relayed by
recent Bitcoin Core software.
----
Regarding lowS: I think the more severe standardness change was the added
requirement that (some of the) pubkeys in a multisig must be parsable. I
have talked with people who cannot retrieve their funds now, when before
they could. However, like lowS, this was only a change to the standardness
rules and not a consensus change, so these funds are not necessarily
permanently lost. They can be retrieved with miner help.
I don't see how BIP 117, which is a change in consensus rules that could
cause permanent loss of otherwise well-secured funds (in addition to the
other issues raised about BIP 117), is even comparable to the previous
changes in only the standardness rules.
[-- Attachment #2: Type: text/html, Size: 1874 bytes --]
next prev parent reply other threads:[~2018-01-16 8:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 11:22 Rusty Russell
2018-01-09 12:40 ` Mark Friedenbach
2018-01-09 14:21 ` Pieter Wuille
2018-01-09 22:57 ` Mark Friedenbach
2018-01-12 10:48 ` Russell O'Connor
2018-01-16 1:06 ` Rusty Russell
2018-01-16 3:27 ` Gregory Maxwell
2018-01-16 4:15 ` Luke Dashjr
2018-01-16 8:39 ` Russell O'Connor [this message]
2018-03-05 15:28 ` Johnson Lau
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='CAMZUoKkb1zcw7N=_Gn3_0miuNVP_LKSYkbeA-U2Yt8+b2G+b7w@mail.gmail.com' \
--to=roconnor@blockstream$(echo .)io \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=kalle.alm@gmail$(echo .)com \
--cc=luke@dashjr$(echo .)org \
--cc=roconnor@blockstream$(echo .)com \
/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