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
|
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 <jtimonmv@gmail.com>) id 1U4rAQ-0002oG-7O
for bitcoin-development@lists.sourceforge.net;
Mon, 11 Feb 2013 11:03:22 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.128.51 as permitted sender)
client-ip=209.85.128.51; envelope-from=jtimonmv@gmail.com;
helo=mail-qe0-f51.google.com;
Received: from mail-qe0-f51.google.com ([209.85.128.51])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1U4rAA-0007AH-On
for bitcoin-development@lists.sourceforge.net;
Mon, 11 Feb 2013 11:03:22 +0000
Received: by mail-qe0-f51.google.com with SMTP id 6so2486325qea.38
for <bitcoin-development@lists.sourceforge.net>;
Mon, 11 Feb 2013 03:03:01 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.229.106.88 with SMTP id w24mr1118619qco.99.1360580581170;
Mon, 11 Feb 2013 03:03:01 -0800 (PST)
Received: by 10.49.27.102 with HTTP; Mon, 11 Feb 2013 03:03:01 -0800 (PST)
In-Reply-To: <CACezXZ85Bzw1jAFtnGXdp49dTYSoRL5cEjFtVPMxc1KTd0Vb+w@mail.gmail.com>
References: <CACezXZ_1TjtPtm_PXF+f63NvtR92+UtsXDizS05wXWP+YOrp_g@mail.gmail.com>
<CACezXZ85Bzw1jAFtnGXdp49dTYSoRL5cEjFtVPMxc1KTd0Vb+w@mail.gmail.com>
Date: Mon, 11 Feb 2013 12:03:01 +0100
Message-ID: <CABOyFfprYJ3B+6QxKUcaj1cbQT7LrsPBYhqRhXH5iKAjtF0okQ@mail.gmail.com>
From: =?ISO-8859-1?B?CUpvcmdlIFRpbfNu?= <jtimonmv@gmail.com>
To: Petr Praus <petr@praus.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -1.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
(jtimonmv[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
-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
0.0 TIME_LIMIT_EXCEEDED Exceeded time limit / deadline
X-Headers-End: 1U4rAA-0007AH-On
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: Mon, 11 Feb 2013 11:03:22 -0000
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_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 into
> it, I thought it might be a good idea to ask here if the community has an=
y
> 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 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 questions on
> this.
>
--=20
Jorge Tim=F3n
http://freico.in/
http://archive.ripple-project.org/
|
