From: Gary Rowe <g.rowe@froot•co.uk>
To: Walter Stanish <walter@stani•sh>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Announcing the IFEX Project
Date: Fri, 13 Apr 2012 11:16:07 +0100 [thread overview]
Message-ID: <CAKm8k+3Ep4FhQnFqeD23k4i+ifCd3opBWdkF_Lwv1=qx7jfAaw@mail.gmail.com> (raw)
In-Reply-To: <CACwuEiPSXLOLwQiia2pv5RbD1sQPMBcD6h0R2K4Nrpx=i3ZKpw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4242 bytes --]
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 <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. 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
>
[-- Attachment #2: Type: text/html, Size: 5269 bytes --]
prev parent reply other threads:[~2012-04-13 10:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-13 9:34 Walter Stanish
2012-04-13 10:16 ` Gary Rowe [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAKm8k+3Ep4FhQnFqeD23k4i+ifCd3opBWdkF_Lwv1=qx7jfAaw@mail.gmail.com' \
--to=g.rowe@froot$(echo .)co.uk \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=walter@stani$(echo .)sh \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox