From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1U3dxi-0006VS-2O for bitcoin-development@lists.sourceforge.net; Fri, 08 Feb 2013 02:45:14 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of praus.net designates 209.85.215.46 as permitted sender) client-ip=209.85.215.46; envelope-from=petr@praus.net; helo=mail-la0-f46.google.com; Received: from mail-la0-f46.google.com ([209.85.215.46]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1U3dxf-0006Od-W0 for bitcoin-development@lists.sourceforge.net; Fri, 08 Feb 2013 02:45:14 +0000 Received: by mail-la0-f46.google.com with SMTP id fq12so3256905lab.5 for ; Thu, 07 Feb 2013 18:45:04 -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:content-type:x-gm-message-state; bh=CHXnsJOFX9kg8lJvLC7912aOlmfSLh9/3TTyZOrhEF4=; b=TX0t9gzAiWLYx1MVpm5LJAVQPc1/UuRAAI7c941QSho/MPcutiUAtV/1w+C9zaCsd3 lXW9bHsBUvEi0DNIk80xA4PD1qnKlOD0ATMQEjlFOnMVZi0ygbLZiK/vIAhjsJtwxxv0 R6UmifkiOEqQQexcw2+qL9fyGO0yx3OtThf7qqtg0TfSgL6RkMy0cEaHEWfCoAnLmcye Il3V8KYX1/z53sV6PJMws8odj2bPi9/dj99Ok0eo3EirdydVzzAT1Zrmt+klK55nHbIE Ck9pebfmnr1Mod+4QHLAmsEv+XmueBvwe+WMyDEezY7aW4J5bhHkduwg0YsaV4sva/iU K4sA== X-Received: by 10.112.27.33 with SMTP id q1mr1669886lbg.78.1360291504582; Thu, 07 Feb 2013 18:45:04 -0800 (PST) MIME-Version: 1.0 Received: by 10.112.43.1 with HTTP; Thu, 7 Feb 2013 18:44:44 -0800 (PST) X-Originating-IP: [24.155.29.161] In-Reply-To: References: From: Petr Praus Date: Thu, 7 Feb 2013 20:44:44 -0600 Message-ID: To: bitcoin-development@lists.sourceforge.net Content-Type: multipart/alternative; boundary=bcaec554da72ebef7004d52d8b88 X-Gm-Message-State: ALoCoQnzlG3Ex2k8i6KewhU9GsppXo2qnqjXahE8VqOmQmkUWnEWV1/26okwHpO3FvusiKvwLiMO 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: 1U3dxf-0006Od-W0 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: Fri, 08 Feb 2013 02:45:14 -0000 --bcaec554da72ebef7004d52d8b88 Content-Type: text/plain; charset=UTF-8 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 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 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. 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 thread indicates it should be fine to post alternative development questions on this. --bcaec554da72ebef7004d52d8b88 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi,

I intend to implement trading across chains in a P2P manner (as described b= y Mike Hearn in=C2=A0https://en.bitcoin.it/wiki/Co= ntracts#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 t= hink it wouldn't be accepted). Before I dive into it, I thought it migh= t be a good idea to ask here if the community has any useful ideas or comme= nts on this topic?

Thanks to Gary Rowe I = know about=C2=A0Open Transactions. They=C2=A0can do "multic= urrency trading" too,=C2=A0but it's objectives are quite ambitious= and I'm looking at making relatively small changes in the mainline Bit= coin client rather than diving into something entirely new.

A little background on= why am I doing this, can be found=C2=A0here. In s= hort it's part of research towards my Master's thesis (more precise= ly, 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=C2=A0this=C2=A0thread ind= icates it should be fine to post alternative development questions on this.= =C2=A0
--bcaec554da72ebef7004d52d8b88--