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
|
Return-Path: <ZmnSCPxj@protonmail.com>
Received: from smtp2.osuosl.org (smtp2.osuosl.org [IPv6:2605:bc80:3010::133])
by lists.linuxfoundation.org (Postfix) with ESMTP id F3CBBC0011
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 25 Feb 2022 00:05:03 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp2.osuosl.org (Postfix) with ESMTP id E0AD040150
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 25 Feb 2022 00:05:03 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -1.599
X-Spam-Level:
X-Spam-Status: No, score=-1.599 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001,
FROM_LOCAL_NOVOWEL=0.5, RCVD_IN_MSPIKE_H5=0.001,
RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001]
autolearn=ham autolearn_force=no
Authentication-Results: smtp2.osuosl.org (amavisd-new);
dkim=pass (2048-bit key) header.d=protonmail.com
Received: from smtp2.osuosl.org ([127.0.0.1])
by localhost (smtp2.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id xSsk4GIA5bw1
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 25 Feb 2022 00:05:02 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0
Received: from mail-40135.protonmail.ch (mail-40135.protonmail.ch
[185.70.40.135])
by smtp2.osuosl.org (Postfix) with ESMTPS id 93E0E4010C
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 25 Feb 2022 00:05:02 +0000 (UTC)
Date: Fri, 25 Feb 2022 00:04:54 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com;
s=protonmail3; t=1645747499;
bh=ryJyqVoGyKFM7/oRszaXJT9MzJK0X4LjooNHR4Yn3DI=;
h=Date:To:From:Cc:Reply-To:Subject:Message-ID:In-Reply-To:
References:From:To:Cc:Date:Subject:Reply-To:Feedback-ID:
Message-ID;
b=VRtnQ1a7fGfbcd8AxkxDW+tahuDrHaov2qnFNepU/AbMqpaIwvKg3MWmm7Z+K+kuq
1H+cLvPHFQp+Vwdlv9GKT0EMd9mKoDRicaP0MQvMdovpPaOJuHERBrn9x6cL35WWpp
FKDCwo6H/BqdpIUQs6YWQsY+a+oczd6LBZDmVSmjUvWRmcciT7y32AmBvO7UngfGxj
ETLBtUAy9pGBLqmEPNZvoM5doZVO4c5RNeo9jRy5VrCKfENbTQyj9a6CnhfjyXs0tw
B1m5xpBniGq26esTQKfu0L5O7CWVJtVRnVbvQzllCb9j1FYvOQ27W6bEk3xJmkVedE
Xj5QzlX/F1nmQ==
To: Zac Greenwood <zachgrw@gmail.com>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
From: ZmnSCPxj <ZmnSCPxj@protonmail.com>
Reply-To: ZmnSCPxj <ZmnSCPxj@protonmail.com>
Message-ID: <vmZt7irtItdhrsha-cHM0-HgzhCQ6GlWdJXr6mKzEHXmoNz5ypuQLR9eKsltreHb0O2kMfcr_VRkZ1hmoJ9RAp5DaMZorhG1JsRSclhin6s=@protonmail.com>
In-Reply-To: <CAJ4-pEBnprd-SdXMZeDsJ37=SiGbQEnaFfpvBzryR21Wbqc1Ew@mail.gmail.com>
References: <157744394-3dec42994f1798ce65b00e23b21ea656@pmq2v.m5r2.onet>
<CAJ4-pEBnprd-SdXMZeDsJ37=SiGbQEnaFfpvBzryR21Wbqc1Ew@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [bitcoin-dev] OP_RETURN inside TapScript
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, 25 Feb 2022 00:05:04 -0000
Good morning Zac,
> Reducing the footprint of storing data on-chain might better be achieved =
by *supporting* it.
>
> Currently storing data is wasteful because it is embedded inside an OP_RE=
TURN within a transaction structure. As an alternative, by supporting stori=
ng of raw data without creating a transaction, waste can be reduced.
If the data is not embedded inside a transaction, how would I be able to pa=
y a miner to include the data on the blockchain?
I need a transaction in order to pay a miner anyway, so why not just embed =
it into the same transaction I am using to pay the miner?
(i.e. the current design)
Regards,
ZmnSCPxj
|
