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
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <flavien.charlon@pixodegames.com>) id 1WX6CS-0007yK-3w
for bitcoin-development@lists.sourceforge.net;
Mon, 07 Apr 2014 09:50:44 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of
pixodegames.com designates 209.85.215.49 as permitted sender)
client-ip=209.85.215.49;
envelope-from=flavien.charlon@pixodegames.com;
helo=mail-la0-f49.google.com;
Received: from mail-la0-f49.google.com ([209.85.215.49])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WX6CQ-00088B-N4
for bitcoin-development@lists.sourceforge.net;
Mon, 07 Apr 2014 09:50:44 +0000
Received: by mail-la0-f49.google.com with SMTP id mc6so4437738lab.8
for <bitcoin-development@lists.sourceforge.net>;
Mon, 07 Apr 2014 02:50:36 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:from:date
:message-id:subject:to:cc:content-type;
bh=F8mh5CRkIXxBLzdEcpYoW7GO0+mrVBT3ZorKnv04Dr0=;
b=encBrZW6g6cnT38ngdueLFMktTgS2t3MjvqXm8umoo0LPAAHabo6Qz7wayDMBsbS72
+8J3jX4IbDNTuTTVgxCgP2ihJLV2zWH2Ss5KPg6/ZRTJ/GJy1y/3+rc7HOaLbs4YFs4J
S4RoJduSNf3c78C4JCZ6xrv4DHWlO5sDHWVEq1xjkHVH7JQbtaWf8UUgaa24Y3Cwdy20
BnRtSysQ6OElU1ZFGYhPOa2XGTUBtWPcbXV2BRaODzxv8nEk4x13w11GbDlx2JNID7iA
wMqAGiH8zgihNcj7NUKa8Iorp6EcubiqQaD+iLnMldOXYPIc7vZsJgHmkvmMb/OFSGVm
3FTQ==
X-Gm-Message-State: ALoCoQmnEg4g1BdWCeQsduhFrU8rKUmSzlc0MDDwKx4gVxhG1Qtb8KiFWrfxNDWyTKPug46oY/Pq
X-Received: by 10.112.186.98 with SMTP id fj2mr393449lbc.54.1396864235971;
Mon, 07 Apr 2014 02:50:35 -0700 (PDT)
Received: from mail-lb0-f174.google.com (mail-lb0-f174.google.com
[209.85.217.174]) by mx.google.com with ESMTPSA id
kk4sm11563990lbb.22.2014.04.07.02.50.35
for <bitcoin-development@lists.sourceforge.net>
(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
Mon, 07 Apr 2014 02:50:35 -0700 (PDT)
Received: by mail-lb0-f174.google.com with SMTP id u14so4495024lbd.19
for <bitcoin-development@lists.sourceforge.net>;
Mon, 07 Apr 2014 02:50:35 -0700 (PDT)
X-Received: by 10.152.115.133 with SMTP id jo5mr159937lab.54.1396864235456;
Mon, 07 Apr 2014 02:50:35 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.114.185.230 with HTTP; Mon, 7 Apr 2014 02:49:55 -0700 (PDT)
X-Originating-IP: [82.127.2.238]
In-Reply-To: <5341E1FF.7080204@monetize.io>
References: <CABbpET96CboPcQeV-nKXv-CeaPiwpTKVUB_ioGPB2s3_5Y7bnQ@mail.gmail.com>
<5341E1FF.7080204@monetize.io>
From: Flavien Charlon <flavien.charlon@coinprism.com>
Date: Mon, 7 Apr 2014 10:49:55 +0100
Message-ID: <CABbpET_JFceNhRkxSZMyiTxkkYr2MvQVob7o4juEsPj4wo8e8g@mail.gmail.com>
To: Mark Friedenbach <mark@monetize.io>
Content-Type: multipart/alternative; boundary=001a11c34dd08ddb7e04f670cc8a
X-Spam-Score: 2.1 (++)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
1.2 RCVD_IN_BL_SPAMCOP_NET RBL: Received via a relay in bl.spamcop.net
[Blocked - see <http://www.spamcop.net/bl.shtml?209.85.217.174>]
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
1.5 SF_NO_SPF_SPAM SF_NO_SPF_SPAM
X-Headers-End: 1WX6CQ-00088B-N4
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Feedback request: colored coins protocol
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: Mon, 07 Apr 2014 09:50:44 -0000
--001a11c34dd08ddb7e04f670cc8a
Content-Type: text/plain; charset=ISO-8859-1
Thanks for the feedback Mark.
> (1) there is absolutely no reason to include asset tagging information if
it is not validated
Sure, there is a good reason to include it in the blockchain: so that
clients don't need external information to recognize colored coins. Also,
I'm not sure what you mean by "not validated", in that proposal, the tagged
transaction is the authoritative source of information.
> that just bloats the block chain
9 bytes is much less than what Mastercoin and counterparty are doing
(certainly under the 40 bytes allowed).
> Have you seen the padded order-based coloring scheme worked out here?
Yes I have seen it and find the padding quite clumsy and unintuitive. A
more general solution is the one I described in my original post, where the
color value is entirely separate from the satoshi value, and encoded
separately: if you have to have an additional "padding" value to calculate
color_value = satoshi_value - padding, you might as well have color_value
directly, independently from satoshi_value. But I don't even think it is
necessary:
> (2) And needing a capital of 54 btc for a million shares is totally
unacceptable.
An easy workaround is to have various scales, the same way you have $1
bills, $5 bills an $10 bills. I don't see that as a big problem. That way
the protocol is more lightweight and simple.
Also those 54 BTC (actually 5.4 BTC if the dust is now 540 satoshis) become
part of the capital of the company, and can always be recovered by
uncoloring the shares. It's an investment, not an expense, so I think it is
acceptable.
Best,
Flavien
On Mon, Apr 7, 2014 at 12:23 AM, Mark Friedenbach <mark@monetize.io> wrote:
> On 04/06/2014 01:59 PM, Flavien Charlon wrote:
> > Do you think this is the right approach?
>
> No, I'm afraid it has significant flaws. The two chief flaws are (1)
> there is absolutely no reason to include asset tagging information if it
> is not validated - that just bloats the block chain, and (2) you
> shouldn't be using fixed increments for share sizes either. It's not
> future-proof as the minimum output size changes based on the minimum fee
> (currently 540 satoshis, not 5,400, and it will float in the near
> future). And needing a capital of 54 btc for a million shares is totally
> unacceptable.
>
> Flavien, I know that I've seen you on the Bitcoin-X mailing list, where
> these issues have been mostly worked out:
>
> https://groups.google.com/forum/#!forum/bitcoinx
>
> Have you seen the padded order-based coloring scheme worked out here?
>
> https://github.com/bitcoinx/colored-coin-tools/wiki/colored_coins_intro
>
> Kind regards,
> Mark Friedenbach
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--001a11c34dd08ddb7e04f670cc8a
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div>Thanks for the feedback Mark.</div><div><br></div><di=
v>> (1) there is absolutely no reason to include asset tagging informati=
on if it is not validated</div><div><br></div><div>Sure, there is a good re=
ason to include it in the blockchain: so that clients don't need extern=
al information to recognize colored coins. Also, I'm not sure what you =
mean by "not validated", in that proposal, the tagged transaction=
is the authoritative source of information.</div>
<div><br></div><div>> that just bloats the block chain</div><div><br></d=
iv><div>9 bytes is much less than what Mastercoin and counterparty are doin=
g (certainly under the 40 bytes allowed).</div><div><br></div><div>> Hav=
e you seen the padded order-based coloring scheme worked out here?</div>
<div><br></div><div>Yes I have seen it and find the padding quite clumsy an=
d unintuitive. A more general solution is the one I described in my origina=
l post, where the color value is entirely separate from the satoshi value, =
and encoded separately: if you have to have an additional "padding&quo=
t; value to calculate color_value =3D=A0satoshi_value - padding, you might =
as well have color_value directly, independently from satoshi_value. But I =
don't even think it is necessary:<br>
</div><div><br></div><div>> (2) And needing a capital of 54 btc for a mi=
llion shares is totally unacceptable.</div><div><br></div><div>An easy work=
around is to have various scales, the same way you have $1 bills, $5 bills =
an $10 bills. I don't see that as a big problem. That way the protocol =
is more lightweight and simple.</div>
<div><br></div><div>Also those 54 BTC (actually 5.4 BTC if the dust is now =
540 satoshis) become part of the capital of the company, and can always be =
recovered by uncoloring the shares. It's an investment, not an expense,=
so I think it is acceptable.</div>
<div><br></div><div>Best,</div><div>Flavien</div><div><br></div><div><br></=
div><div><br></div><div><br></div><div class=3D"gmail_extra"><br><br><div c=
lass=3D"gmail_quote">On Mon, Apr 7, 2014 at 12:23 AM, Mark Friedenbach <spa=
n dir=3D"ltr"><<a href=3D"mailto:mark@monetize.io" target=3D"_blank">mar=
k@monetize.io</a>></span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;padding=
-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-l=
eft-style:solid"><div>On 04/06/2014 01:59 PM, Flavien Charlon wrote:<br>
> Do you think this is the right approach?<br>
<br>
</div>No, I'm afraid it has significant flaws. The two chief flaws are =
(1)<br>
there is absolutely no reason to include asset tagging information if it<br=
>
is not validated - that just bloats the block chain, and (2) you<br>
shouldn't be using fixed increments for share sizes either. It's no=
t<br>
future-proof as the minimum output size changes based on the minimum fee<br=
>
(currently 540 satoshis, not 5,400, and it will float in the near<br>
future). And needing a capital of 54 btc for a million shares is totally<br=
>
unacceptable.<br>
<br>
Flavien, I know that I've seen you on the Bitcoin-X mailing list, where=
<br>
these issues have been mostly worked out:<br>
<br>
<a href=3D"https://groups.google.com/forum/#!forum/bitcoinx" target=3D"_bla=
nk">https://groups.google.com/forum/#!forum/bitcoinx</a><br>
<br>
Have you seen the padded order-based coloring scheme worked out here?<br>
<br>
<a href=3D"https://github.com/bitcoinx/colored-coin-tools/wiki/colored_coin=
s_intro" target=3D"_blank">https://github.com/bitcoinx/colored-coin-tools/w=
iki/colored_coins_intro</a><br>
<br>
Kind regards,<br>
Mark Friedenbach<br>
<br>
---------------------------------------------------------------------------=
---<br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net" target=3D"_bla=
nk">Bitcoin-development@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
</blockquote></div><br></div></div>
--001a11c34dd08ddb7e04f670cc8a--
|
