Open GoogleCodeExporter opened 9 years ago
I have currently implemented an Android content provider for this (just one
data source though).
However, I feel that even under the light of issue 125 this just doesn't feel a
good fit to BitCoinJ. That's because everything else is P2P.
Original comment by andreas....@gmail.com
on 3 Feb 2012 at 2:03
Sure, but that's alright. Perhaps one day we'll have p2p broadcast of exchange
data or something, but until then, direct fetching can work OK.
Original comment by hearn@google.com
on 3 Feb 2012 at 2:13
Myself and Tim Molter are currently working on a unified exchange library
called XChange under the MIT license. Code is at an early stage, but is in
GitHub here: https://github.com/timmolter/XChange
It might be worth reading around the Wiki to see the general design approach.
While it's implemented in Java we are hoping to provide enough detail that it
can be easily ported to other languages.
Original comment by g.rowe.f...@gmail.com
on 3 Feb 2012 at 3:35
If you're going to focus primarily on Bitcoin exchanges, would you want to fold
that into BitcoinJ or we would depend on it via Maven or ... ? It's just I
think this is such a common operation I'd like it to be a first class part of
the API somehow.
Original comment by hearn@google.com
on 3 Feb 2012 at 3:51
The aim for XChange is to be a general purpose exchange offering, not confined
to Bitcoin exchanges. This will allow for more sophisticated trading (say using
LSE against Mt Gox and so on). However, since Mt Gox will be well-supported,
I'd say that BitCoinJ could reference it as a "provided optional" dependency
and then use it's common API to permit developers to work with many exchanges.
Otherwise BitCoinJ starts duplicating the existing effort and may be forced to
be selective with which exchanges it supports.
Original comment by g.rowe.f...@gmail.com
on 5 Feb 2012 at 7:14
Original comment by hearn@google.com
on 8 Jan 2013 at 4:43
Original issue reported on code.google.com by
hearn@google.com
on 3 Feb 2012 at 1:45