MIME-Version: 1.0
In-Reply-To: <CAJowKgJys93VTFuGA3ydcuqxcx_O6r0D7715Kgfyc+SP4P8J9A@mail.gmail.com>
References: <CA+1nnrmZAdzBn-FMBVMGtp4n7bbG8W0VEGvi1WopS-M49zBXpw@mail.gmail.com>
	<201605260353.06939.luke@dashjr.org>
	<20160705174636.GA24068@fedora-21-dvm>
	<201607060122.20593.luke@dashjr.org>
	<CAH+Axy5A-_oDoPjabyzzAF8kVq9DsFwonEYPp9EU+Hf_BP1-DA@mail.gmail.com>
	<CA+1nnrmsU5kLxuW=GJSmy8C7s6F3EM8sgFYoXDg1iM-eD2qzsg@mail.gmail.com>
	<CAJowKgJys93VTFuGA3ydcuqxcx_O6r0D7715Kgfyc+SP4P8J9A@mail.gmail.com>
From: Alex Mizrahi <alex.mizrahi@gmail.com>
Date: Tue, 2 Aug 2016 20:25:50 +0300
Message-ID: <CAE28kUSaTsQ4qyGK5t5D1KiEF3yf4LEjkFvy+SiGxDK5VeAo9Q@mail.gmail.com>
To: Erik Aronesty <erik@q32.com>, 
	Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary=001a1145b8e61dc0cc05391a0282
Cc: Nicolas Dorier <nicolas.dorier@gmail.com>
Subject: Re: [bitcoin-dev] BIP Number Request: Open Asset
Precedence: list

--001a1145b8e61dc0cc05391a0282
Content-Type: text/plain; charset=UTF-8

>
> I would love to see an RFC-style standard "multiple-colored-coin-protocol"
> written by reps from all of the major protocols and that meta-merges the
> features of these implementations
>

We actually tried to do that in 2014-2015, but that effort have failed...
Nobody was really interested in collaboration, each company only cared
about it's own product.
Especially Colu, they asked everyone for requirements, and then developed a
new protocol completely on their own without taking anyone's input.

I'm not sure that merging the protocols makes sense, as some protocols
value simplicity, and a combined protocol cannot have this feature.

I don't think there is much interest in a merged colored coin protocol now.
Colu is moving away from colored coins, as far as I can tell.
CoinSpark is now doing MultiChain closed-source private blockchain.
CoinPrism also seems to be largely disinterested in colored coins.

We (ChromaWay) won't mind replacing EPOBC with something better, our
software could always support multiple different kernels so adding a new
protocol isn't a big deal for us.

So if somebody is interested in a new protocol please ping me.

One of ideas I have is to decouple input-output mapping/multiplexing from
coloring.
So one layer will describe a mapping, e.g. "Inputs 0 and 1 should go into
outputs 0, 1 and 2".
In this case it will be possible to create more advanced protocols (e.g.
with support for 'smart contracts' and whatnot) while also keeping them
compatible with old ones to some extent, e.g. a wallet can safely engage in
p2ptrade or CoinJoin transactions without understanding all protocols used
in a transaction.


> - in collaboration with feedback from core developers that understand the
> direction the protocol will be taking and the issues to avoid.
>

Core developers generally dislike things like colored coins, so I doubt
they are going to help.

Blockstream is developing a sidechain with user-defined assets, so I guess
they see it as the preferred way of doing things:
https://elementsproject.org/elements/asset-issuance/


> As it stands, investors have to install multiple wallets to deal with
> these varying implementations.
>

Actually this can be solved without making a new "merged protocol": one can
just implement a wallet which supports multiple protocols.

--001a1145b8e61dc0cc05391a0282
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left=
-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);paddi=
ng-left:1ex"><div dir=3D"ltr"><div><div><div><div>I would love to see an RF=
C-style standard &quot;multiple-colored-coin-protocol&quot; written by reps=
 from all of the major protocols and that meta-merges the features of these=
 implementations</div></div></div></div></div></blockquote><div><br></div><=
div>We actually tried to do that in 2014-2015, but that effort have failed.=
..</div><div>Nobody was really interested in collaboration, each company on=
ly cared about it&#39;s own product.</div><div>Especially Colu, they asked =
everyone for requirements, and then developed a new protocol completely on =
their own without taking anyone&#39;s input.</div><div><br></div><div>I&#39=
;m not sure that merging the protocols makes sense, as some protocols value=
 simplicity, and a combined protocol cannot have this feature.</div><div><b=
r></div><div>I don&#39;t think there is much interest in a merged colored c=
oin protocol now.</div><div>Colu is moving away from colored coins, as far =
as I can tell.</div><div>CoinSpark is now doing MultiChain closed-source pr=
ivate blockchain.</div><div>CoinPrism also seems to be largely disintereste=
d in colored coins.</div><div><br></div><div>We (ChromaWay) won&#39;t mind =
replacing EPOBC with something better, our software could always support mu=
ltiple different kernels so adding a new protocol isn&#39;t a big deal for =
us.</div><div><br></div><div>So if somebody is interested in a new protocol=
 please ping me.</div><div><br></div><div>One of ideas I have is to decoupl=
e input-output mapping/multiplexing from coloring.</div><div>So one layer w=
ill describe a mapping, e.g. &quot;Inputs 0 and 1 should go into outputs 0,=
 1 and 2&quot;.</div><div>In this case it will be possible to create more a=
dvanced protocols (e.g. with support for &#39;smart contracts&#39; and what=
not) while also keeping them compatible with old ones to some extent, e.g. =
a wallet can safely engage in p2ptrade or CoinJoin transactions without und=
erstanding all protocols used in a transaction.</div><div>=C2=A0<br></div><=
blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-l=
eft-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);pa=
dding-left:1ex"><div dir=3D"ltr"><div><div><div><div> - in collaboration wi=
th feedback from core developers that understand the direction the protocol=
 will be taking and the issues to avoid.=C2=A0=C2=A0 </div></div></div></di=
v></div></blockquote><div><br></div><div>Core developers generally dislike =
things like colored coins, so I doubt they are going to help.</div><div><br=
></div><div>Blockstream is developing a sidechain with user-defined assets,=
 so I guess they see it as the preferred way of doing things:</div><div><a =
href=3D"https://elementsproject.org/elements/asset-issuance/">https://eleme=
ntsproject.org/elements/asset-issuance/</a><br></div><div>=C2=A0<br></div><=
blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-l=
eft-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);pa=
dding-left:1ex"><div dir=3D"ltr"><div>As it stands, investors have to insta=
ll multiple wallets to deal with these varying implementations.</div></div>=
</blockquote><div><br></div><div>Actually this can be solved without making=
 a new &quot;merged protocol&quot;: one can just implement a wallet which s=
upports multiple protocols.</div><div><br></div><div><br></div></div></div>=
</div>

--001a1145b8e61dc0cc05391a0282--