Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1SIdYB-0007my-8n for bitcoin-development@lists.sourceforge.net; Fri, 13 Apr 2012 10:16:19 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.213.175 as permitted sender) client-ip=209.85.213.175; envelope-from=g.rowe.froot@gmail.com; helo=mail-yx0-f175.google.com; Received: from mail-yx0-f175.google.com ([209.85.213.175]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-MD5:128) (Exim 4.76) id 1SIdY5-00013d-Bm for bitcoin-development@lists.sourceforge.net; Fri, 13 Apr 2012 10:16:19 +0000 Received: by yenm3 with SMTP id m3so1828174yen.34 for ; Fri, 13 Apr 2012 03:16:08 -0700 (PDT) MIME-Version: 1.0 Received: by 10.236.76.226 with SMTP id b62mr1082043yhe.13.1334312167979; Fri, 13 Apr 2012 03:16:07 -0700 (PDT) Sender: g.rowe.froot@gmail.com Received: by 10.236.190.65 with HTTP; Fri, 13 Apr 2012 03:16:07 -0700 (PDT) In-Reply-To: References: Date: Fri, 13 Apr 2012 11:16:07 +0100 X-Google-Sender-Auth: hRRXP_FpyMj9U4N6O-Xt9awQlG8 Message-ID: From: Gary Rowe To: Walter Stanish Content-Type: multipart/alternative; boundary=20cf3005132ecab8f404bd8cc292 X-Spam-Score: -0.2 (/) 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 (g.rowe.froot[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 0.3 URIBL_RHS_DOB Contains an URI of a new domain (Day Old Bread) [URIs: ifex-project.org] 1.0 HTML_MESSAGE BODY: HTML included in message 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: 1SIdY5-00013d-Bm Cc: bitcoin-development@lists.sourceforge.net Subject: Re: [Bitcoin-development] Announcing the IFEX Project 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, 13 Apr 2012 10:16:19 -0000 --20cf3005132ecab8f404bd8cc292 Content-Type: text/plain; charset=UTF-8 Hi Walter, This could be of interest to the XChange project. See GitHub: https://github.com/timmolter/XChange The aim of this project is to provide a unifed API for applications to access financial exchanges. At present it supports Bitcoin exchanges (MtGox and Intersango are the primary focus with others to follow). It is in the very early stages of development, but is likely to be integrated into the MultiBit Bitcoin client (see http://multibit.org) in the near future (early prototypes are available directly from sources). One problem that the XChange development team faces is that each exchange rolls its own data model and uses its own protocol (web socket, socket IO, direct socket and so on). To provide a reference implementation of how an exchange should publish its data would be beneficial. Kind regards, Gary On 13 April 2012 10:34, Walter Stanish wrote: > The Internet Financial EXchange (IFEX) Project is an open body for the > discussion and development of financial standards for the internet > community. The project seeks to focus on enhancing interoperability > between financial settlement systems of all types, including > conventional financial systems, emerging digital currencies, > alternative financial communities, and financial service providers. > > Interested parties are invited to review the proposals on the website > at http://www.ifex-project.org/ and join the mailing list at > http://group.ifex-project.org/ > > Two items on the site that may be of particular interest: > > (1) The latest version of the IIBAN Proposal (v1) for financial > endpoint identification at > http://www.ifex-project.org/our-proposals/iiban. This latest version > includes initial IANA registry contents and a reference mechanism for > financial endpoint transcription error correction. (Relevance: In > contrast to settlement system-specific financial endpoint identifiers, > IIBAN provides a democratically allocated, 13 character identifier > that is already familiar in format to users in Europe and other > countries and is theoretically compatible with conventional banking > infrastructure in those regions. In addition, IIBAN is not tied to > any specific financial commodity or settlement system, and provides > strong protection against identifier transcription errors.) > > (2) The IFEX Protocol is a *work in progress* that hopes to bridge the > gap between conventional financial systems, emerging digital > currencies, alternative financial communities, and financial service > providers by providing a standard protocol for transaction and > settlement path negotiation with arbitrary financial instruments, > currencies or assets. (Relevance: better connectivity, lower > settlement fees, real time redundant financial routing, arbitrary > instrument/currency/asset handling) > > How IFEX's proposed infrastructure differs from existing projects: > - Not a currency, not a settlement-network, but a mechanism for bridging > them. > - Broader and more inclusive scope than existing vendor-specific APIs > and conventional finance industry networking protocols. Global focus. > No legacy 'features'. No artificial barriers to innovators. > > The hope is to move towards an open source implementation of the (work > in progress) IFEX protocol that interoperates with major and emerging > settlement networks for the benefit of all parts of the community. We > have already had expressions of interest from representatives in a > range of communities (Bitcoin, CES, Ripple, W3C Web Payments, digital > currency exchange developers, etc.), and look forward your input on > the mailing list. > > Happy Friday the 13th! > > Regards, > Walter Stanish > The IFEX Project > http://www.ifex-project.org/ > > > ------------------------------------------------------------------------------ > For Developers, A Lot Can Happen In A Second. > Boundary is the first to Know...and Tell You. > Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! > http://p.sf.net/sfu/Boundary-d2dvs2 > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development > --20cf3005132ecab8f404bd8cc292 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Walter,

This could be of interest to the XChange project. See Git= Hub: https://github.com/ti= mmolter/XChange

The aim of this project is to provide a unifed A= PI for applications to access financial exchanges. At present it supports B= itcoin exchanges (MtGox and Intersango are the primary focus with others to= follow). It is in the very early stages of development, but is likely to b= e integrated into the MultiBit Bitcoin client (see http://multibit.org) in the near future (early prototypes are a= vailable directly from sources).

One problem that the XChange development team faces is that each exchan= ge rolls its own data model and uses its own protocol (web socket, socket I= O, direct socket and so on). To provide a reference implementation of how a= n exchange should publish its data would be beneficial.

Kind regards,

Gary

On 13 April= 2012 10:34, Walter Stanish <walter@stani.sh> wrote:
The Internet Financial EXchange (IFEX) Project is an open body for the
discussion and development of financial standards for the internet
community. =C2=A0The project seeks to focus on enhancing interoperability between financial settlement systems of all types, including
conventional financial systems, emerging digital currencies,
alternative financial communities, and financial service providers.

Interested parties are invited to review the proposals on the website
at http://www.if= ex-project.org/ and join the mailing list at
http://group.i= fex-project.org/

Two items on the site that may be of particular interest:

(1) The latest version of the IIBAN Proposal (v1) for financial
endpoint identification at
http://www.ifex-project.org/our-proposals/iiban. =C2=A0This latest v= ersion
includes initial IANA registry contents and a reference mechanism for
financial endpoint transcription error correction. (Relevance: In
contrast to settlement system-specific financial endpoint identifiers,
IIBAN provides a democratically allocated, 13 character identifier
that is already familiar in format to users in Europe and other
countries and is theoretically compatible with conventional banking
infrastructure in those regions. =C2=A0In addition, IIBAN is not tied to any specific financial commodity or settlement system, and provides
strong protection against identifier transcription errors.)

(2) The IFEX Protocol is a *work in progress* that hopes to bridge the
gap between conventional financial systems, emerging digital
currencies, alternative financial communities, and financial service
providers by providing a standard protocol for transaction and
settlement path negotiation with arbitrary financial instruments,
currencies or assets. =C2=A0(Relevance: better connectivity, lower
settlement fees, real time redundant financial routing, arbitrary
instrument/currency/asset handling)

How IFEX's proposed infrastructure differs from existing projects:
=C2=A0- Not a currency, not a settlement-network, but a mechanism for bridg= ing them.
=C2=A0- Broader and more inclusive scope than existing vendor-specific APIs=
and conventional finance industry networking protocols. Global focus.
No legacy 'features'. No artificial barriers to innovators.

The hope is to move towards an open source implementation of the (work
in progress) IFEX protocol that interoperates with major and emerging
settlement networks for the benefit of all parts of the community. We
have already had expressions of interest from representatives in a
range of communities (Bitcoin, CES, Ripple, W3C Web Payments, digital
currency exchange developers, etc.), and look forward your input on
the mailing list.

Happy Friday the 13th!

Regards,
Walter Stanish
The IFEX Project
http://www.ifex-= project.org/

---------------------------------------------------------------------------= ---
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.= sf.net/sfu/Boundary-d2dvs2
_______________________________________________
Bitcoin-development mailing list
Bitcoin-develo= pment@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-de= velopment

--20cf3005132ecab8f404bd8cc292--