From mboxrd@z Thu Jan 1 00:00:00 1970 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 ) 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 ; 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: References: From: Petr Praus Date: Thu, 14 Feb 2013 15:02:25 -0600 Message-ID: To: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 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 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 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 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. > >> > 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 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
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 acr= oss "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://rip= ple.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 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, I= OUs
>> of another currency...Colored coins can be atomically traded for >> bitcoin. If you implement the trade across chains contract they wo= uld
>> 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 net= work
>> are able to pay with IOUs transitively. It has a new p2p
>> implementation =C2=A0that is still on development. The new impleme= ntation
>> is very similar to bitcoin in certain senses but it has no mining.=
>> Bitcoin IOUs can be traded there.
>>
>> https://ripple.c= om/
>>
>> 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@p= raus.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 developme= nt, I
>> > don't
>> > have any plans for merging it back into main client (not beca= use I
>> > don't
>> > want to, but because I think it wouldn't be accepted). Be= fore I dive
>> > into
>> > it, I thought it might be a good idea to ask here if the comm= unity 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 chan= ges in the
>> > mainline Bitcoin client rather than diving into something ent= irely new.
>> >
>> > A little background on why am I doing this, can be found
>> > here<https://groups.google.com/d/topi= c/bitcoinj/lmVSF8yaJHk/discussion>.
>> > In short it's part of research towards my Master's th= esis (more
>> precisely,
>> > an excuse to hack on Bitcoin and sell it as research :)) whic= h 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 q= uestions
>> > on
>> > this.
>> >
>>
>>
>> --
>> Jorge Tim=C3=B3n
>>
>> http://freico.in/<= /a>
>> h= ttp://archive.ripple-project.org/
>>
>


--
Jorge Tim=C3=B3n

http://freico.in/
http://arc= hive.ripple-project.org/

--e89a8f22c381adbb2504d5b59472--