summaryrefslogtreecommitdiff
path: root/94/a5ceaf994062299a397dd4c02b4708c1bc455d
blob: d1f9b1ee4e4ee893e58547f377dbd8a1a864b209 (plain)
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
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
	helo=mx.sourceforge.net)
	by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <petr@praus.net>) id 1U5k6L-00089W-AK
	for bitcoin-development@lists.sourceforge.net;
	Wed, 13 Feb 2013 21:42:49 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of praus.net
	designates 209.85.217.178 as permitted sender)
	client-ip=209.85.217.178; envelope-from=petr@praus.net;
	helo=mail-lb0-f178.google.com; 
Received: from mail-lb0-f178.google.com ([209.85.217.178])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1U5k6H-0000RG-IN
	for bitcoin-development@lists.sourceforge.net;
	Wed, 13 Feb 2013 21:42:49 +0000
Received: by mail-lb0-f178.google.com with SMTP id n1so1312377lba.9
	for <bitcoin-development@lists.sourceforge.net>;
	Wed, 13 Feb 2013 13:42:38 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=x-received:mime-version:x-originating-ip:in-reply-to:references
	:from:date:message-id:subject:to:cc:content-type:x-gm-message-state;
	bh=/yFXbNZ3AFikBB7UpfBKDyjjyQLIxm8D1D4Af3AGc7A=;
	b=Vd4GqNQVOQwVHosv3eHpAEjG7qeea00LcQLyaYwN8gFFQSjowsEiJUglH3qwPBV9hA
	FEDT5fuwdSVn+6k/qww3tDNI2iau8vkFTgx3QbNLDb18kg1too/i2ApNdL9PtzMygiC1
	5CipztP62+NjheEjYHzgd2yqMbJ90tnHuz4RhG1sbqXZAATS0ZgUNDColWFVc9WNEH8i
	xEI46+G4u7BgCw68tE4INkTvR2X0ohxDWa+PeJW7gkKdG6kfPpgqXBWry35DAGu5BJZk
	5RpiYgbalbv0MFEhIT1ks2eXzKTRgDjDhKyuWFDhjxvWCBVFH3zb/o/YCwTRxjfRqyO/
	BefA==
X-Received: by 10.152.48.113 with SMTP id k17mr1956693lan.29.1360791758350;
	Wed, 13 Feb 2013 13:42:38 -0800 (PST)
MIME-Version: 1.0
Received: by 10.112.45.5 with HTTP; Wed, 13 Feb 2013 13:42:17 -0800 (PST)
X-Originating-IP: [24.155.29.161]
In-Reply-To: <CABOyFfprYJ3B+6QxKUcaj1cbQT7LrsPBYhqRhXH5iKAjtF0okQ@mail.gmail.com>
References: <CACezXZ_1TjtPtm_PXF+f63NvtR92+UtsXDizS05wXWP+YOrp_g@mail.gmail.com>
	<CACezXZ85Bzw1jAFtnGXdp49dTYSoRL5cEjFtVPMxc1KTd0Vb+w@mail.gmail.com>
	<CABOyFfprYJ3B+6QxKUcaj1cbQT7LrsPBYhqRhXH5iKAjtF0okQ@mail.gmail.com>
From: Petr Praus <petr@praus.net>
Date: Wed, 13 Feb 2013 15:42:17 -0600
Message-ID: <CACezXZ_qqZkg6zN6OFVZYjV_hfkhKgFH2foAqMqwjCAAQCN9QQ@mail.gmail.com>
To: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= <jtimonmv@gmail.com>
Content-Type: multipart/alternative; boundary=bcaec55244145eaa5304d5a20512
X-Gm-Message-State: ALoCoQn39/E+MX2Ovpv86m9X1NCudZNBiNMuxX+9sTO7yAL5VbSFxd+IsIzkVxrS7XE8VeuLAzuo
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 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: 1U5k6H-0000RG-IN
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Implementing trading across chains
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: Wed, 13 Feb 2013 21:42:49 -0000

