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
|
Return-Path: <jtimon@jtimon.cc>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id A676ABE6
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 15 Aug 2018 20:33:45 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-oi0-f46.google.com (mail-oi0-f46.google.com
[209.85.218.46])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 15942786
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 15 Aug 2018 20:33:45 +0000 (UTC)
Received: by mail-oi0-f46.google.com with SMTP id b16-v6so4186765oic.9
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 15 Aug 2018 13:33:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=jtimon-cc.20150623.gappssmtp.com; s=20150623;
h=mime-version:in-reply-to:references:from:date:message-id:subject:to
:content-transfer-encoding;
bh=nO/3E7LY7p7PPu/tBFm6kkluzxgQEP+uI8VMOBVOgX0=;
b=AyV5s1jQNI3waIAXU/ah63T5P4UQwDvEHKCkMQOSpAaAybCzgSDYnh0RU1KR6MYQ1u
bFhKa8ZukoOzHWPwu8NXsUqpmClKtnh5UPW52/trA7YKaEkA/A1OhGdTarMlkD/5Q14W
QB9XMYDYlkihiH32v86i4EvTCZPXfZaBntEhJUhsJMHQaoOyFUPRLyU05kjwB74MYCUr
/NTEoM3ARQO4NRF9tCnEM57DMzP07WhxtHP3a5RYhrrDzof1PQXhF2g7Y+xNHfczopRF
sFvzp9WrfW2lLNINH/S+/4I0BYLhPxY06txtEQzpPrZU7a5Fzvk0d4buTsgGBztQ5HLO
3MMg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:in-reply-to:references:from:date
:message-id:subject:to:content-transfer-encoding;
bh=nO/3E7LY7p7PPu/tBFm6kkluzxgQEP+uI8VMOBVOgX0=;
b=IsHaw6LdeUrlE9yJlL5hCargO30eAhE53gSsHgAPcQ9wBiCACwMVU3TfnsAagwI8nW
/T3hW61JNLYp09BoJUcxZp6cPIDwexu1xyb6X3sb95cgmUDT5Z1ATsu2x5R/RD51VVfU
diUn/qLhQJSTpLKTwyvgnH04OU8g3pYm36gOq+dAc5gN6En3b7P0EcA/pJOopUAy6k74
PKCNKnUJtFOU6XzuPXBmHRDyxmUK240yG1Y5gm7cDVeYE6DOor9h7tmN4xblME/Rh2v/
YrfZH8yyQtRe194m0AelqatFbBqE955DknSDGpORr1RsTm1MeL4ZKfuhtq5VfTa7zuUo
bjIA==
X-Gm-Message-State: AOUpUlGLElPXwUF6HThXAMvHKbuvtHSGNE+Qoc8mCSTIEtGSohnMlmEl
o/eR3jgOK3Omvv46TYWagvqDgcdH0uMM6f4fJxOCVSury98=
X-Google-Smtp-Source: AA+uWPz6Q3Fy45CMq6G5E8gy2/njHwLYENo0nXHQI9q5L4TeisWyGrKIVs64UiSiLzhFJQCUfBYFHODGV4pG39reWbY=
X-Received: by 2002:aca:bec2:: with SMTP id
o185-v6mr29832069oif.22.1534365224318;
Wed, 15 Aug 2018 13:33:44 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a4a:d1b3:0:0:0:0:0 with HTTP; Wed, 15 Aug 2018 13:33:43
-0700 (PDT)
In-Reply-To: <CACrqygD_5jpkTvvcFo7eHxZfiH4evzZQc=YB=opBo6M_0EsZTQ@mail.gmail.com>
References: <CACrqygD_5jpkTvvcFo7eHxZfiH4evzZQc=YB=opBo6M_0EsZTQ@mail.gmail.com>
From: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= <jtimon@jtimon.cc>
Date: Wed, 15 Aug 2018 22:33:43 +0200
Message-ID: <CABm2gDpOvXg7_Yv9jkX=+a7ALXHgA5-4Oh4ZQnzp=pw5-0bZPA@mail.gmail.com>
To: Christopher Allen <ChristopherA@lifewithalacrity.com>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Spam-Status: No, score=-0.9 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, FROM_EXCESS_BASE64,
RCVD_IN_DNSWL_NONE autolearn=no version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Subject: Re: [bitcoin-dev] Claiming an OP_RETURN Prefix
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: Wed, 15 Aug 2018 20:33:45 -0000
op_return outputs can be pruned because they are not spendable.
putting a hash on in the witness script data won't make things better
(it would actually make them worse) and it definitely doesn't help
"block size bloat".
I think I'm missing some context, but if you're using op_return purely
for timestamping I would recommend using pay 2 contract instead.
On Tue, Aug 14, 2018 at 8:34 PM, Christopher Allen via bitcoin-dev
<bitcoin-dev@lists.linuxfoundation.org> wrote:
> On August 5, 2018 9:11:26 PM UTC, Lautaro Dragan via bitcoin-dev
> <bitcoin-dev at lists.linuxfoundation.org> wrote:
>>Should we actually be using the BIP process to claim a prefix?
>
> I recommend against using an op_return prefix, as they allow for transact=
ion
> censorship.
>
> In fact, in our case, where we use an IPFS hash in an op_return, we remov=
e
> the IPFS multihash prefix information to post a =E2=80=9Cbare=E2=80=9D SH=
A256 hash to look
> like many other hashes being posted in op_returns, to minimize any abilit=
y
> for a miner to identify our transaction. The more projects that do this t=
he
> better =E2=80=94 a form of herd immunity.
>
> Longer term I=E2=80=99m looking for more responsible ways to publish this=
hash, for
> instance have the hash be in the witness script data, so that it can be
> easily purged from nodes that do not wish to preserve it and prevent bloc=
k
> size bloat. However, to do so everyone has to do it the same way, ideally
> have it look like any other transaction. I=E2=80=99ve not quite seen a so=
lid
> proposal for best practices here.
>
> =E2=80=94 Christopher Allen
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
|
