summaryrefslogtreecommitdiff
path: root/02/9a07037b69d18ab8e41876060162511e9d2ab3
blob: 26bc2152b3b244765a6d465ea692c81d1ac47cb1 (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
Return-Path: <ctpacia@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id E9951C03
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Mon,  9 Jan 2017 04:32:55 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-qt0-f169.google.com (mail-qt0-f169.google.com
	[209.85.216.169])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 7C165A1
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Mon,  9 Jan 2017 04:32:55 +0000 (UTC)
Received: by mail-qt0-f169.google.com with SMTP id x49so60412057qtc.2
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sun, 08 Jan 2017 20:32:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=subject:to:references:from:message-id:date:user-agent:mime-version
	:in-reply-to:content-transfer-encoding;
	bh=c+sO0kkaIlOVcCaX+ajHbWQ1gqeHw6eQlIbs0lFFvOY=;
	b=R3rUZ1gTexVDN6p7Ez/NhU8p+SU0g/4nNNQhglh/Pl/0u0zRg/mp37if1bzMmzxqSa
	+7rK0cdrqV4zMIOCklmzI8HVXuKXmghfsFPyK7oxUYeVVACuCFTcNjPWSQ1jlLUPNwZc
	yV+NRYc8JiFD4DsRxuOONnZCXMaIz3KpJP+1DfuPV/1n6mvUlTEI62nV1tmLni/re1ck
	fAQxoq4cEaRB5Dn7gWRkaIDJOa4GL+BiXAaRGMgMzkYg5z/ZIanrzBKLzR/dT0mwMreu
	GZYx6ZitVm7L0ziCrD/PBhfgx+lujVA17mKkEpiQGReBWnpHjsN0Qwzrn/qBrFCFZ39g
	69Fw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:subject:to:references:from:message-id:date
	:user-agent:mime-version:in-reply-to:content-transfer-encoding;
	bh=c+sO0kkaIlOVcCaX+ajHbWQ1gqeHw6eQlIbs0lFFvOY=;
	b=Wfq7KQcUrCELuPpxarAzaOi41qKf78J1tegM6VaYuIVu4upEWMmUv0C+Cqwkly/d4m
	FYkHYEwhyG7vxTRWMzqajgVrzwUHrMj48PBPYHczwporRyX8KzdS72g0Y6ZXd3cwpuqG
	FLXBKvsigVe6BpEpxVE3AtjogwM8Zj5mu+ec/DlxHBts4UTGNYQsnFoA+yQTCvJP1lkh
	cHr+cIexUMgOelufY+K3Kb50HuYKg8KoMQTdub7jgBgxDTOKtQ64hMKjKdqWJUGL0S2M
	/PS6aTBUcrj5G0h4O8xBS3XCuCZN6AJNfCR+sNx6GefyDVhdA6eS2GXk9Vc6ml3aDLAF
	jjLA==
X-Gm-Message-State: AIkVDXJWAkSMwEprOHhiaH9SwUrv4LHaWgWcyXFngKo3dvJ/vzbHsYLewKbg1o1SPl8Nlw==
X-Received: by 10.237.36.24 with SMTP id r24mr17001561qtc.229.1483936374565;
	Sun, 08 Jan 2017 20:32:54 -0800 (PST)
Received: from ?IPv6:2601:18d:8181:e4d0:5c3e:2e5e:422f:1752?
	([2601:18d:8181:e4d0:5c3e:2e5e:422f:1752])
	by smtp.gmail.com with ESMTPSA id
	t35sm5706900qtc.40.2017.01.08.20.32.53
	(version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
	Sun, 08 Jan 2017 20:32:54 -0800 (PST)
To: Luke Dashjr <luke@dashjr.org>,
	Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
References: <8c64f5db-7cac-3fde-85c0-a75d752c4192@gmail.com>
	<201701090308.58360.luke@dashjr.org>
From: Chris <ctpacia@gmail.com>
Message-ID: <7cc28f27-9917-6992-6de5-38fd91d42e29@gmail.com>
Date: Sun, 8 Jan 2017 23:32:53 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
	Thunderbird/45.5.1
MIME-Version: 1.0
In-Reply-To: <201701090308.58360.luke@dashjr.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-Spam-Status: No, score=-1.5 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE,
	RCVD_IN_SORBS_SPAM 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] Mutli-push op_return
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: Mon, 09 Jan 2017 04:32:56 -0000

Maybe I was too premature. The script wiki (which I realize might not be
up to date) says only one pushdata is allowed but I don't see that in
the code.

https://github.com/bitcoin/bitcoin/blob/e8cfe1ee2d01c493b758a67ad14707dca15792ea/src/policy/policy.cpp#L49

Am I missing something or am I correct to assume that multiple pushdatas
in op_return would normally be considered standard?


On 01/08/2017 10:08 PM, Luke Dashjr wrote:
> On Monday, January 09, 2017 2:09:09 AM Chris via bitcoin-dev wrote:
>> Would there be an objection to making op_return outputs with two
>> pushdatas standard (same max data size)?
> Standards (BIPs) need to describe a specific use case and protocol for doing 
> it.
>
> As you note, the default policy on most nodes is to allow such outputs.
>
> Luke
>