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
|
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 <alex.mizrahi@gmail.com>) 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 <bitcoin-development@lists.sourceforge.net>;
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: <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
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: <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: 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
<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'=
;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--
|
