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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <alex.mizrahi@gmail.com>) id 1WYIiF-0006nC-95
for bitcoin-development@lists.sourceforge.net;
Thu, 10 Apr 2014 17:24:31 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.216.181 as permitted sender)
client-ip=209.85.216.181; envelope-from=alex.mizrahi@gmail.com;
helo=mail-qc0-f181.google.com;
Received: from mail-qc0-f181.google.com ([209.85.216.181])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WYIiE-0008Jd-Gc
for bitcoin-development@lists.sourceforge.net;
Thu, 10 Apr 2014 17:24:31 +0000
Received: by mail-qc0-f181.google.com with SMTP id x3so4754587qcv.12
for <bitcoin-development@lists.sourceforge.net>;
Thu, 10 Apr 2014 10:24:25 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.224.88.131 with SMTP id a3mr22271962qam.54.1397150664936;
Thu, 10 Apr 2014 10:24:24 -0700 (PDT)
Received: by 10.96.77.38 with HTTP; Thu, 10 Apr 2014 10:24:24 -0700 (PDT)
In-Reply-To: <5346CDD4.8050206@monetize.io>
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>
Date: Thu, 10 Apr 2014 20:24:24 +0300
Message-ID: <CAE28kUSWwamovgPA1AvAojoKuwaDvuWzbnYf6yJhQ89HRnOJGg@mail.gmail.com>
From: Alex Mizrahi <alex.mizrahi@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=001a11c2dac014d1ab04f6b37d67
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: 1WYIiE-0008Jd-Gc
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: Thu, 10 Apr 2014 17:24:31 -0000
--001a11c2dac014d1ab04f6b37d67
Content-Type: text/plain; charset=ISO-8859-1
> 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.
--001a11c2dac014d1ab04f6b37d67
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"><div=
>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord=
er-left:1px #ccc solid;padding-left:1ex"><div class=3D"">
</div>At this point, I don'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>Nope, it's still colored coins. The differenc=
e between colored coin model and Mastercoin model is that colored coins are=
linked to transaction outputs, while Mastercoin has a notion of address ba=
lances.</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=
'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>
--001a11c2dac014d1ab04f6b37d67--
|
