From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WX7jE-0003JM-GN for bitcoin-development@lists.sourceforge.net; Mon, 07 Apr 2014 11:28:40 +0000 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; Received: from mail-qa0-f47.google.com ([209.85.216.47]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WX7jD-00073u-IL for bitcoin-development@lists.sourceforge.net; Mon, 07 Apr 2014 11:28:40 +0000 Received: by mail-qa0-f47.google.com with SMTP id m5so712442qaj.20 for ; Mon, 07 Apr 2014 04:28:34 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.224.172.131 with SMTP id l3mr14277161qaz.57.1396870114045; Mon, 07 Apr 2014 04:28:34 -0700 (PDT) Received: by 10.96.77.38 with HTTP; Mon, 7 Apr 2014 04:28:33 -0700 (PDT) In-Reply-To: <5341E1FF.7080204@monetize.io> References: <5341E1FF.7080204@monetize.io> Date: Mon, 7 Apr 2014 14:28:33 +0300 Message-ID: From: Alex Mizrahi To: bitcoin-development@lists.sourceforge.net Content-Type: multipart/alternative; boundary=047d7b673fb6f1f41d04f6722a13 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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (alex.mizrahi[at]gmail.com) -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: 1WX7jD-00073u-IL 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Apr 2014 11:28:40 -0000 --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
Have you seen the padded order-based coloring scheme worked out here?

https://github.com/bitcoinx/colored-coin-tools/w= iki/colored_coins_intro

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'= ;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 transact= ions.
Padding can be chosen for each transaction individually and= can be set to zero.=A0

Python code is here (I recommend waiting for documentat= ion, though): =A0


It is able to work with transactions with multipl= e colored and uncolored outputs, particularly, p2ptrade transactions.

Examples of p2ptrade transactions on mainnet:
--047d7b673fb6f1f41d04f6722a13--