summaryrefslogtreecommitdiff
path: root/90/8ba503d40b2a033674a1a56502bc103cc39aba
blob: 5a694fde471c8313253e73dfaa0e8602c89bbb87 (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
Return-Path: <christophera@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 5944DD4B
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed, 15 Aug 2018 21:55:04 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-oi0-f44.google.com (mail-oi0-f44.google.com
	[209.85.218.44])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 00DD280C
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed, 15 Aug 2018 21:55:03 +0000 (UTC)
Received: by mail-oi0-f44.google.com with SMTP id b15-v6so4537387oib.10
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed, 15 Aug 2018 14:55:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=lifewithalacrity-com.20150623.gappssmtp.com; s=20150623;
	h=mime-version:references:in-reply-to:from:date:message-id:subject:to; 
	bh=4AKo9MTqpy4r4CH4QNLxNnQYoW5zh4hUQwwMrpzXqfs=;
	b=iSOKIILrxeCpJXB3xLcDla3p6mm1Crtbv4O4OjSm2rOW4W9vpwGG8FyLvLyUhKWtR5
	PIT8hSPUxdeOupl56p9HnZrlDaC7Qt5FnYT9y/r1SsRHrGj2Qpl7nK1vVCWZYXzdOGSi
	8adUHG3c45rSsnGxZVQhK+mCZYKJG6bv5zmDJhsBzWwZOIdP7E1U4fp2RkDlfHBpZST3
	5t4jfR4hf1+uBxim3LKKhqRH+iR/N9X6pW6YVTCSjRHODzx3TMKv0SkoTu0aoGWMKbda
	QA0Nzuuv9AW03d6YvkWLKPD1SRL/GQ0WM5Rb7Fz5+MpmeAbzVws60GrOzHmmUJrkb8Qe
	rDHQ==
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=4AKo9MTqpy4r4CH4QNLxNnQYoW5zh4hUQwwMrpzXqfs=;
	b=ra2r+gz9TxhL5mvd3MHQYf2tu0FjCDAE4w014mZlX6w406jNoPDUGjmSwP1Bf8vNHj
	ZCAFl1IKvCw+xHOG2lETpnXxSCNtEejMI9iGXdu9O6YUyABrD75ArNeBNp8NSYg+wZ5S
	RrM4vAu+6iFQoqe4uvFQptpFOrSPCOTZ+sQRcsZ3HP78+ZsHfZ8TnW2agAo3zrdNmtnR
	bjzRK1UOrPxYjKI5D74dSkyZauGPb06zGeBS9lounzGkcXQ4xfPb7iv3CAsorTQAFDOe
	c8iNeopJA/F/2yt78yYcqxVj5u5JwH3DDwhv9/Sn4MTQNt2My/DBVgU39hS/2l30+u5H
	HZ9A==
X-Gm-Message-State: AOUpUlGiUWCt0mN313cfXu/iy5folOgBnssMpMUL3rkHRTAgofYdFNMn
	rAK/1cdfj9pHeaJew8J93BYUbUsETXSWQ7Hqc7as7g==
X-Google-Smtp-Source: AA+uWPy1QJU2ByO0KF0ORv6WIDh+dzfEoxbgwZTeRWhOH/b1jMNggknXWoFz83IQqANCt8WzmGKUpo3Ayzvg9KVsPis=
X-Received: by 2002:aca:5754:: with SMTP id
	l81-v6mr30799743oib.100.1534370102862; 
	Wed, 15 Aug 2018 14:55:02 -0700 (PDT)
MIME-Version: 1.0
References: <CACrqygD_5jpkTvvcFo7eHxZfiH4evzZQc=YB=opBo6M_0EsZTQ@mail.gmail.com>
	<CABm2gDpOvXg7_Yv9jkX=+a7ALXHgA5-4Oh4ZQnzp=pw5-0bZPA@mail.gmail.com>
	<CAFsQEP1ttFbAZZzz49Jg3E3jbZjztNRDVGJAKOWULYzrn+7obQ@mail.gmail.com>
In-Reply-To: <CAFsQEP1ttFbAZZzz49Jg3E3jbZjztNRDVGJAKOWULYzrn+7obQ@mail.gmail.com>
From: Christopher Allen <ChristopherA@lifewithalacrity.com>
Date: Wed, 15 Aug 2018 14:54:50 -0700
Message-ID: <CACrqygBJ=RdPpHqHzPNqqj0V2w5XL6GVtKobOWnj1EsVykUS8w@mail.gmail.com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>,
	Jude Nelson <judecn@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000ef6bed05738060af"
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID, FREEMAIL_FROM, 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: Thu, 16 Aug 2018 00:35:28 +0000
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 21:55:04 -0000

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

On Wed, Aug 15, 2018 at 2:24 PM Jude Nelson via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> Can a miner identify which transactions came from your software simply by
> running a copy themselves?  If so, then they can censor your transactions
> no matter how you encode them.
>

Possibly, but in the IPFS case I suspect the latency required to inspect
all hashes would likely  impact the ability of the miner to succeed in the
block. (True? I don=E2=80=99t touch mining software.)

Thus as long as all hashes look the same, and there are multiple content
addressable schemes that use hashes that have to be searched in order to
know to censor, you have to censor all or none.

=E2=80=94 Christopher Allen

>

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

<div>On Wed, Aug 15, 2018 at 2:24 PM Jude Nelson via bitcoin-dev &lt;<a hre=
f=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">bitcoi=
n-dev@lists.linuxfoundation.org</a>&gt; wrote:<br></div><div><div class=3D"=
gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;b=
order-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div>Can a min=
er identify which transactions came from your software simply by running a =
copy themselves?=C2=A0 If so, then they can censor your transactions no mat=
ter how you encode them.</div></div></blockquote><div dir=3D"auto"><br></di=
v><div dir=3D"auto">Possibly, but in the IPFS case I suspect the latency re=
quired to inspect all hashes would likely =C2=A0impact the ability of the m=
iner to succeed in the block. (True? I don=E2=80=99t touch mining software.=
)</div><div dir=3D"auto"><br></div><div dir=3D"auto">Thus as long as all ha=
shes look the same, and there are multiple content addressable schemes that=
 use hashes that have to be searched in order to know to censor, you have t=
o censor all or none.</div><div dir=3D"auto"><br></div><div dir=3D"auto">=
=E2=80=94 Christopher Allen</div><blockquote class=3D"gmail_quote" style=3D=
"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D=
"ltr"><div></div></div></blockquote></div></div>

--000000000000ef6bed05738060af--