NuclearPhynance Archive

About 4 months ago, I released here information that I work on startup related to market data distribution from cryptocurrency markets on this thread: https://nuclearphynance.com/Show%20Post.aspx?PostIDKey=184393



Several people from this forum show interest, many thanks @mtsm for input.



Website is live at address https://www.coinapi.io/ and project provides access to market data from cryptocurrency markets using simple API and multiple protocols (HTTP REST, WebSocket, FIX).



From first customer acquisitions, I see that there is a demand for data export and more quick start materials how to play with historical data, so it will be added in upcoming days, including how load data directly into R or Matlab using single line of code.



I strive for your feedback!

Do you have bitrex? Historical data or just a pipe through?



Listing the exchange coverage in an obvious place, and historical data availability would be useful.



Also explaining how you collect the data (Kraken for example, uses some weird polling scheme, poloniex uses websockets, etc, only coinbase has a grownup API) may or may not make people inclined to buy. Since most of the APIs are garbage designed by node.js bros, it's probably as easy to deal with them directly than it is to trust someone else who might bork the clocks or do something weak of the sauces.

>> Do you have bitrex? Historical data or just a pipe through?



Yes. For every exchange there are historical data and real-time stream.



>> Listing the exchange coverage in an obvious place.



I will add that, listing is public at https://rest.coinapi.io/v1/exchanges but i noticed that people better like html tables than json data;-)



>> Also explaining how you collect the data (Kraken for example, uses some weird polling scheme, poloniex uses websockets, etc, only coinbase has a grownup API) may or may not make people inclined to buy.



Kraken is connected through rest, using this weird pooling scheme (time credits). Poloniex and coinbase are through websockets. It's good idea to include this on integration scope page!



>> Since most of the APIs are garbage designed by node.js bros, it's probably as easy to deal with them directly than it is to trust someone else who might bork the clocks or do something weak of the sauces.



It's very hard to deal with them directly because of fact they are developed by node.js bros. Mostly because of no standarization and many things dont make sense for experienced developers also you need standarize and clean metadata yourself by hand. I don't get your second part, our real-time data is distributed without additionality latency and there was a lot of bugfixing and tweeking down the road so from my perspective it's hard task to acheive similar quality of data, also we have everything both timestamped by exchange and by nearest exchange receiver to 100 nanoseconds.



If you want do that by yourself, a lot better solution will be using open-source java project which make attempt to implement all the API, but like I mentioned earlier at the end if you want to collocate it on AWS will be few times more expense and prepare to deal with: bugs, redudnacy, infrastructure, data cleansing, data transport pipe from java to your environment, development hours etc. and at the end you dont have history data, support and integration assitance.



Thanks for this questions, it's clear for me that this value propositions should be visible on website.



I hope it expains something more and maybe opens next questions for me.

nice looking landing page.



why is TensorFlow listed as a supported language?

@jslade: Integration scope page is available at https://www.coinapi.io/integration



This was not probably well cleared by me: CoinAPI publishing all exchanges via all protocols, so if on exchange side is only REST, then on our side data will also appear in real-time streams (WebSockets and FIX), as soon as new trade appear or book will change will be received.



@h0h0: why is TensorFlow listed as a supported language?



It can be connected through python sdk. Initially we think that will be separate sdk package.

Thanks for the update.

Fwiiw you have competition:



https://cpxtrading.net/news/

Semi-relatedly, anyone know a good library/resource for confirmations? Helping a friend out on a project and so far BlockCypher looks pretty good but I figure there's got to be a lot more players in this space.

This looks really cool. No worries if you can't provide details but I've a quick question, you mentioned kraken uses REST though you offer a websocket - are you just doing the polling on your side and then publishing the results via websocket?

Pretty sure Kraken uses websockets. Terrible exchange though.

>> This looks really cool. No worries if you can't provide details but I've a quick question, you mentioned kraken uses REST though you offer a websocket - are you just doing the polling on your side and then publishing the results via websocket?



Yes, we are doing that.