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
|
Return-Path: <jlrubin@mit.edu>
Received: from smtp4.osuosl.org (smtp4.osuosl.org [140.211.166.137])
by lists.linuxfoundation.org (Postfix) with ESMTP id 8BAB6C000A
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 16 Apr 2021 18:00:47 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp4.osuosl.org (Postfix) with ESMTP id 64DC541907
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 16 Apr 2021 18:00:47 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3,
SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from smtp4.osuosl.org ([127.0.0.1])
by localhost (smtp4.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id jLE9Kvvf14SF
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 16 Apr 2021 18:00:43 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11])
by smtp4.osuosl.org (Postfix) with ESMTPS id 4B502418ED
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 16 Apr 2021 18:00:43 +0000 (UTC)
Received: from mail-io1-f49.google.com (mail-io1-f49.google.com
[209.85.166.49]) (authenticated bits=0)
(User authenticated as jlrubin@ATHENA.MIT.EDU)
by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 13GI0fZ7031859
(version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NOT)
for <bitcoin-dev@lists.linuxfoundation.org>; Fri, 16 Apr 2021 14:00:41 -0400
Received: by mail-io1-f49.google.com with SMTP id a9so17676550ioc.8
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 16 Apr 2021 11:00:41 -0700 (PDT)
X-Gm-Message-State: AOAM530UkWVvlMYiqIpiRX2Sf/t+CsUHjRPBBYRKMdsZOidlhBDOqnha
udv4hRYtVoJ3G3k30cA03YDRnH+qUqOSCijTE4o=
X-Google-Smtp-Source: ABdhPJyQ1lwQk9C7klcB2d99Z6Mjl2e0nPrwgtt5GsSbdUjNS/nkGJYpPhciuBhcDPCSi8GrmdzTZdpkXowl5aOD+Zo=
X-Received: by 2002:a5d:8d12:: with SMTP id p18mr4582083ioj.31.1618596041013;
Fri, 16 Apr 2021 11:00:41 -0700 (PDT)
MIME-Version: 1.0
References: <CAK=nyAxOa8fsVfxucH7WTTMn25BCzgQ28h_sNsunedpCoRXjjQ@mail.gmail.com>
<CAD5xwhiAPkxRxvgJNU3uG7LLToa-+9j7CdXYWvOYOpZKz-p7Hw@mail.gmail.com>
<CAK=nyAwbWbEkL29J-teW-NJ+28pgrCVEvP5csH65uzCWfP=9KA@mail.gmail.com>
In-Reply-To: <CAK=nyAwbWbEkL29J-teW-NJ+28pgrCVEvP5csH65uzCWfP=9KA@mail.gmail.com>
From: Jeremy <jlrubin@mit.edu>
Date: Fri, 16 Apr 2021 11:00:29 -0700
X-Gmail-Original-Message-ID: <CAD5xwhgFduuvJ22PhPat-RFYJ3swAhJyJxRufAGOJcQBe2+Y2A@mail.gmail.com>
Message-ID: <CAD5xwhgFduuvJ22PhPat-RFYJ3swAhJyJxRufAGOJcQBe2+Y2A@mail.gmail.com>
To: Christopher Gilliard <christopher.gilliard@gmail.com>
Content-Type: multipart/alternative; boundary="0000000000000f3dd705c01ac21b"
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP - limiting OP_RETURN / HF
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: Fri, 16 Apr 2021 18:00:47 -0000
--0000000000000f3dd705c01ac21b
Content-Type: text/plain; charset="UTF-8"
For every workaround, someone may have a long lost stash that you'd be
confiscating :)
https://bitcoin.stackexchange.com/questions/90127/why-does-this-coinbase-transaction-have-two-op-return-outputs
--0000000000000f3dd705c01ac21b
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div style=3D"font-family:arial,helvetica,sans-serif;font-=
size:small;color:rgb(0,0,0)" class=3D"gmail_default">For every workaround, =
someone may have a long lost stash that you'd be confiscating :)</div><=
div style=3D"font-family:arial,helvetica,sans-serif;font-size:small;color:r=
gb(0,0,0)" class=3D"gmail_default"><br></div><div style=3D"font-family:aria=
l,helvetica,sans-serif;font-size:small;color:rgb(0,0,0)" class=3D"gmail_def=
ault"><a href=3D"https://bitcoin.stackexchange.com/questions/90127/why-does=
-this-coinbase-transaction-have-two-op-return-outputs">https://bitcoin.stac=
kexchange.com/questions/90127/why-does-this-coinbase-transaction-have-two-o=
p-return-outputs</a></div><br></div>
--0000000000000f3dd705c01ac21b--
|
