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; 
MIME-Version: 1.0
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
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Feedback request: colored coins protocol
Precedence: list

--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>&gt; 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&#39;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&#39;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&#39;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">&lt;<a href=3D"mai=
lto:alex.mizrahi@gmail.com" target=3D"_blank">alex.mizrahi@gmail.com</a>&gt=
;</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&#39;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&#39;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=
&#39;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 &amp; 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--