Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.216.47 as permitted sender)
	client-ip=209.85.216.47; envelope-from=alex.mizrahi@gmail.com;
	helo=mail-qa0-f47.google.com; 
MIME-Version: 1.0
In-Reply-To: <5341E1FF.7080204@monetize.io>
References: <CABbpET96CboPcQeV-nKXv-CeaPiwpTKVUB_ioGPB2s3_5Y7bnQ@mail.gmail.com>
	<5341E1FF.7080204@monetize.io>
Date: Mon, 7 Apr 2014 14:28:33 +0300
Message-ID: <CAE28kURZB=huuvRPwOnVxSUzcez-pypDMpOzA3jiO7m2Q0pwsQ@mail.gmail.com>
From: Alex Mizrahi <alex.mizrahi@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Content-Type: multipart/alternative; boundary=047d7b673fb6f1f41d04f6722a13
Subject: Re: [Bitcoin-development] Feedback request: colored coins protocol
Precedence: list

--047d7b673fb6f1f41d04f6722a13
Content-Type: text/plain; charset=ISO-8859-1

>
> Have you seen the padded order-based coloring scheme worked out here?
>
> https://github.com/bitcoinx/colored-coin-tools/wiki/colored_coins_intro


Just to clarify, a variant of padded order-based coloring called epobc is
already implemented in coloredcoinlib (which is used by
ngcccbase/ChromaWallet). It isn't document yet, however.
The idea is to use the otherwise unused nSequence field of first input to
specify padding and differentiate between genesis and transfer transactions.
Padding can be chosen for each transaction individually and can be set to
zero.

Python code is here (I recommend waiting for documentation, though):

https://github.com/bitcoinx/ngcccbase/blob/master/coloredcoinlib/colordef.py#L262

It is able to work with transactions with multiple colored and uncolored
outputs, particularly, p2ptrade transactions.

Examples of p2ptrade transactions on mainnet:
https://blockchain.info/tx/8c1926f2e3527153bf06e8ab2c8a417aad3d8e6cd993a4350efbb4050ab961fa
https://blockchain.info/tx/f85b6213939c9cbc14538dd24838061179cac2485f50be20a974b819a85e5ee9(It
looks quite a bit weird, I know.)

--047d7b673fb6f1f41d04f6722a13
Content-Type: text/html; charset=ISO-8859-1
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-color:rgb(204,204,204);border-left-style:solid;paddi=
ng-left:1ex">
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></blockquote><div><br></div><div>Just to clarify=
, a variant of padded order-based coloring called epobc is already implemen=
ted in coloredcoinlib (which is used by ngcccbase/ChromaWallet). It isn&#39=
;t document yet, however.</div>
<div>The idea is to use the otherwise unused nSequence field of first input=
 to specify padding and differentiate between genesis and transfer transact=
ions.</div><div>Padding can be chosen for each transaction individually and=
 can be set to zero.=A0</div>
<div><br></div><div>Python code is here (I recommend waiting for documentat=
ion, though): =A0</div><div><br></div><div><a href=3D"https://github.com/bi=
tcoinx/ngcccbase/blob/master/coloredcoinlib/colordef.py#L262">https://githu=
b.com/bitcoinx/ngcccbase/blob/master/coloredcoinlib/colordef.py#L262</a><br=
>
</div><div><br></div><div>It is able to work with transactions with multipl=
e colored and uncolored outputs, particularly, p2ptrade transactions.<br></=
div><div><br></div><div>Examples of p2ptrade transactions on mainnet:</div>
<div><a href=3D"https://blockchain.info/tx/8c1926f2e3527153bf06e8ab2c8a417a=
ad3d8e6cd993a4350efbb4050ab961fa">https://blockchain.info/tx/8c1926f2e35271=
53bf06e8ab2c8a417aad3d8e6cd993a4350efbb4050ab961fa</a><br></div><div><a hre=
f=3D"https://blockchain.info/tx/f85b6213939c9cbc14538dd24838061179cac2485f5=
0be20a974b819a85e5ee9">https://blockchain.info/tx/f85b6213939c9cbc14538dd24=
838061179cac2485f50be20a974b819a85e5ee9</a> (It looks quite a bit weird, I =
know.)</div>
</div></div></div>

--047d7b673fb6f1f41d04f6722a13--