blob: e2cb06f1da14ab3c5975d33bb46be77011390c16 (
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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mark@monetize.io>) id 1Wgf5m-0007q1-Dx
for bitcoin-development@lists.sourceforge.net;
Sat, 03 May 2014 18:55:22 +0000
Received: from mail-pa0-f47.google.com ([209.85.220.47])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Wgf5l-00064i-5f
for bitcoin-development@lists.sourceforge.net;
Sat, 03 May 2014 18:55:22 +0000
Received: by mail-pa0-f47.google.com with SMTP id fa1so7188179pad.20
for <bitcoin-development@lists.sourceforge.net>;
Sat, 03 May 2014 11:55:15 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:message-id:date:from:organization:user-agent
:mime-version:to:subject:references:in-reply-to:content-type
:content-transfer-encoding;
bh=aQr2HlduwShiOT339xDmFaD5VUkmD2PqpYG87cvoYqU=;
b=X4gJAzIER9InNZEP0SOvXT+fy9d5K9Zw3Y8dYBA41Tb1aZ1IdIWPieTsS9Y+k/52Zi
eGviwAWcdBT9aWkwfOHM5vZJ8G5NGo80iUGE1s9u1aDzajZ7t7TTsqE8mZsO9oZdxsEy
5qQ2maB+vLM0Uw1XB5OnL8shef3AViA6NCLNE5bi1UIbGZ62kknyFwjoN3i4JulAFafS
Cu/dTUwNjwYE4YjCaCF2BL/h8aVc5RvwluSqnsJnNTo5FVqQq5lj3iVeMPPaCKV3Qn4u
9nVRgRNLLV26m+GSv3YhUPMdyFKv0B1+ztJ59Weh8Nx7a46yzSxDA4bmDFm4XhF+LP8E
n6sA==
X-Gm-Message-State: ALoCoQnAwixdaGaqTIhmNVH5Ey7kq8Dq2J1qFLljqSLteMqCRrhv75bA7xlRavbZee2vYw6PMR5k
X-Received: by 10.67.14.98 with SMTP id ff2mr50540589pad.101.1399143315183;
Sat, 03 May 2014 11:55:15 -0700 (PDT)
Received: from [192.168.127.239] (50-0-36-93.dsl.dynamic.sonic.net.
[50.0.36.93]) by mx.google.com with ESMTPSA id
nx12sm25243939pab.6.2014.05.03.11.55.13
for <bitcoin-development@lists.sourceforge.net>
(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
Sat, 03 May 2014 11:55:14 -0700 (PDT)
Message-ID: <53653B90.4070401@monetize.io>
Date: Sat, 03 May 2014 11:55:12 -0700
From: Mark Friedenbach <mark@monetize.io>
Organization: Monetize.io Inc.
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: bitcoin-development@lists.sourceforge.net
References: <CABbpET-uDQRFQ_XAFeWkgc=A1jEW62Q+8BTZZuW5UbZXX0y+HQ@mail.gmail.com>
<218332ea-948d-4af0-b4c5-ced83f25d734@email.android.com>
In-Reply-To: <218332ea-948d-4af0-b4c5-ced83f25d734@email.android.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
X-Headers-End: 1Wgf5l-00064i-5f
Subject: Re: [Bitcoin-development] Bug with handing of OP_RETURN?
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Sat, 03 May 2014 18:55:22 -0000
I don't think such a pull request would be accepted. The point was to
minimize impact to the block chain. Each extras txout adds 9 bytes
minimum, with zero benefit over serializing the data together in a
single OP_RETURN.
On 05/03/2014 11:39 AM, Peter Todd wrote:
> The standard format ended up being exactly:
>
> OP_RETURN <0 to 40-byte PUSHDATA>
>
> You've split the data across two PUSHDATA's. The standard should have let the data be split up like that; pull requests accepted.
>
|
