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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <flavien.charlon@pixodegames.com>) id 1WYbJ7-00079Z-VN
for bitcoin-development@lists.sourceforge.net;
Fri, 11 Apr 2014 13:15:50 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of
pixodegames.com designates 209.85.215.47 as permitted sender)
client-ip=209.85.215.47;
envelope-from=flavien.charlon@pixodegames.com;
helo=mail-la0-f47.google.com;
Received: from mail-la0-f47.google.com ([209.85.215.47])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WYbJ6-0006Sz-JB
for bitcoin-development@lists.sourceforge.net;
Fri, 11 Apr 2014 13:15:49 +0000
Received: by mail-la0-f47.google.com with SMTP id pn19so3436167lab.20
for <bitcoin-development@lists.sourceforge.net>;
Fri, 11 Apr 2014 06:15:41 -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=prL+xFtmrZZvj9OgoSIus2R6Z/awkIULOS/MLDRPeJI=;
b=WoNx0T77PZ8xdc+ho67VFtIqh6/VbOwIiJ6WQY+P5FCt1VIAb66EcYGlluFycdC9So
6Yyet4id9wX8wWr48omebu05i3PJW1z8ZotdxGjT5X2I4n8lScZrY1IJP1FC37vGo06B
nxqwKyEcS8VCwk5jzi7pVvg1cZmBjP8DPIZgmdzGMR3hl+MN1Nz24HVBx5Y5fVmkkQqc
/rhSGBWQiIdNa6P88CHhgT5STaLTdfRO8R6WktllLDlGgs1XafgyZxQ4SccMQAJO07sv
xc1aYdwiPBkk0sPetWaBlpxCA37jp6g3bi4C+rgSXSS7cvYRW/JP2uVuFk+jocjaCN78
f75Q==
X-Gm-Message-State: ALoCoQk6FtPKoiEBHrk7ku/oF7PXvu3cHI7LxarfX8nD0qsTx8eKBGTUjE+ezzMgjMqu9Wy7+5wR
X-Received: by 10.112.61.199 with SMTP id s7mr329154lbr.25.1397220711478;
Fri, 11 Apr 2014 05:51:51 -0700 (PDT)
Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com
[209.85.217.182])
by mx.google.com with ESMTPSA id cq4sm7149340lad.5.2014.04.11.05.51.50
for <bitcoin-development@lists.sourceforge.net>
(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
Fri, 11 Apr 2014 05:51:50 -0700 (PDT)
Received: by mail-lb0-f182.google.com with SMTP id n15so3485936lbi.13
for <bitcoin-development@lists.sourceforge.net>;
Fri, 11 Apr 2014 05:51:50 -0700 (PDT)
X-Received: by 10.152.21.200 with SMTP id x8mr984817lae.58.1397220710633; Fri,
11 Apr 2014 05:51:50 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.114.185.230 with HTTP; Fri, 11 Apr 2014 05:51:10 -0700 (PDT)
X-Originating-IP: [2a01:110:8:1003:494e:7ce7:f38e:659a]
In-Reply-To: <CAE28kUSWwamovgPA1AvAojoKuwaDvuWzbnYf6yJhQ89HRnOJGg@mail.gmail.com>
References: <CABbpET96CboPcQeV-nKXv-CeaPiwpTKVUB_ioGPB2s3_5Y7bnQ@mail.gmail.com>
<5341E1FF.7080204@monetize.io>
<CABbpET_JFceNhRkxSZMyiTxkkYr2MvQVob7o4juEsPj4wo8e8g@mail.gmail.com>
<CAC1+kJMpEetKdpKs-OaFGvnBwi6-Pj8ycJ77cJzHOTk_jUPw=g@mail.gmail.com>
<CABbpET-S5ahuQVcBaJZGyvFMS1=RU2mJZUAmECBKhFOFu6B6EA@mail.gmail.com>
<5342BEE0.3050204@monetize.io>
<CABbpET8Qbvhb47ZJX4EVh4673_ic9UwpMdMyZbsHay9F2zTj9Q@mail.gmail.com>
<CAC1+kJPBH85p8Mgu0_7+1JxizgX19a-HWWF+38BLA7DZ4Ldd6g@mail.gmail.com>
<CABbpET8DaEKbafX6Cju_e+ygeV1WDf_LXQKU6tTofh32R9XM=Q@mail.gmail.com>
<CAE28kURu7-OgY6vN0az6rQUGpChK76ZQL9_eL1J4j-HZOqhRYA@mail.gmail.com>
<CABbpET93YxPepKLHFKKabr6P7vpkRDOouVuo8zmWAf3FKc85Cg@mail.gmail.com>
<5346CDD4.8050206@monetize.io>
<CAE28kUSWwamovgPA1AvAojoKuwaDvuWzbnYf6yJhQ89HRnOJGg@mail.gmail.com>
From: Flavien Charlon <flavien.charlon@coinprism.com>
Date: Fri, 11 Apr 2014 13:51:10 +0100
Message-ID: <CABbpET_bP5tgXBzOCoEaO3iQof4A5tFF1-BxO4JYHrvKN-TU_A@mail.gmail.com>
To: Alex Mizrahi <alex.mizrahi@gmail.com>
Content-Type: multipart/alternative; boundary=089e0158aef421664404f6c3ccfb
X-Spam-Score: -0.6 (/)
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
-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
X-Headers-End: 1WYbJ6-0006Sz-JB
Cc: Bitcoin Dev <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: Fri, 11 Apr 2014 13:15:50 -0000
--089e0158aef421664404f6c3ccfb
Content-Type: text/plain; charset=ISO-8859-1
I have updated the
spec<https://github.com/Flavien/colored-coins-protocol/blob/master/specification.mediawiki>
.
> This is an interesting approach, but OP_RETURN size limitations can be a
significant problem for some kinds of applications.
This is correct, the number of colored outputs you can have per transaction
is limited by OP_RETURN's 40 bytes. We use a compact format
(LEB128<http://en.wikipedia.org/wiki/LEB128>)
for the asset quantity of each output to mitigate that. Assuming you're
transferring small amounts of colored coins, you could have up to about 30
colored ouputs.
It should work for a decentralized exchange (you only really need 2 or 3
colored outputs). Applications like sending dividends in colored coins
however may require splitting into several smaller transactions, but I
believe that's an acceptable limitation.
On Thu, Apr 10, 2014 at 6:24 PM, Alex Mizrahi <alex.mizrahi@gmail.com>wrote:
>
>
>> At this point, I don't think what you are doing is even colored coins
>> anymore. You might want to look into Counterparty or Mastercoin.
>>
>
> Nope, it's still colored coins. The difference between colored coin model
> and Mastercoin model is that colored coins are linked to transaction
> outputs, while Mastercoin has a notion of address balances.
>
> The implications of this is that in colored coin model explicit
> dependencies allow us to rely on SPV. (Assuming that one can fetch the
> dependency graph to link txout in question to genesis.)
> While it is not the case with Mastercoin.
>
> While it's pretty far from the original colored coins model, what Flavien
> have described is identical to it in majority of aspects.
>
> This is an interesting approach, but OP_RETURN size limitations can be a
> significant problem for some kinds of applications.
>
>
> ------------------------------------------------------------------------------
> Put Bad Developers to Shame
> Dominate Development with Jenkins Continuous Integration
> Continuously Automate Build, Test & Deployment
> Start a new project now. Try Jenkins in the cloud.
> http://p.sf.net/sfu/13600_Cloudbees
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
--089e0158aef421664404f6c3ccfb
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div>I have updated the <a href=3D"https://github.com/Flav=
ien/colored-coins-protocol/blob/master/specification.mediawiki">spec</a>.</=
div><div><br></div><div>> This is an interesting approach, but OP_RETURN=
size limitations can be a significant problem for some kinds of applicatio=
ns.</div>
<div><br></div><div>This is correct, the number of colored outputs you can =
have per transaction is limited by=A0OP_RETURN's 40 bytes. We use a com=
pact format (<a href=3D"http://en.wikipedia.org/wiki/LEB128">LEB128</a>) fo=
r the asset quantity of each output to mitigate that. Assuming you're t=
ransferring small amounts of colored coins, you could have up to about 30 c=
olored ouputs.</div>
<div><br></div><div>It should work for a decentralized exchange (you only r=
eally need 2 or 3 colored outputs). Applications like sending dividends in =
colored coins however may require splitting into several smaller transactio=
ns, but I believe that's an acceptable limitation.</div>
</div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Thu,=
Apr 10, 2014 at 6:24 PM, Alex Mizrahi <span dir=3D"ltr"><<a href=3D"mai=
lto:alex.mizrahi@gmail.com" target=3D"_blank">alex.mizrahi@gmail.com</a>>=
;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_extra">=
<div class=3D"gmail_quote"><div><div>=A0</div><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:r=
gb(204,204,204);border-left-width:1px;border-left-style:solid">
<div>
</div>At this point, I don't think what you are doing is even colored c=
oins<br>
anymore. You might want to look into Counterparty or Mastercoin.<br></block=
quote><div><br></div></div><div>Nope, it's still colored coins. The dif=
ference between colored coin model and Mastercoin model is that colored coi=
ns are linked to transaction outputs, while Mastercoin has a notion of addr=
ess balances.</div>
<div><br></div><div>The implications of this is that in colored coin model =
explicit dependencies allow us to rely on SPV. (Assuming that one can fetch=
the dependency graph to link txout in question to genesis.)=A0</div><div>
While it is not the case with Mastercoin.</div><div><br></div><div>While it=
's pretty far from the original colored coins model, what Flavien have =
described is identical to it in majority of aspects.</div><div><br></div>
<div>This is an interesting approach, but OP_RETURN size limitations can be=
a significant problem for some kinds of applications.</div></div></div></d=
iv>
<br>-----------------------------------------------------------------------=
-------<br>
Put Bad Developers to Shame<br>
Dominate Development with Jenkins Continuous Integration<br>
Continuously Automate Build, Test & Deployment<br>
Start a new project now. Try Jenkins in the cloud.<br>
<a href=3D"http://p.sf.net/sfu/13600_Cloudbees" target=3D"_blank">http://p.=
sf.net/sfu/13600_Cloudbees</a><br>_________________________________________=
______<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@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>
<br></blockquote></div><br></div>
--089e0158aef421664404f6c3ccfb--
|
