summaryrefslogtreecommitdiff
path: root/18/7f5f92f97194922392a15c2bc5a178dac76346
blob: 7421b84aba2ad0949606a6a67f04aa372eb9ee66 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
Return-Path: <roconnor@blockstream.com>
Received: from fraxinus.osuosl.org (smtp4.osuosl.org [140.211.166.137])
 by lists.linuxfoundation.org (Postfix) with ESMTP id 8C981C0051
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Thu,  8 Oct 2020 15:47:59 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by fraxinus.osuosl.org (Postfix) with ESMTP id 7C27A86D03
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Thu,  8 Oct 2020 15:47:59 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
Received: from fraxinus.osuosl.org ([127.0.0.1])
 by localhost (.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id VkrVAUGZP5gM
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Thu,  8 Oct 2020 15:47:54 +0000 (UTC)
X-Greylist: delayed 00:18:40 by SQLgrey-1.7.6
Received: from mail-qt1-f181.google.com (mail-qt1-f181.google.com
 [209.85.160.181])
 by fraxinus.osuosl.org (Postfix) with ESMTPS id 3243586CFC
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Thu,  8 Oct 2020 15:47:54 +0000 (UTC)
Received: by mail-qt1-f181.google.com with SMTP id c5so5475362qtw.3
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Thu, 08 Oct 2020 08:47:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=blockstream-com.20150623.gappssmtp.com; s=20150623;
 h=mime-version:references:in-reply-to:from:date:message-id:subject:to;
 bh=Ui4ziDc0Zh///O95CYOepES/ksfo7wqJddAJENhEIWI=;
 b=L6iPjfxjdWVrtQUQAo0hRBBSFV14ELqH459GBqTpDOJZ76Ysj5XMsELh4WKFOrRU6A
 MeN/xctC8tEpiuwps9+q0Hlt7XPMouRcNd+2l626qgJQb5UWF9udu+NykHRz6rbbdHCk
 9OEV/j5niokkR8I/OF4lwpMiwdlTvfg+wLY65g9T3Bbl4cjYVYRVxYI06MXsVxPerH6C
 8uSWsTOojjcc4vI8LWPoWoMMj6/w3vAPJXUgOW2yjOT2NFkvVvgEGLWqBXOdDcIxf2G8
 KMoY0EaSUxrCh/5hrHQQnGwgXa0061Z2kQii8UosonkMgq/btsvmTcAjGZd72icUeAFd
 JjgA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:mime-version:references:in-reply-to:from:date
 :message-id:subject:to;
 bh=Ui4ziDc0Zh///O95CYOepES/ksfo7wqJddAJENhEIWI=;
 b=QtUOnyl+7Cm5PUI07zF+mer4s5y5+IR2vZPHvfpBWhNOPOiPFkZH0AKhn8hJDCM7ds
 AyJrolOLLCNinMCpYcm/z2Ni/Y7Rs/BGGBPL73EVF05ykiSHBTUYyN04yL32U2F7RoKS
 HuMIbQ7B0zybllGNTS6gir1rWnFO9vxnKHcjTsQyAomrHsUPrUjI3LWmBPmvNC9olV67
 Mz3znkfN1YChackCDqNYB2elNGeFwL/CzXv85FP8eH4hh+Z+wG9VSjTDYua4208Zrkm7
 kTRLncHBeTYFY0UGoI2h65W7gVFZOwgBzDoFv0LxzQy2UGQRW+7tLuJYx58hAJh2lGgE
 RwHA==
X-Gm-Message-State: AOAM531MW9ZELnhQ1O0sPs/hFtVIwmcKm8dhoof8F72pzqkPzGv6Eah1
 ouzMarTdULagRtjphn9K3QfnxWx/GZn/T1pGkb8DZ9rb9PA=
X-Google-Smtp-Source: ABdhPJwffUJFDAggul574+DHAk6AmqCT0U3bwyhHqGxnb+rXjqk6is9XLDovo9by1oLimEC/bnyvou3PX/9l5A4PiqE=
X-Received: by 2002:a37:495:: with SMTP id 143mr8622825qke.384.1602170518556; 
 Thu, 08 Oct 2020 08:21:58 -0700 (PDT)
MIME-Version: 1.0
References: <87imblmutl.fsf@rustcorp.com.au>
 <20201008145938.vrmm33f6sugdc7qm@ganymede>
In-Reply-To: <20201008145938.vrmm33f6sugdc7qm@ganymede>
From: "Russell O'Connor" <roconnor@blockstream.com>
Date: Thu, 8 Oct 2020 11:21:47 -0400
Message-ID: <CAMZUoKk1FA_imTcf+Y8WiW9CbNPvMKyfW6B3-qxXGBCvAX0i9A@mail.gmail.com>
To: "David A. Harding" <dave@dtrt.org>, 
 Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="000000000000a0e7fd05b12a6427"
Subject: Re: [bitcoin-dev] Progress on bech32 for future Segwit Versions
	(BIP-173)
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>, 
 <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>, 
 <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Oct 2020 15:47:59 -0000

--000000000000a0e7fd05b12a6427
Content-Type: text/plain; charset="UTF-8"

On Thu, Oct 8, 2020 at 11:00 AM David A. Harding via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> Rather than go through that again, I'd prefer we use the
> backwards compatible proposal from BIPs PR#945 and, if we want to
> maximize safety, consensus restrict v1 witness program size, e.g. reject
> transactions with scriptPubKeys paying v1 witness programs that aren't
> exactly 32 bytes.
>

Adding some kind of relay policy rule would be easier than a consensus
rule, and maybe effective enough.  (This comment is not intended to endorse
any one proposal over another.)


> Hopefully by the time we want to use segwit v2, most software will have
> implemented length limits and so we won't need any additional consensus
> restrictions from then on forward.
>

--000000000000a0e7fd05b12a6427
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"g=
mail_attr">On Thu, Oct 8, 2020 at 11:00 AM David A. Harding via bitcoin-dev=
 &lt;<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@l=
ists.linuxfoundation.org</a>&gt; wrote:<br></div><blockquote class=3D"gmail=
_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204=
,204);padding-left:1ex">Rather than go through that again, I&#39;d prefer w=
e use the<br>
backwards compatible proposal from BIPs PR#945 and, if we want to<br>
maximize safety, consensus restrict v1 witness program size, e.g. reject<br=
>
transactions with scriptPubKeys paying v1 witness programs that aren&#39;t<=
br>
exactly 32 bytes.<br></blockquote><div><br></div><div>Adding some kind of r=
elay policy rule would be easier than a consensus rule, and maybe effective=
 enough.=C2=A0 (This comment is not intended to endorse any one proposal ov=
er another.)<br></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padd=
ing-left:1ex">
Hopefully by the time we want to use segwit v2, most software will have<br>
implemented length limits and so we won&#39;t need any additional consensus=
<br>
restrictions from then on forward.<br>
</blockquote></div></div>

--000000000000a0e7fd05b12a6427--