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
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <petr@praus.net>) id 1U65xJ-0004IS-R3
for bitcoin-development@lists.sourceforge.net;
Thu, 14 Feb 2013 21:02:58 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of praus.net
designates 209.85.215.44 as permitted sender)
client-ip=209.85.215.44; envelope-from=petr@praus.net;
helo=mail-la0-f44.google.com;
Received: from mail-la0-f44.google.com ([209.85.215.44])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1U65xG-00017r-3j
for bitcoin-development@lists.sourceforge.net;
Thu, 14 Feb 2013 21:02:57 +0000
Received: by mail-la0-f44.google.com with SMTP id eb20so2763172lab.3
for <bitcoin-development@lists.sourceforge.net>;
Thu, 14 Feb 2013 13:02:47 -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=dPkunbouYM7JqsgL4t8x2pFZ01PqkUaqVMD4Klvf3G4=;
b=RHQirdBDPXmXojd2ff94G4fWjT+/jrKMcBXXLPFbDzcDUpHmoOokBC+LOwA1oGjTWD
p8zlqFe86S6mKn6L7t7B9rfSZZNCqZCTDI4IX5p/NGmMObkSO6j/8TjV2idmtGofZPgx
lR+P2BOcQsSVcjMzmiFUCnjgLeYYZxWRv5WBkKKgviPjplSCMY+Q8INZIvVN0PUnfhgI
tmLYq5WHze6abTwYd4P9vXHtXr1eJO4Ss1JdOMOc4vsG6VsIGiRmVOONJCWc+9eQUNYg
QJfwmJ50volW3ffrsbpeWK+n8RDQqdvyhIOV+JcbWBXjCTCq3pnr7gyMpvOKmDJM8T0B
Eung==
X-Received: by 10.152.147.36 with SMTP id th4mr94654lab.19.1360875767052; Thu,
14 Feb 2013 13:02:47 -0800 (PST)
MIME-Version: 1.0
Received: by 10.112.45.5 with HTTP; Thu, 14 Feb 2013 13:02:25 -0800 (PST)
X-Originating-IP: [129.62.151.28]
In-Reply-To: <CABOyFfoRq3Kqx8baw4zGkYEFRLabMdVWDRdvw4sy5RrH=TjLKQ@mail.gmail.com>
References: <CACezXZ_1TjtPtm_PXF+f63NvtR92+UtsXDizS05wXWP+YOrp_g@mail.gmail.com>
<CACezXZ85Bzw1jAFtnGXdp49dTYSoRL5cEjFtVPMxc1KTd0Vb+w@mail.gmail.com>
<CABOyFfprYJ3B+6QxKUcaj1cbQT7LrsPBYhqRhXH5iKAjtF0okQ@mail.gmail.com>
<CACezXZ_qqZkg6zN6OFVZYjV_hfkhKgFH2foAqMqwjCAAQCN9QQ@mail.gmail.com>
<CABOyFfoRq3Kqx8baw4zGkYEFRLabMdVWDRdvw4sy5RrH=TjLKQ@mail.gmail.com>
From: Petr Praus <petr@praus.net>
Date: Thu, 14 Feb 2013 15:02:25 -0600
Message-ID: <CACezXZ_DbSsBwChB-uoSu+VcWnBJOuvzV3eim5aKTYCZos+_RQ@mail.gmail.com>
To: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= <jtimonmv@gmail.com>
Content-Type: multipart/alternative; boundary=e89a8f22c381adbb2504d5b59472
X-Gm-Message-State: ALoCoQm3KmFNnSX1YRLLzik52QLy7FFOgaRFRbjt8rvsTVPdQIEssziZPVvQd6O8lWZCRB08/VeG
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: 1U65xG-00017r-3j
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: Thu, 14 Feb 2013 21:02:58 -0000
--e89a8f22c381adbb2504d5b59472
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Ah, I missed this, thanks.
On 13 February 2013 15:49, Jorge Tim=C3=B3n <jtimonmv@gmail.com> wrote:
> Well, if it's even possible to trade across "chains" with Ripple (and
> I don't know of any reason shouldn't be), you will have to wait to the
> release of the full node (validator) code, for now only a javascript
> web client is open sourced. But it seems they at least have plans for
> contracts judging from the wiki:
>
> https://ripple.com/wiki/Contracts
>
>
> On 2/13/13, Petr Praus <petr@praus.net> wrote:
> > Jorge, thanks for bitcoinx tip, I didn't know about it and it's certain=
ly
> > 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
> >> > described
> >> > by Mike Hearn in
> >> > https://en.bitcoin.it/wiki/Contracts#Example_5:_Trading_across_chain=
s
> ).
> >> > 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
> >> > into
> >> > it, I thought it might be a good idea to ask here if the community h=
as
> >> 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 qui=
te
> >> > 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 shoul=
d
> >> > be
> >> > 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 question=
s
> >> > on
> >> > this.
> >> >
> >>
> >>
> >> --
> >> Jorge Tim=C3=B3n
> >>
> >> http://freico.in/
> >> http://archive.ripple-project.org/
> >>
> >
>
>
> --
> Jorge Tim=C3=B3n
>
> http://freico.in/
> http://archive.ripple-project.org/
>
--e89a8f22c381adbb2504d5b59472
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Ah, I missed this, thanks.</div><div class=3D"gmail_extra"=
><br><br><div class=3D"gmail_quote">On 13 February 2013 15:49, Jorge Tim=C3=
=B3n <span dir=3D"ltr"><<a href=3D"mailto:jtimonmv@gmail.com" target=3D"=
_blank">jtimonmv@gmail.com</a>></span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Well, if it's even possible to trade acr=
oss "chains" with Ripple (and<br>
I don't know of any reason shouldn't be), you will have to wait to =
the<br>
release of the full node (validator) code, for now only a javascript<br>
web client is open sourced. But it seems they at least have plans for<br>
contracts judging from the wiki:<br>
<br>
<a href=3D"https://ripple.com/wiki/Contracts" target=3D"_blank">https://rip=
ple.com/wiki/Contracts</a><br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
On 2/13/13, Petr Praus <<a href=3D"mailto:petr@praus.net">petr@praus.net=
</a>> wrote:<br>
> Jorge, thanks for bitcoinx tip, I didn't know about it and it'=
s certainly<br>
> related. I'll have a closer look<br>
> Regarding Ripple, I tried it but as far as I can tell, it doesn't =
have any<br>
> contract enforcement (by technical means) built in.<br>
><br>
><br>
> On 11 February 2013 05:03, Jorge Tim=C3=B3n <<a href=3D"mailto:jtim=
onmv@gmail.com">jtimonmv@gmail.com</a>> wrote:<br>
><br>
>> Hi, you may be interested in a couple of related projects.<br>
>><br>
>> Colored coins uses satoshis to represent smart property, shares, I=
OUs<br>
>> of another currency...Colored coins can be atomically traded for<b=
r>
>> bitcoin. If you implement the trade across chains contract they wo=
uld<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 net=
work<br>
>> are able to pay with IOUs transitively. It has a new p2p<br>
>> implementation =C2=A0that is still on development. The new impleme=
ntation<br>
>> 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.c=
om/</a><br>
>><br>
>> Good luck with the implementation, this is a good feature to have,=
<br>
>> even if it's not on the main client.<br>
>><br>
>><br>
>> On 2/8/13, Petr Praus <<a href=3D"mailto:petr@praus.net">petr@p=
raus.net</a>> wrote:<br>
>> > Hi,<br>
>> ><br>
>> > I intend to implement trading across chains in a P2P manner (=
as<br>
>> > described<br>
>> > by Mike Hearn in<br>
>> > <a href=3D"https://en.bitcoin.it/wiki/Contracts#Example_5:_Tr=
ading_across_chains" target=3D"_blank">https://en.bitcoin.it/wiki/Contracts=
#Example_5:_Trading_across_chains</a>).<br>
>> > Note, this is indended more as an alternative chain developme=
nt, I<br>
>> > don't<br>
>> > have any plans for merging it back into main client (not beca=
use I<br>
>> > don't<br>
>> > want to, but because I think it wouldn't be accepted). Be=
fore I dive<br>
>> > into<br>
>> > it, I thought it might be a good idea to ask here if the comm=
unity has<br>
>> any<br>
>> > useful ideas or comments on this topic?<br>
>> ><br>
>> > Thanks to Gary Rowe I know about Open<br>
>> > Transactions<<a href=3D"https://github.com/FellowTraveler/=
Open-Transactions" target=3D"_blank">https://github.com/FellowTraveler/Open=
-Transactions</a>>.<br>
>> > They can do "multicurrency trading" too, but it'=
;s objectives are quite<br>
>> > ambitious and I'm looking at making relatively small chan=
ges in the<br>
>> > mainline Bitcoin client rather than diving into something ent=
irely new.<br>
>> ><br>
>> > A little background on why am I doing this, can be found<br>
>> > here<<a href=3D"https://groups.google.com/d/topic/bitcoinj=
/lmVSF8yaJHk/discussion" target=3D"_blank">https://groups.google.com/d/topi=
c/bitcoinj/lmVSF8yaJHk/discussion</a>>.<br>
>> > In short it's part of research towards my Master's th=
esis (more<br>
>> precisely,<br>
>> > an excuse to hack on Bitcoin and sell it as research :)) whic=
h should<br>
>> > be<br>
>> > about multicurrency (alternative chains) in Bitcoin.<br>
>> ><br>
>> > Thanks,<br>
>> > Petr<br>
>> ><br>
>> > PS: I hope I'm not too off topic here, but<br>
>> > this<<a href=3D"https://bitcointalk.org/index.php?topic=3D=
15527.0" target=3D"_blank">https://bitcointalk.org/index.php?topic=3D15527.=
0</a>> thread<br>
>> > indicates it should be fine to post alternative development q=
uestions<br>
>> > on<br>
>> > this.<br>
>> ><br>
>><br>
>><br>
>> --<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">h=
ttp://archive.ripple-project.org/</a><br>
>><br>
><br>
<br>
<br>
--<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>
</div></div></blockquote></div><br></div>
--e89a8f22c381adbb2504d5b59472--
|
