summaryrefslogtreecommitdiff
path: root/94/e4973f6d47fc573e12a76d0adf75a3959533ab
blob: 2db851918ffa5e90d15af40018c009511c96b46d (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
129
130
131
132
Return-Path: <roconnor@blockstream.io>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 3CFB69DA
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sat,  9 Mar 2019 18:29:28 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-io1-f53.google.com (mail-io1-f53.google.com
	[209.85.166.53])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id BF9707FC
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sat,  9 Mar 2019 18:29:27 +0000 (UTC)
Received: by mail-io1-f53.google.com with SMTP id x9so612798iog.12
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sat, 09 Mar 2019 10:29:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=blockstream.io; s=google;
	h=mime-version:references:in-reply-to:from:date:message-id:subject:to
	:cc; bh=UFEhFNSwCTO/4NAIMNblr94xfDASb3mcCyGUrlUdQu0=;
	b=AxTVet9dELT0O78NpajSpQCOINYF0Tl3tsUPGyt4uMjnklXgBnl0e8MUPcFJ5i79nQ
	3kMgyzx6/4bpo3lKxSsnk7rHslW6LRuNTIz5QoIWUmDIvxsMXN+dPX3E3wYvS2MQG7r4
	TEbasf96FK8rWGjeUkfCwzng5Hbo4htLfb54c=
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:cc;
	bh=UFEhFNSwCTO/4NAIMNblr94xfDASb3mcCyGUrlUdQu0=;
	b=a/a91pJ2d3w2FOPk+5AqFo5II0V1xzEaE0XhPin2Qmv3skpgHQfbTlfYz1hnRM67z7
	hskPiHoA2sYS1iow7hpJ45WB5VpAz956bKKV7q33A5c8P6EpcIZZsvlKf/o1svHnRtQE
	8ywKWbX2n9G364OHs8bl/b/gYU4fKIldMAqUaO/6o19hWhkLL0Lo3MeAHQsVBnm3+p1K
	BcnWUcMqBuwL87Qmo4DybwV//4GZYBJJ9nksSywdV4XA5ReLN6JzU6+zVzTWb6JAKTeA
	r1LRP+GoI/GYEMDJ6VWM87qTijsXjIM6pSIGfFI2L6RedOWwFP5syNjG+10lMcruveQC
	0feg==
X-Gm-Message-State: APjAAAUtA7R42eHpco6WMdA35npOiG9x16eUDgWtrqSIFV5lyk20bY1v
	rxbv4vTPLqrTvJiFAsBI1ILA1KI+0vPVVGfqKYJlU3d/
X-Google-Smtp-Source: APXvYqxqLc9TD6Lii3PSFyNuNicAUDB7lJeWYCudK4vx7HYWiNzSV8QUGKpXAJXk2NdlXbcUJDEPf2upvOZqkqd+KUU=
X-Received: by 2002:a6b:7b08:: with SMTP id l8mr460170iop.33.1552156166434;
	Sat, 09 Mar 2019 10:29:26 -0800 (PST)
MIME-Version: 1.0
References: <bf96c2fb-2e2e-a47f-e59f-87e56d83eca3@mattcorallo.com>
	<CAMZUoK=1kgZLR1YZ+cJgzwmEOwrABYFs=2Ri=xGX=BCr+w=VQw@mail.gmail.com>
	<6bb308f5-f478-d5ec-064f-e4972709f29c@mattcorallo.com>
	<D2014BB7-1EFC-4604-ACF6-3C5AC74B6FC0@sprovoost.nl>
In-Reply-To: <D2014BB7-1EFC-4604-ACF6-3C5AC74B6FC0@sprovoost.nl>
From: "Russell O'Connor" <roconnor@blockstream.io>
Date: Sat, 9 Mar 2019 13:29:15 -0500
Message-ID: <CAMZUoKmKvQXLvmUuts4+XieSisL6bHQe0mg=65C7t+t3ApBRQA@mail.gmail.com>
To: Sjors Provoost <sjors@sprovoost.nl>
Content-Type: multipart/alternative; boundary="000000000000efd01c0583ad845f"
X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID, DKIM_VALID_AU, HTML_MESSAGE,
	RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.org
X-Mailman-Approved-At: Sat, 09 Mar 2019 22:19:20 +0000
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] OP_CODESEPARATOR Re: BIP Proposal: The Great
 Consensus Cleanup
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
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: Sat, 09 Mar 2019 18:29:28 -0000

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

Hi Sjors,

On Fri, Mar 8, 2019 at 2:12 PM Sjors Provoost <sjors@sprovoost.nl> wrote:

> Transaction weight currently doesn't consider OP codes, it only considers
> if bytes are part of the witness. Changing that to something more akin to
> Ethereums gas pricing sounds too complicated to even consider.
>

I did say per executed OP_CODESEPARATOR, but upon reflection, I agree that
we'd like to know the weight without execution.  I think counting the
number of occurrences of OP_CODESEPARATOR (perhaps at the same time we
count OP_CHECKSIG operations?) is a reasonable compromise, and increasing
the weight according to my proposed formula based on that count (ideally
we'd take OP_IF branches into account).


> I would also like to believe that whoever went through the trouble of
> using OP_CODESEPARATOR reads this list.
>

I wish this were the case too, but I don't think it is reasonable to assume
that (even maaku isn't subscribed
<https://github.com/bitcoin/bitcoin/pull/15482#issuecomment-469836918>),
and I don't even think it is fair to assume such a someone necessarily even
speaks English.

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

<div dir=3D"ltr"><div>Hi Sjors,<br></div><br><div class=3D"gmail_quote"><di=
v dir=3D"ltr" class=3D"gmail_attr">On Fri, Mar 8, 2019 at 2:12 PM Sjors Pro=
voost &lt;<a href=3D"mailto:sjors@sprovoost.nl" target=3D"_blank">sjors@spr=
ovoost.nl</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">
Transaction weight currently doesn&#39;t consider OP codes, it only conside=
rs if bytes are part of the witness. Changing that to something more akin t=
o Ethereums gas pricing sounds too complicated to even consider.<br></block=
quote><div><br></div><div>I did say per executed OP_CODESEPARATOR, but upon=
 reflection, I agree that we&#39;d like to know the weight without executio=
n.=C2=A0 I think counting the number of occurrences of OP_CODESEPARATOR (pe=
rhaps at the same time we count OP_CHECKSIG operations?) is a reasonable co=
mpromise, and increasing the weight according to my proposed formula based =
on that count (ideally we&#39;d take OP_IF branches into account).<br></div=
><div>=C2=A0<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">
I would also like to believe that whoever went through the trouble of using=
 OP_CODESEPARATOR reads this list.<br></blockquote><div><br></div><div>I wi=
sh this were the case too, but I don&#39;t think it is reasonable to assume=
 that (even <a href=3D"https://github.com/bitcoin/bitcoin/pull/15482#issuec=
omment-469836918" target=3D"_blank">maaku isn&#39;t subscribed</a>), and I =
don&#39;t even think it is fair to assume such a someone necessarily even s=
peaks English.<br></div></div></div>

--000000000000efd01c0583ad845f--