--bcaec55244145eaa5304d5a20512
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Jorge, thanks for bitcoinx tip, I didn't know about it and it's certainly
related. I'll have a closer look
Regarding Ripple, I tried it but as far as I can tell, it doesn't have any
contract enforcement (by technical means) built in.


On 11 February 2013 05:03, Jorge Tim=C3=B3n <jtimonmv@gmail.com> wrote:

> Hi, you may be interested in a couple of related projects.
>
> Colored coins uses satoshis to represent smart property, shares, IOUs
> of another currency...Colored coins can be atomically traded for
> bitcoin. If you implement the trade across chains contract they would
> also be tradeable for another chain currencies like namecoin or
> freicoin.
>
> http://www.bitcoinx.org/
>
> Ripple is a concept by which people that trust each other on a network
> are able to pay with IOUs transitively. It has a new p2p
> implementation  that is still on development. The new implementation
> is very similar to bitcoin in certain senses but it has no mining.
> Bitcoin IOUs can be traded there.
>
> https://ripple.com/
>
> Good luck with the implementation, this is a good feature to have,
> even if it's not on the main client.
>
>
> On 2/8/13, Petr Praus <petr@praus.net> wrote:
> > Hi,
> >
> > I intend to implement trading across chains in a P2P manner (as describ=
ed
> > by Mike Hearn in
> > https://en.bitcoin.it/wiki/Contracts#Example_5:_Trading_across_chains).
> > Note, this is indended more as an alternative chain development, I don'=
t
> > have any plans for merging it back into main client (not because I don'=
t
> > want to, but because I think it wouldn't be accepted). Before I dive in=
to
> > it, I thought it might be a good idea to ask here if the community has
> any
> > useful ideas or comments on this topic?
> >
> > Thanks to Gary Rowe I know about Open
> > Transactions<https://github.com/FellowTraveler/Open-Transactions>.
> > They can do "multicurrency trading" too, but it's objectives are quite
> > ambitious and I'm looking at making relatively small changes in the
> > mainline Bitcoin client rather than diving into something entirely new.
> >
> > A little background on why am I doing this, can be found
> > here<https://groups.google.com/d/topic/bitcoinj/lmVSF8yaJHk/discussion>=
.
> > In short it's part of research towards my Master's thesis (more
> precisely,
> > an excuse to hack on Bitcoin and sell it as research :)) which should b=
e
> > about multicurrency (alternative chains) in Bitcoin.
> >
> > Thanks,
> > Petr
> >
> > PS: I hope I'm not too off topic here, but
> > this<https://bitcointalk.org/index.php?topic=3D15527.0> thread
> > indicates it should be fine to post alternative development questions o=
n
> > this.
> >
>
>
> --
> Jorge Tim=C3=B3n
>
> http://freico.in/
> http://archive.ripple-project.org/
>

--bcaec55244145eaa5304d5a20512
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Jorge, thanks for bitcoinx tip, I didn&#39;t know about it=
 and it&#39;s certainly related. I&#39;ll have a closer look<div style>Rega=
rding Ripple, I tried it but as far as I can tell, it doesn&#39;t have any =
contract enforcement (by technical means) built in.</div>

</div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On 11 F=
ebruary 2013 05:03, Jorge Tim=C3=B3n <span dir=3D"ltr">&lt;<a href=3D"mailt=
o:jtimonmv@gmail.com" target=3D"_blank">jtimonmv@gmail.com</a>&gt;</span> w=
rote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;borde=
r-left:1px #ccc solid;padding-left:1ex">

Hi, you may be interested in a couple of related projects.<br>
<br>
Colored coins uses satoshis to represent smart property, shares, IOUs<br>
of another currency...Colored coins can be atomically traded for<br>
bitcoin. If you implement the trade across chains contract they would<br>
also be tradeable for another chain currencies like namecoin or<br>
freicoin.<br>
<br>
<a href=3D"http://www.bitcoinx.org/" target=3D"_blank">http://www.bitcoinx.=
org/</a><br>
<br>
Ripple is a concept by which people that trust each other on a network<br>
are able to pay with IOUs transitively. It has a new p2p<br>
implementation =C2=A0that is still on development. The new implementation<b=
r>
is very similar to bitcoin in certain senses but it has no mining.<br>
Bitcoin IOUs can be traded there.<br>
<br>
<a href=3D"https://ripple.com/" target=3D"_blank">https://ripple.com/</a><b=
r>
<br>
Good luck with the implementation, this is a good feature to have,<br>
even if it&#39;s not on the main client.<br>
<div class=3D"im"><br>
<br>
On 2/8/13, Petr Praus &lt;<a href=3D"mailto:petr@praus.net">petr@praus.net<=
/a>&gt; wrote:<br>
&gt; Hi,<br>
&gt;<br>
&gt; I intend to implement trading across chains in a P2P manner (as descri=
bed<br>
&gt; by Mike Hearn in<br>
&gt; <a href=3D"https://en.bitcoin.it/wiki/Contracts#Example_5:_Trading_acr=
oss_chains" target=3D"_blank">https://en.bitcoin.it/wiki/Contracts#Example_=
5:_Trading_across_chains</a>).<br>
&gt; Note, this is indended more as an alternative chain development, I don=
&#39;t<br>
&gt; have any plans for merging it back into main client (not because I don=
&#39;t<br>
&gt; want to, but because I think it wouldn&#39;t be accepted). Before I di=
ve into<br>
&gt; it, I thought it might be a good idea to ask here if the community has=
 any<br>
&gt; useful ideas or comments on this topic?<br>
&gt;<br>
&gt; Thanks to Gary Rowe I know about Open<br>
</div>&gt; Transactions&lt;<a href=3D"https://github.com/FellowTraveler/Ope=
n-Transactions" target=3D"_blank">https://github.com/FellowTraveler/Open-Tr=
ansactions</a>&gt;.<br>
<div class=3D"im">&gt; They can do &quot;multicurrency trading&quot; too, b=
ut it&#39;s objectives are quite<br>
&gt; ambitious and I&#39;m looking at making relatively small changes in th=
e<br>
&gt; mainline Bitcoin client rather than diving into something entirely new=
.<br>
&gt;<br>
&gt; A little background on why am I doing this, can be found<br>
</div>&gt; here&lt;<a href=3D"https://groups.google.com/d/topic/bitcoinj/lm=
VSF8yaJHk/discussion" target=3D"_blank">https://groups.google.com/d/topic/b=
itcoinj/lmVSF8yaJHk/discussion</a>&gt;.<br>
<div class=3D"im">&gt; In short it&#39;s part of research towards my Master=
&#39;s thesis (more precisely,<br>
&gt; an excuse to hack on Bitcoin and sell it as research :)) which should =
be<br>
&gt; about multicurrency (alternative chains) in Bitcoin.<br>
&gt;<br>
&gt; Thanks,<br>
&gt; Petr<br>
&gt;<br>
&gt; PS: I hope I&#39;m not too off topic here, but<br>
</div>&gt; this&lt;<a href=3D"https://bitcointalk.org/index.php?topic=3D155=
27.0" target=3D"_blank">https://bitcointalk.org/index.php?topic=3D15527.0</=
a>&gt; thread<br>
<div class=3D"HOEnZb"><div class=3D"h5">&gt; indicates it should be fine to=
 post alternative development questions on<br>
&gt; this.<br>
&gt;<br>
<br>
<br>
</div></div><span class=3D"HOEnZb"><font color=3D"#888888">--<br>
Jorge Tim=C3=B3n<br>
<br>
<a href=3D"http://freico.in/" target=3D"_blank">http://freico.in/</a><br>
<a href=3D"http://archive.ripple-project.org/" target=3D"_blank">http://arc=
hive.ripple-project.org/</a><br>
</font></span></blockquote></div><br></div>

--bcaec55244145eaa5304d5a20512--