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
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <flavien.charlon@pixodegames.com>) id 1WXA6n-0007aW-Q0
for bitcoin-development@lists.sourceforge.net;
Mon, 07 Apr 2014 14:01:09 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of
pixodegames.com designates 209.85.215.46 as permitted sender)
client-ip=209.85.215.46;
envelope-from=flavien.charlon@pixodegames.com;
helo=mail-la0-f46.google.com;
Received: from mail-la0-f46.google.com ([209.85.215.46])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WXA6m-0000nh-QC
for bitcoin-development@lists.sourceforge.net;
Mon, 07 Apr 2014 14:01:09 +0000
Received: by mail-la0-f46.google.com with SMTP id hr17so4781978lab.19
for <bitcoin-development@lists.sourceforge.net>;
Mon, 07 Apr 2014 07:01:02 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:from:date
:message-id:subject:to:cc:content-type;
bh=DHju6SiS/0tKdASIFmqlPMNqk59xAXrcn2s+tF4YC30=;
b=Pc/ew/h+JiCVOrku6JIhZpVFIeQ3Rlf/Kjlx8ucLK5AACQnOqrrHjC643w0JlB6gUZ
h+jgylGHJbp4pUTWySpxfVU65PSjYj/hwKKCsMqHqP0MSPn+uBmk1oHZJQAQBwrr47O6
YN5um6hFQwnJ6eNIAk4j+3mbygsxkittcbUYM+Sgp5lP4xvMDysD4RctSCj/SNXzVWxv
Sgxy74Z2tKWjRWS+5UcM/GrbT0aSu5GPIoevnmgxw3a+rzOwdZ3kwRLzk0er4+WJATW5
rqv81xyerwMaTjlRMlU3p0VoKfIULr/sB6JGghsHV0UPo2y9aGDajuEkbf8so8z1fpXN
NziQ==
X-Gm-Message-State: ALoCoQmOUUR4GYPTcyadaiUNnOIrleZywmIr79lT7qIE8PD4HFWTNcCqgPlci6G+9Z29vgJPWf68
X-Received: by 10.152.6.2 with SMTP id w2mr6046965law.28.1396879262127;
Mon, 07 Apr 2014 07:01:02 -0700 (PDT)
Received: from mail-la0-f41.google.com (mail-la0-f41.google.com
[209.85.215.41]) by mx.google.com with ESMTPSA id
v20sm11994093lbi.24.2014.04.07.07.01.01
for <bitcoin-development@lists.sourceforge.net>
(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
Mon, 07 Apr 2014 07:01:01 -0700 (PDT)
Received: by mail-la0-f41.google.com with SMTP id gl10so4914984lab.0
for <bitcoin-development@lists.sourceforge.net>;
Mon, 07 Apr 2014 07:01:01 -0700 (PDT)
X-Received: by 10.152.42.164 with SMTP id p4mr21299781lal.5.1396879261118;
Mon, 07 Apr 2014 07:01:01 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.114.185.230 with HTTP; Mon, 7 Apr 2014 07:00:20 -0700 (PDT)
X-Originating-IP: [79.97.126.227]
In-Reply-To: <CAC1+kJMpEetKdpKs-OaFGvnBwi6-Pj8ycJ77cJzHOTk_jUPw=g@mail.gmail.com>
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>
From: Flavien Charlon <flavien.charlon@coinprism.com>
Date: Mon, 7 Apr 2014 15:00:20 +0100
Message-ID: <CABbpET-S5ahuQVcBaJZGyvFMS1=RU2mJZUAmECBKhFOFu6B6EA@mail.gmail.com>
To: =?ISO-8859-1?Q?Jorge_Tim=F3n?= <jtimon@monetize.io>
Content-Type: multipart/alternative; boundary=001a11c33f982744a704f6744c80
X-Spam-Score: 2.1 (++)
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
1.2 RCVD_IN_BL_SPAMCOP_NET RBL: Received via a relay in bl.spamcop.net
[Blocked - see <http://www.spamcop.net/bl.shtml?209.85.215.41>]
-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
1.5 SF_NO_SPF_SPAM SF_NO_SPF_SPAM
X-Headers-End: 1WXA6m-0000nh-QC
Cc: bitcoin-development@lists.sourceforge.net
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 14:01:09 -0000
--001a11c33f982744a704f6744c80
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Jorge, they'd have to be. Otherwise, assuming the price of the share goes
low enough, you could buy a share of the company, melt the gold plate, and
sell it for a profit. If the gold is part of the capital of the company,
the cheapest a share can be is the price of the gold on which the stock
certificate is printed.
This is why I think the importance of padding with colored coins is
overblown.
On Mon, Apr 7, 2014 at 1:12 PM, Jorge Tim=F3n <jtimon@monetize.io> wrote:
> On 4/7/14, Flavien Charlon <flavien.charlon@coinprism.com> wrote:
> > Also those 54 BTC (actually 5.4 BTC if the dust is now 540 satoshis)
> become
> > part of the capital of the company, and can always be recovered by
> > uncoloring the shares. It's an investment, not an expense, so I think i=
t
> is
> > acceptable.
>
> This doesn't make much sense to me.
> If you print shares on gold plates instead of paper, is that gold
> "part of the capital of the company"? I don't think so.
>
--001a11c33f982744a704f6744c80
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div>Jorge, they'd have to be. Otherwise, assuming the=
price of the share goes low enough, you could buy a share of the company, =
melt the gold plate, and sell it for a profit. If the gold is part of the c=
apital of the company, the cheapest a share can be is the price of the gold=
on which the stock certificate is printed.</div>
<div><br></div><div>This is why I think the importance of padding with colo=
red coins is overblown.<br></div><div class=3D"gmail_extra"><br><br><div cl=
ass=3D"gmail_quote">On Mon, Apr 7, 2014 at 1:12 PM, Jorge Tim=F3n <span dir=
=3D"ltr"><<a href=3D"mailto:jtimon@monetize.io" target=3D"_blank">jtimon=
@monetize.io</a>></span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;padding=
-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-l=
eft-style:solid"><div>On 4/7/14, Flavien Charlon <<a href=3D"mailto:flav=
ien.charlon@coinprism.com">flavien.charlon@coinprism.com</a>> wrote:<br>
> Also those 54 BTC (actually 5.4 BTC if the dust is now 540 satoshis) b=
ecome<br>
> part of the capital of the company, and can always be recovered by<br>
> uncoloring the shares. It's an investment, not an expense, so I th=
ink it is<br>
> acceptable.<br>
<br>
</div>This doesn't make much sense to me.<br>
If you print shares on gold plates instead of paper, is that gold<br>
"part of the capital of the company"? I don't think so.<br>
</blockquote></div><br></div></div>
--001a11c33f982744a704f6744c80--
|
